[Spce-user] Contact header too long?
Marco Teixeira
admin at marcoteixeira.com
Thu Mar 23 14:47:22 EDT 2017
So... searching around the mailing list archives, I can see that in the
ngcpct parameter was 22 chars shorter back in 2014...
https://lists.sipwise.com/pipermail/spce-user/2014-January/005675.html
is this something I can manipulate? the length of ngcpct?
=Marco
On Thu, Mar 23, 2017 at 6:20 PM, Marco Teixeira <admin at marcoteixeira.com>
wrote:
> Forgot to mention, the peer is a Metaswitch Perimeta SBC.
>
> =Marco
>
>
> On Thu, Mar 23, 2017 at 6:04 PM, Marco Teixeira <admin at marcoteixeira.com>
> wrote:
>
>> Hi list,
>>
>> Trying to figure out a problem where calls incoming from peer get dropped
>> around 900 secs.
>> Peer vendor claiming the issue is, and I quote:
>>
>> "(...) because the request-uri is >160 bytes. (...) The reason the
>> Request-URI is so long is due to the long contact header coming from
>> 1.2.3.4 -
>> Contact: <sip:ngcp-lb at 1.2.3.4:5060;ngcpct=7369703a3332372e302e302e313
>> a353338303b707278726f7574653d33>"
>> Please ask the customer to reduce the length of the ngcpct parameter
>> coming from their SIP server."
>>
>> Has anyone ever came across this issue?
>> Is 160 bytes limits even on the SIP RFC?
>> How can i shorten or stop using ngcpct parameter in contact?
>>
>> Apreciate your help,
>> Marco
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170323/1e8caeeb/attachment-0001.html>
More information about the Spce-user
mailing list