[Spce-user] Contact header too long?

[Marco Teixeira]

Thankx Andreas,

Question is, this was working before on 3.8.7 and simptoms started aftrer
upgrading to 3.8.9.

Like i said, on the forum there is at least one finding witch stated a
smaller base64 hash...
Did this hash increase in size between the two versions?

=Marco


On Fri, Mar 24, 2017 at 1:27 PM, Andreas Granig <agranig at sipwise.com> wrote:

> Hi,
>
> 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
> https://www.dialogic.com/webhelp/BorderNet2020/2.1.0/
> WebHelp/sip_message_header_restrict.htm.
>
> 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.
>
> Andreas
>
> 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...
> > 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
> > <mailto: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 <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 1.2.3.4 -
> >         Contact: <sip:ngcp-lb at 1.2.3.4:5060
> >         <http://sip:ngcp-lb@1.2.3.4:5060>;ngcpct=
> 7369703a3332372e302e302e313a353338303b707278726f7574653d33>"
> >         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
> >
> >
> >
> >
> >
> > _______________________________________________
> > Spce-user mailing list
> > Spce-user at lists.sipwise.com
> > https://lists.sipwise.com/listinfo/spce-user
> >
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170324/15206018/attachment-0001.html>