[Spce-user] BYE not correct when sent by called party SPCE 2.8

Flo florian at acw.at
Fri Sep 20 08:08:54 EDT 2013


Hi Andrew,

thank you for your answer!

Unfortunately, I don't know, where and how I could change this!

Can you please tell me!

Florian

On 09/20/2013 01:56 PM, Andrew Pogrebennyk wrote:
> Hi Florian,
>
> On 09/20/2013 11:59 AM, Flo wrote:
>> Hello,
>>
>> here some better logs!
>>
>> kamailio-proxy.log -> nothing to see from the BYE packet from the called
>> party
>>
>> kamailio-lb.log -> attached
>> ngrep-sip br > attached
>
> Better now, as I see from the ngrep the peer is sending the BYE with
> wrong Request-URI.
>
> We send our Contact to peer as:
> Contact:
> <sip:ngcp-lb at SUBSCRIBERNATIP.36:5060;ngcpct=c2lwOjEyNy4wLjAuMTo1MDgw>'
>
> This means it should send a BYE to spce with same URI as Request-URI.
> But it sends a BYE sip:43CALLEDNUMBER at vgw01.PEERDOMAIN.net SIP/2.0'
>
> Here is the part of the trace I'm talking about:
>
> #
> U 2013/09/20 11:49:51.827378 SUBSCRIBERNATIP.36:5060 -> PEERIP:5060
> ACK sip:0043CALLEDNUMBER at PEERIP SIP/2.0'
> Max-Forwards: 10'
> Record-Route:
> <sip:SUBSCRIBERNATIP.36;r2=on;lr=on;ftag=2D6F97BF-523C1A35000A2A97-A5609700;ngcplb=yes>'
> Record-Route:
> <sip:127.0.0.1;r2=on;lr=on;ftag=2D6F97BF-523C1A35000A2A97-A5609700;ngcplb=yes>'
> Via: SIP/2.0/UDP
> SUBSCRIBERNATIP.36;branch=z9hG4bKff01.cc2d0e998dd6b9b89bf530351fd42957.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKcZIzLa2R;rport=5080'
> From: <sip:bla at vgw01.PEERDOMAIN.net>;tag=2D6F97BF-523C1A35000A2A97-A5609700'
> To:
> <sip:43CALLEDNUMBER at vgw01.PEERDOMAIN.net>;tag=733740290666219083462495233513'
> CSeq: 11 ACK'
> Call-ID: 53e8e45c-b62fd7a2 at 172.16.2.224_b2b-1'
> Proxy-Authorization: Digest username="bla", realm="PEERIP",
> nonce="556337816273119283810480695675",
> uri="sip:0043CALLEDNUMBER at PEERIP",
> response="83ff938fd2f867cec8073e79a20e41c3", algorithm=MD5'
> Content-Length: 0'
> Contact:
> <sip:ngcp-lb at SUBSCRIBERNATIP.36:5060;ngcpct=c2lwOjEyNy4wLjAuMTo1MDgw>'
> '
>
>
> #
> U 2013/09/20 11:49:56.728444 PEERIP:5060 -> SUBSCRIBERNATIP.36:5060
> BYE sip:43CALLEDNUMBER at vgw01.PEERDOMAIN.net SIP/2.0'
> Max-Forwards: 50'
> Via: SIP/2.0/UDP PEERIP:5060;rport;branch=z9hG4bK15704533780527689185809'
> Route:
> <sip:SUBSCRIBERNATIP.36;r2=on;lr=on;ftag=2D6F97BF-523C1A35000A2A97-A5609700;ngcplb=yes>'
> Route:
> <sip:127.0.0.1;r2=on;lr=on;ftag=2D6F97BF-523C1A35000A2A97-A5609700;ngcplb=yes>'
> From:
> <sip:43CALLEDNUMBER at vgw01.PEERDOMAIN.net>;tag=733740290666219083462495233513'
> To: <sip:bla at vgw01.PEERDOMAIN.net>;tag=2D6F97BF-523C1A35000A2A97-A5609700'
> Contact: <sip:0043CALLEDNUMBER at PEERIP>'
> User-Agent: bla2-vgw01'
> Call-ID: 53e8e45c-b62fd7a2 at 172.16.2.224_b2b-1'
> CSeq: 11 BYE'
> Allow:
> INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER,SUBSCRIBE'
> Cisco-Guid: 13594-1012006928-2324243254-2782071253'
> Content-Length: 0'
>





More information about the Spce-user mailing list