[OpenSIPS-Users] why 483 too many Hops

Kurtis Heimerl kheimerl at endaga.com
Sat May 24 02:55:11 CEST 2014


Hi,

I'm just starting with OpenSIPs, but this means that the message isn't
being routed correctly. It's falling through the dialplan to a self-route,
which causes it to handle it again, eventually failing as it cuts the hop
count every time. I'm working on resolving the issue myself, but that is
the core of it.


On Fri, May 23, 2014 at 7:23 AM, toasterisk at gmail.com
<toasterisk at gmail.com>wrote:

> hello:
> I install opensips-1.8.2 and asterisk together at my vmware. but when I
> register the SIP phone or physical
> Phone, the clients always show 483 too many Hops. I disable the fireware
> and use:
>  ngrep -d lo -qt -W byline port 5060, the debug info is this:
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.4fd0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.3fd0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.2fd0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.1fd0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.0fd0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.fed0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.eed0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.ded0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.ced0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.bed0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.aed0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.9ed0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.8ed0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.7ed0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.6ed0d422.0.
> Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bKda41.5ed0d422.0.
> Via: SIP/2.0/UDP 192.168.1.103:5060;received=192.168.1.103;branch=z9hG4bK176606475;rport=5060.
>
> From: <sip:bob at 192.168.1.104>;tag=1356181947.
> To: <sip:bob at 192.168.1.104>.
> Call-ID: 2124473842-5060-1 at BJC.BGI.B.BAD.
> CSeq: 2029 REGISTER.
> Contact: <sip:bob at 192.168.1.103:5060>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B824017A0>".
>
> X-Grandstream-PBX: true.
> Max-Forwards: 26.
> User-Agent: Grandstream GXP2124 1.0.4.10.
> Supported: path.
> Expires: 480.
> Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER,
> UPDATE, MESSAGE.
> Content-Length: 0.
> P-hint: outbound.
> P-hint: outbound.
> P-hint: outbound.
> P-hint: outbound.
> P-hint: outbound.
> P-hint: outbound.
> P-hint: outbound.
> P-hint: outbound.
> =================================================================
> anyone knows this problem?
>
>
> ------------------------------
> *Cheers!*
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20140523/15c02928/attachment.htm>


More information about the Users mailing list