[Spce-user] Problem with new peer : ngcp-lb at 82.139.112.32:5060; ngcpct='sip%3A10.18.3.200%3A5080'

Jon Bonilla (Manwe) jbonilla at sipwise.com
Mon Jun 10 14:36:21 EDT 2013


El Mon, 10 Jun 2013 17:16:59 +0200
"Raul Alonso" <raul.alonso at tpartner.net> escribió:

> Dear All,
> 
>  
> 
> I have a problem with a new peer. 
> 
> When I make a call through this peer (either incoming or outgoing) spce send
> a “contact” with ngcpct=’sip:… my peer modifies and returns
> ngcpct='sip%3A10…
> 
>  
> 
> U 2013/06/10 16:58:56.829499 82.139.112.32:5060 -> 89.10.21.41:5060
> 
> SIP/2.0 200 OK'
> 
> Contact: <sip:ngcp-lb at 82.139.112.32:5060;ngcpct='sip:10.18.3.200:5080'>'
> 
> #
> 
> U 2013/06/10 16:58:56.843893 89.10.21.41:5060 -> 82.139.112.32:5060
> 
> ACK sip:ngcp-lb at 82.139.112.32:5060;ngcpct='sip%3A10.18.3.200%3A5080'
> SIP/2.0'
> 
>  
> 
> To test I created a customtt of kamailio-lb and I deleted the part of ngcpct
> = 'sip: ...
> 
>  
> 
> With this change calls work correctly. but I do not know if this change will
> make other parts stop working.
> 


There is a patch pending to encode the contact header. I could provide you with
the patched version of kamailio and the templates if you want to try.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130610/64902026/attachment-0001.asc>


More information about the Spce-user mailing list