[Spce-user] ngcpct='sip:127.0.0.1:5080' in Contact header

Skyler skchopperguy at gmail.com
Wed Mar 27 15:53:13 EDT 2013


I would say that the invite you are looking at was internal between the 
proxy and lb. its easy to mix them. Would be impossible for any outside 
peer to contact localhost so SPCE would not insert 127.0.0.1 as a 
contact to an outside peer. Are you sure the invite was from your 
external IP to the external peer IP?

Skyler

On 3/27/2013 10:17 AM, Gary Nieboer wrote:
> I found an old pcap with an invite showing the Contact.
>
> That could be the issue.   On the SPCE Invite to the Peer, the only
> thing in the capture is:
>
>     Contact: <sip:127.0.0.1:5080 <http://127.0.0.1:5080>>
>
>
> and nothing in the Contact field about our ip:  x.x.x.x:5060 or with
>   "ngcp-lb" or "ngcpct"
>
>
>
>
> -Gary
> --
> Gary Nieboer
>
>
> 877-763-1014 Toll Free  |  801-657-5484 Utah  |  615-800-6946 Tennessee
> | 801-694-6106 Mobile
> gary at netdiverse.com <mailto:gary at netdiverse.com>  | www.netdiverse.com
> <http://www.netdiverse.com/>
>
>
> On Wed, Mar 27, 2013 at 10:48 AM, Skyler <skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>> wrote:
>
>     My guess (as I've not actually had this issue) is that your contact
>     would look something like:
>
>     Contact:
>     <sip:ngcp-lb at your.ext.ip.__address:5060;ngcpct='sip:127.__0.0.1:5080
>     <http://127.0.0.1:5080>'>
>
>     Skyler
>
>
>     On 3/27/2013 9:42 AM, Gary Nieboer wrote:
>
>         I will give a couple of the items advised a try.
>
>         Should there be more than one uri in the Contact field?  If so,
>         that may
>         be the quick fix.  The contact field I captured a few weeks ago
>         only has
>         one, and it is the loopback/proxy address of 127.0.0.1:5080
>         <http://127.0.0.1:5080>
>         <http://127.0.0.1:5080>
>
>         -Gary
>         --
>         Gary Nieboer
>
>
>         877-763-1014 <tel:877-763-1014> Toll Free  | 801-657-5484
>         <tel:801-657-5484> Utah  | 615-800-6946 <tel:615-800-6946> Tennessee
>         | 801-694-6106 <tel:801-694-6106> Mobile
>         gary at netdiverse.com <mailto:gary at netdiverse.com>
>         <mailto:gary at netdiverse.com <mailto:gary at netdiverse.com>>  |
>         www.netdiverse.com <http://www.netdiverse.com>
>         <http://www.netdiverse.com/>
>
>
>
>         On Wed, Mar 27, 2013 at 10:31 AM, Skyler <skchopperguy at gmail.com
>         <mailto:skchopperguy at gmail.com>
>         <mailto:skchopperguy at gmail.com
>         <mailto:skchopperguy at gmail.com>__>> wrote:
>
>              That makes sense, also might just be that the ngcpct sip
>         uri is the
>              last uri read in the contact.
>
>                Maybe Sylvester and Gary could test this out as they have
>         the OP.
>
>              What would a good test look like to base64-encode that
>         ngcpct in a
>              customtt.tt2?
>
>              Skyler
>
>
>              On 3/27/2013 9:07 AM, Andreas Granig wrote:
>
>                  Hi,
>
>                  On 03/27/2013 04:55 PM, Skyler wrote:
>
>                         I created an lo:0 with a private IP address
>                      (10.10.xxx.xxx) for lb >
>                      b2buas: & proxies > sip:. That may help in this
>         case as its
>                      likely the
>                      127.0.0.1 which is confusing the upstream proxy.
>
>
>                  I've heard of endpoints disliking the SIP uri with the
>         quotes...
>                  so one
>                  option could be to convert the
>         "ngcpct='sip:127.0.0.1:5080 <http://127.0.0.1:5080>
>                  <http://127.0.0.1:5080>'" and
>                  base64-encode the "sip:127.0.0.1:5080
>         <http://127.0.0.1:5080> <http://127.0.0.1:5080>",
>
>                  so it gets something like
>                  "ngcpct=____c2lwOjEyNy4wLjAuMTo1MDgwCg==" instead.
>
>                  Andreas
>
>
>              ___________________________________________________
>              Spce-user mailing list
>         Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>         <mailto:Spce-user at lists.__sipwise.com
>         <mailto:Spce-user at lists.sipwise.com>>
>         http://lists.sipwise.com/____listinfo/spce-user
>         <http://lists.sipwise.com/__listinfo/spce-user>
>              <http://lists.sipwise.com/__listinfo/spce-user
>         <http://lists.sipwise.com/listinfo/spce-user>>
>
>
>




More information about the Spce-user mailing list