[Spce-user] Bye, Call-ID not found or tags didn't matche

Andrew Pogrebennyk apogrebennyk at sipwise.com
Mon Apr 15 09:42:17 EDT 2013

The problem is incorrect BYE from the callee at

BYE sip:ngcp-lb at;ngcpct='sip:' SIP/2.0
Via: SIP/2.0/UDP;branch=z9hG4bKfq0qkm009091cpoq47g1sd6gobbc1.1
From: <sip:+4531456020 at>;tag=1342899548-1366030644618
To: <sip:+4578788470 at sip.talkip.dk>;tag=0062B2E2-516BF931000C6A2F-2E818700
Call-ID: 3c275f72641e-ub8931x18dr2_b2b-1
CSeq: 115520856 BYE
Max-Forwards: 29
Content-Length: 0

It is completely missing the Route headers that should be:


Hope this helps.

On 04/15/2013 02:58 PM, Sylvester Nielsen wrote:
> Here's a trace of a new call.
> -----Oprindelig meddelelse-----
> Fra: Andrew Pogrebennyk [mailto:apogrebennyk at sipwise.com] 
> Sendt: 15. april 2013 14:54
> Til: Sylvester Nielsen
> Cc: spce-user at lists.sipwise.com
> Emne: Re: SV: [Spce-user] Bye, Call-ID not found or tags didn't matche
> This probably means something is wrong in signaling, because the _b2b-1 leg is not supposed to reach proxy. it's going like:
> Caller UA -> lb -> proxy -> sbc as 3c27555c7c6b-4ikbkvf770jq sbc -> lb -> Callee UA as 3c27555c7c6b-4ikbkvf770jq_b2b-1
> Maybe the Routes are wrong somewhere and BYE with
> 3c27555c7c6b-4ikbkvf770jq_b2b-1 is going from lb to the proxy skipping sbc, need a trace (preferably as .pcap file) to tell that for sure..
> On 04/15/2013 02:47 PM, Sylvester Nielsen wrote:
>> As far as I can see, _b2b-1 is added to the call-id, which is the reason it does not recognize it.
>> However, both the invite and bye contain the _b2b-1, so the question must be why it's not removed before sending the delete request to mediaproxy.
>> Also, by looking at the rtp log, _b2b-1 only appear in the delete request.
> ********************************************************
> Denne mail er scannet af fest.dk ApS og fundet virusfri.
> ********************************************************

More information about the Spce-user mailing list