[Spce-user] CE 2.6 - send reply to contact

[Andreas Granig]

Klaus Peter,

The trace you sent is incomplete (doesn't show the second call leg), so
it's impossible to tell where things went wrong. Please provide a trace
which also contains the second leg (with the "_b2b-1" suffix in the
Call-ID). Also check /var/log/ngcp/sems.log for this call to see if it
complains about something obvious, because it's replying with 481,
although it even forwards the CANCEL and gets a 200 back for it.

In any case, it seems to have nothing to do with replies or even the
Contact header, but with bad CANCEL message.

Andreas

On 09/21/2012 06:28 PM, Klaus Peter v. Friedeburg wrote:
> Hi Andreas,
> 
> o.k. my mistake I have misspelled the problem and will try again:
> 
> I have make an SIP-Capture (see attached pcap-file) and an image from the SIP-flow (see attaches png-file) so you can see what the problem is.
> Packet No 28 come from PSTN-Gateway and have a contact-header
> But ngcp 2.6 ignore this
> The effect is that the phone in the PSTN ringing and you can pick up the call, but the PSTN-Gateway terminate the call after a few seconds
> NGCP has not recogniced that the call was establishes for a few seconds
> Mediaproxy is still disabled for domain and for the peer
> 
> (because of the attaches files I don’t send this message to the list, I have sending an other message (without attachments to the list)
> 
> Klaus Peter
> 
>> -----Ursprüngliche Nachricht-----
>> Von: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von
>> Andreas Granig
>> Gesendet: Donnerstag, 20. September 2012 21:35
>> An: spce-user at lists.sipwise.com
>> Betreff: Re: [Spce-user] CE 2.6 - send reply to contact
>>
>>
>>
>> On 09/20/2012 09:09 PM, Klaus Peter v. Friedeburg wrote:
>>> I have problems to build up the following szenario:
>>> My PSTN-Provider have a SIP-loadbalancer with IP 1.1.1.1. This IP is the peering.
>>> But the replys must be send to an other the IP ex. 1.1.1.2 (written down in contact header)
>>>
>>> How is a way to send my replys to the contact ?
>>
>> Replies are sent along the Via header vector. If your peering provider
>> requires you to send replies to somewhere else than it originated from,
>> he should set the Via accordingly.
>>
>> If you really must hack that scenario (which horribly breaks the SIP
>> RFC, so I'd REALLY not do it), you can use textops module to alter the
>> topmost Via in the request already, so replies automatically take
>> another path. Not sure if there's a way to change the d-uri of a reply
>> because it's forbidden by RFC.
>>
>> Andreas
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20120921/8118b7ae/attachment-0001.asc>