[OpenSER-Users] OpenSER looping routes back to itself.

Taylor Carpenter taylor at codecafe.com
Mon Jul 30 07:39:06 CEST 2007


Running OpenSER v1.1.1 with internal ip for sip client connections  
and ext ip to connect to sip providers.  I am getting loops in my  
calls sometimes... They stop after reaching the max hops  trying to  
send the BYE message to it self.  I am wondering if it is the record- 
route that I see that includes the internal IP.  The 483 error is


U 2007/07/30 00:49:56.133157 192.168.18.22:5060 -> 192.168.18.22:5060
SIP/2.0 483 Too Many Hops.
From: <sip:15126461516 at 192.168.18.1:5060>;tag=nu-481d-6c62.
To: <sip:18065436468 at 192.168.18.22:5060>;tag=6738.
Call-ID: 421ac0c6-1dd2-11b2-8093-df998124da20 at 192.168.18.91.
CSeq: 11269143 BYE.
Via: SIP/2.0/UDP 192.168.18.22;rport=5060;branch=z9hG4bKe6ff.7fe832a5.0.
Via: SIP/2.0/UDP 192.168.18.22;rport=5060;branch=z9hG4bKe6ff.6fe832a5.0.
Via: SIP/2.0/UDP 192.168.18.22;rport=5060;branch=z9hG4bKe6ff.5fe832a5.0.
Via: SIP/2.0/UDP 192.168.18.22;rport=5060;branch=z9hG4bKe6ff.4fe832a5.0.
Via: SIP/2.0/UDP 192.168.18.22;rport=5060;branch=z9hG4bKe6ff.3fe832a5.0.
Via: SIP/2.0/UDP 192.168.18.22;rport=5060;branch=z9hG4bKe6ff.2fe832a5.0.
Via: SIP/2.0/UDP 192.168.18.22;rport=5060;branch=z9hG4bKe6ff.1fe832a5.0.
Via: SIP/2.0/UDP 192.168.18.22;rport=5060;branch=z9hG4bKe6ff.0fe832a5.0.
Via: SIP/2.0/UDP 192.168.18.22;rport=5060;branch=z9hG4bKe6ff.fee832a5.0.
Via: SIP/2.0/UDP 192.168.18.22;rport=5060;branch=z9hG4bKe6ff.eee832a5.0.
Via: SIP/2.0/UDP 192.168.18.91:5060;rport=5060.
Server: OpenSer (1.1.1-notls (i386/linux)).
Content-Length: 0.

Any ideas?




More information about the Users mailing list