[Spce-user] Contact header too long?
agranig at sipwise.com
Fri Mar 24 09:27:44 EDT 2017
There is no limit in the SIP RFC (unless I overlooked something), and
different vendors handle it differently. E.g. the Dialogic SBC has a
limit at 1024, see
Actually not much you can do here. The ngcpct is there to work around
issues for other user-agents, which don't handle a Contact of 127.0.0.1
very well, which we used to send in certain scenarios (which is also
totally fine in theory, but in practice breaks some clients). Therefore
we put the IP of the kamailio-lb there and store the original one in
masked form in the ngcpct param and reconstruct it in other scenarios.
On 03/23/2017 07:47 PM, Marco Teixeira wrote:
> So... searching around the mailing list archives, I can see that in the
> ngcpct parameter was 22 chars shorter back in 2014...
> is this something I can manipulate? the length of ngcpct?
> On Thu, Mar 23, 2017 at 6:20 PM, Marco Teixeira <admin at marcoteixeira.com
> <mailto:admin at marcoteixeira.com>> wrote:
> Forgot to mention, the peer is a Metaswitch Perimeta SBC.
> On Thu, Mar 23, 2017 at 6:04 PM, Marco Teixeira
> <admin at marcoteixeira.com <mailto: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 126.96.36.199 -
> Contact: <sip:ngcp-lb at 188.8.131.52:5060
> 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,
> Spce-user mailing list
> Spce-user at lists.sipwise.com
More information about the Spce-user