It is very likely your config is executing dispatcher function for the BYE. You can load debugger module and enable execution trace logging, so you see what functions are executed from the configuration file.
I don't see the Record-Route in the reply and Route header in the BYE, typical usage is to do record routing for handling requests within dialog.
Cheers, Daniel
On 2/13/13 9:19 PM, Scott, Matt wrote:
I don't understand how this happens, hopefully somebody know why??
When the BYE is sent to Kamailio, it forwards to an incorrect address.
This address is only in dispatcher, so I don't understand how it gets to that?
U 192.168.9.130:5060 -> 4.55.10.163:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 4.55.10.163:5060;branch=z9hG4bK0bB4b99383b1a4d3f48..From: <sip
:+1<dialed_number>@4.55.10.163:5060;isup-oli=62>;tag=gK0b747c73..To: <sip:+1<inbound_number>@192.168.9.130
:5060>;tag=as622c3fb5..Call-ID: 2081157154_72743403@4.55.10.163..CSeq: 11847 INVITE..Server: FP
BX-2.10.0(1.8.9.3)..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, P
UBLISH..Supported: replaces, timer..Contact: <sip:+1<inbound_number>@10.1.7.86:5060>..Content-Type: a
pplication/sdp..Content-Length: 228....v=0..o=root 338878463 338878463 IN IP4 10.1.7.86..s=Aste
risk PBX 1.8.9.3..c=IN IP4 10.1.7.86..t=0 0..m=audio 13212 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000.
.a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-16..a=ptime:20..a=sendrecv..
U 10.1.7.86:5060 -> 192.168.9.130:5060
BYE sip:+1<dialed_number>@4.55.10.163:5060 SIP/2.0..Via: SIP/2.0/UDP 10.1.7.86:5060;branch=z9hG4bK6e
5d6461;rport..Max-Forwards: 70..From: <sip:+1<inbound_number>@192.168.9.130:5060>;tag=as622c3fb5..To:
<sip:+1<dialed_number>@4.55.10.163:5060;isup-oli=62>;tag=gK0b747c73..Call-ID: 2081157154_72743403@4
.55.10.163..CSeq: 102 BYE..User-Agent: FPBX-2.10.0(1.8.9.3)..X-Asterisk-HangupCause: Protocol e
rror, unspecified..X-Asterisk-HangupCauseCode: 111..Content-Length: 0....
U 192.168.9.130:5060 -> 205.158.163.150:5060
BYE sip:+1<dialed_number>@<wan_ip>:5060 SIP/2.0..Record-Route: <sip:<wan_ip>:5060;lr=on>
..Via: SIP/2.0/UDP 192.168.9.130;branch=z9hG4bK6d4b.7269e5c5.0..Via: SIP/2.0/UDP 10.1.7.86:5060
;branch=z9hG4bK6e5d6461;rport=5060..Max-Forwards: 69..From: <sip:+1<inbound_number>@192.168.9.130:506
0>;tag=as622c3fb5..To: <sip:+1<dialed_number>@4.55.10.163:5060;isup-oli=62>;tag=gK0b747c73..Call-ID:
2081157154_72743403@4.55.10.163..CSeq: 102 BYE..User-Agent: FPBX-2.10.0(1.8.9.3)..X-Asterisk-H
angupCause: Protocol error, unspecified..X-Asterisk-HangupCauseCode: 111..Content-Length: 0....
U 205.158.163.150:5060 -> 192.168.9.130:5060
SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 192.168.9.130;branch=z9hG4bK6
d4b.7269e5c5.0..Via: SIP/2.0/UDP 74.63.151.37:13000;branch=z9hG4bK6e5d6461;rport=5060..From: <s
ip:+1<inbound_number>@192.168.9.130:5060>;tag=as622c3fb5..To: <sip:+1<dialed_number>@4.55.10.163:5060;isup
-oli=62>;tag=gK0b747c73..Call-ID: 2081157154_72743403@4.55.10.163..CSeq: 102 BYE..Content-Lengt
h: 0....
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users