[Spce-user] ngcpct='sip:127.0.0.1:5080' in Contact header
Skyler
skchopperguy at gmail.com
Sun Mar 31 13:33:14 EDT 2013
Hi,
Seems your call is dropping due to confused signalling. You should not
need to input the 10.10.10.1 into your Taqua gw control list. One thing
I see which does not look correct is the 100 trying response after the
initial invite (spce > peer). as below:
U 2013/03/30 16:13:10.848816 208.73.198.12:5060 -> 208.73.199.250:5060
SIP/2.0 100 Trying'
Via: SIP/2.0/UDP
208.73.199.250;branch=z9hG4bK3642.4b4263c869b06a079cb58096dc4f3039.0,SIP/2.0/UDP
10.10.10.1:5080;branch=z9hG4bKPfekkaGS;rport=5080'
From:
<sip:4179730088 at 208.73.199.250>;tag=57FE8F4B-51575566000CD752-90AB5700'
To: <sip:4172302354 at 208.73.198.12>'
Call-ID: 1454999203-5060-7 at BJC.BGI.B.BF_b2b-1'
CSeq: 10 INVITE'
Content-Length: 0'
'
Notice this first response from the peer contains a single Via having
'SIP/2.0/UDP' twice. As though (assuming) the Taqua gw is appending the
ngcpct= to the via. This could be a case of needing to code the quirks
of this Taqua into spce to overcome its (Taqua) needs for signalling.
What is your spce version?
Latest updates?
Do you have any customtt.tt2 files in your lb or proxy?
My first inclination in troubleshooting is to rule out any individual
customtt files which may have accidentally broken something in spce. Try
moving customtt files to /tmp then ngcpcfg apply, do a test-call again
to see if (or which) customtt may be causing this.
This is only my suggestion, I cannot duplicate or test this behavior.
Skyler
On 3/30/2013 2:22 PM, Marc Rys wrote:
> Sorry for the delay. Attached is the file as requested.
>
> Marc
>
> ----- Original Message -----
> From: "Skyler" <skchopperguy at gmail.com>
> To: spce-user at lists.sipwise.com
> Sent: Wednesday, March 27, 2013 3:05:30 PM
> Subject: Re: [Spce-user] ngcpct='sip:127.0.0.1:5080' in Contact header
>
> I would run..
>
> ngrep-sip b -d any -qt -W byline port 5060 >/tmp/ngcpct_check.txt
>
> and make a test call. Then attach the txt to the list.
>
> Skyler
>
> On 3/27/2013 10:30 AM, Marc Rys wrote:
>> Ok, Im not sure if this is related, but I've been having struggles with our Taqua Gateway peering to SPCE. OUr Gateway kept replying back with a 403 Forbidden whenever SPCE tried to send a call to it.
>>
>> After seeing your dialog about the contact headers, i looked at one our wireshark captures and our Invites were showing the same thing...
>> sip:ngcp-lb at your.ext.ip.address:5060;ngcpct='sip:127.0.0.1:5080'
>>
>> I followed the instructions for the audiocodes fix and changed our dummy address to 10.10.10.1 On our Taqua Gateway I had to add the dummy IP to the IP control list.. (10.10.10.1:5080) and now the Taqua accepts calls from SPCE.
>>
>> I'm not sure if this is solution for you to use with the other providers listed in the thread.
>>
>> In my attached wireshark cap, it appears that SPCE is sending an ACK back from my dummy address 10.10.10.1 to my gateway. Thats not right is it? at this point now, my calls to our gateway dont stay up for longer than 32Seconds then the audio drops out of the call and the person on the PSTN side of the call is disconnected completely, and my SPCE UA appears to have the call up still with no audio until I end the call.
>>
>>
>>
>> Marc Rys
>> http://www.tri-lakes.net
>> http://www.rystec.com
>>
>> ----- Original Message -----
>> From: "Skyler" <skchopperguy at gmail.com>
>> To: "Gary Nieboer" <gary at netdiverse.com>
>> Cc: spce-user at lists.sipwise.com
>> Sent: Wednesday, March 27, 2013 11:48:44 AM
>> Subject: Re: [Spce-user] ngcpct='sip:127.0.0.1:5080' in Contact header
>>
>> 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'>
>>
>> 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>
>>>
>>> -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:31 AM, Skyler <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>'" and
>>> base64-encode the "sip: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>
>>> http://lists.sipwise.com/__listinfo/spce-user
>>> <http://lists.sipwise.com/listinfo/spce-user>
>>>
>>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>
More information about the Spce-user
mailing list