[Spce-user] Outbound time out

Jeremie Chism jchism2 at gmail.com
Wed Nov 14 11:38:45 EST 2012


Here is the log from the call i sent you in the last email.  If this wont
work I can do another complete call with ngrep and grep

root at sipwise:~# grep 'Fo04o9iQ_b2b-1' /var/log/ngcp/kamailio-proxy.log
Nov 14 09:59:49 sipwise /usr/sbin/kamailio[20726]: INFO: <script>: New
request - M=BYE R=sip:127.0.0.1:5080 F=sip:+13185374776 at 72.21.14.34 T=
sip:13184504920 at 107.7.157.250 IP=72.21.14.34:5060 (127.0.0.1:5060)
ID=Fo04o9iQ_b2b-1
Nov 14 09:59:49 sipwise /usr/sbin/kamailio[20726]: INFO: <script>: Stop
mediaproxy for all branches - R=sip:127.0.0.1:5080 ID=Fo04o9iQ_b2b-1
Nov 14 09:59:49 sipwise /usr/sbin/kamailio[20726]: WARNING: <script>:
Domain not served here - R=sip:127.0.0.1:5080 ID=Fo04o9iQ_b2b-1
Nov 14 09:59:49 sipwise /usr/sbin/kamailio[20725]: INFO: <script>: New
request - M=BYE R=sip:127.0.0.1:5080 F=sip:+13185374776 at 72.21.14.34 T=
sip:13184504920 at 107.7.157.250 IP=72.21.14.34:5060 (127.0.0.1:5060)
ID=Fo04o9iQ_b2b-1
Nov 14 09:59:49 sipwise /usr/sbin/kamailio[20725]: INFO: <script>: Stop
mediaproxy for all branches - R=sip:127.0.0.1:5080 ID=Fo04o9iQ_b2b-1
Nov 14 09:59:49 sipwise /usr/sbin/kamailio[20725]: WARNING: <script>:
Domain not served here - R=sip:127.0.0.1:5080 ID=Fo04o9iQ_b2b-1
Nov 14 09:59:50 sipwise /usr/sbin/kamailio[20723]: INFO: <script>: New
request - M=BYE R=sip:127.0.0.1:5080 F=sip:+13185374776 at 72.21.14.34 T=
sip:13184504920 at 107.7.157.250 IP=72.21.14.34:5060 (127.0.0.1:5060)
ID=Fo04o9iQ_b2b-1
Nov 14 09:59:50 sipwise /usr/sbin/kamailio[20723]: INFO: <script>: Stop
mediaproxy for all branches - R=sip:127.0.0.1:5080 ID=Fo04o9iQ_b2b-1
Nov 14 09:59:50 sipwise /usr/sbin/kamailio[20723]: WARNING: <script>:
Domain not served here - R=sip:127.0.0.1:5080 ID=Fo04o9iQ_b2b-1
Nov 14 09:59:52 sipwise /usr/sbin/kamailio[20728]: INFO: <script>: New
request - M=BYE R=sip:127.0.0.1:5080 F=sip:+13185374776 at 72.21.14.34 T=
sip:13184504920 at 107.7.157.250 IP=72.21.14.34:5060 (127.0.0.1:5060)
ID=Fo04o9iQ_b2b-1
Nov 14 09:59:52 sipwise /usr/sbin/kamailio[20728]: INFO: <script>: Stop
mediaproxy for all branches - R=sip:127.0.0.1:5080 ID=Fo04o9iQ_b2b-1
Nov 14 09:59:52 sipwise /usr/sbin/kamailio[20728]: WARNING: <script>:
Domain not served here - R=sip:127.0.0.1:5080 ID=Fo04o9iQ_b2b-1
Nov 14 09:59:56 sipwise /usr/sbin/kamailio[20730]: INFO: <script>: New
request - M=BYE R=sip:127.0.0.1:5080 F=sip:+13185374776 at 72.21.14.34 T=
sip:13184504920 at 107.7.157.250 IP=72.21.14.34:5060 (127.0.0.1:5060)
ID=Fo04o9iQ_b2b-1
Nov 14 09:59:56 sipwise /usr/sbin/kamailio[20730]: INFO: <script>: Stop
mediaproxy for all branches - R=sip:127.0.0.1:5080 ID=Fo04o9iQ_b2b-1
Nov 14 09:59:56 sipwise /usr/sbin/kamailio[20730]: WARNING: <script>:
Domain not served here - R=sip:127.0.0.1:5080 ID=Fo04o9iQ_b2b-1
root at sipwise:~#



On Wed, Nov 14, 2012 at 10:14 AM, Skyler <skchopperguy at gmail.com> wrote:

> ok, well it is definitely your box which is not replying to upstream. Then
> the upstream timer is likely reached so they BYE you.
>
> I need a matching ngrep with proxy log. In case you don't know what I
> mean..
>
> sudo ngrep-sip b -d any -qt -W byline > /tmp/ngrep-1 &
> sudo tail -f /var/log/ngcp/kamailio-proxy.**log > /tmp/proxy-1
>
> Do test call until its dead air or you think its all logged
>
> Ctrl+c to kill the tail
> fg 1
> Ctrl+c to kill the ngrep
>
> attach the /tmp/ngrep-1 and /tmp/proxy-1 to this thread.
>
>
> Skyler
>
>
>
> On 11/14/2012 7:30 AM, Jeremie Chism wrote:
>
>> No I did no customization.
>>
>> Sent from my iPhone
>>
>> On Nov 14, 2012, at 9:06 AM, Skyler <skchopperguy at gmail.com> wrote:
>>
>>  Did you do any customizations to LB or Proxy using customtt.tt2's (or
>>> hopefully not the stock cfg.tt2's)?
>>>
>>> If yes, move the customtt to /tmp/ do ngcpcfg apply and run another test
>>> call.
>>>
>>> Skyler
>>>
>>> On 11/14/2012 6:27 AM, Jeremie Chism wrote:
>>>
>>>> I just saw this address: 4.55.12.33
>>>>
>>>> It is a level 3 address. That is probably who my upstream is using.
>>>>
>>>> I do know that my upstream said they pass some information straight
>>>> through.
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On Nov 14, 2012, at 8:00 AM, Skyler <skchopperguy at gmail.com
>>>> <mailto:skchopperguy at gmail.com**>> wrote:
>>>>
>>>>  Hey,
>>>>>
>>>>> I'm not so sure that the timers on your box is the problem. There's
>>>>> 5-6 IP's in your capture, meaning a few proxies/end-points and right
>>>>> before the drop/BYE I think there is a 200 OK missing. Also, you
>>>>> mention that the call does drop; Indicating that there should not be a
>>>>> BYE at all since no person hungup.
>>>>>
>>>>> This seems to be that time-out rather than timer is the culprit, by
>>>>> way of no-reply to an ACK. But on which end and who is sending the BYE.
>>>>>
>>>>> Can you list out your IP's like 1.2.3.4 = subscriber, 3.2.2.1 = spce,
>>>>> another = upstream etc. this will make it easier, at least for me, to
>>>>> get a visual on the call flow to see which side is not replying.
>>>>>
>>>>> PM if you like.
>>>>>
>>>>> Skyler
>>>>>
>>>>> On 11/14/2012 5:32 AM, Jeremie Chism wrote:
>>>>>
>>>>>> I was digging through past posts and saw someone that had a similar
>>>>>> problem. Here was your recommendation that worked.
>>>>>>
>>>>>>  /  See if this works with your subscribers. If not, try disabling the
>>>>>>>>
>>>>>>> />>/  session
>>>>>> />>/  timers setting this line:
>>>>>> />>/  enable_session_timer=yes
>>>>>> />>/  to
>>>>>> />>/  enable_session_timer=no
>>>>>> />>/
>>>>>> />>/
>>>>>> />>/  and exec "ngcpcfg apply" again
>>>>>> />>/
>>>>>> />>
>>>>>>
>>>>>>
>>>>>> /Where can I find this to edit it. What would be the command please?/
>>>>>>
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>> On Nov 13, 2012, at 2:28 PM, Jon Bonilla (Manwe)
>>>>>> <jbonilla at sipwise.com <mailto:jbonilla at sipwise.com>
>>>>>> <mailto:jbonilla at sipwise.com>> wrote:
>>>>>>
>>>>>>  El Tue, 13 Nov 2012 13:51:37 -0600
>>>>>>> Jeremie Chism <jchism2 at gmail.com <mailto:jchism2 at gmail.com>
>>>>>>> <mailto:jchism2 at gmail.com>> escribió:
>>>>>>>
>>>>>>>  U 2012/11/13 13:48:44.360480 72.21.14.34:5060 -> 107.7.157.250:5060
>>>>>>>> BYE sip:ngcp-lb at 107.7.157.250 <mailto:lb at 107.7.157.250>
>>>>>>>> <mailto:lb at 107.7.157.250>:5060 SIP/2.0'
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Can't start a capture with the BYE. Please copy the whole capture to
>>>>>>> a
>>>>>>> txt file
>>>>>>> and the proxy log to another text file and attach them to your mail.
>>>>>>>
>>>>>>>
>>>>>>> ______________________________**_________________
>>>>>>> Spce-user mailing list
>>>>>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.**sipwise.com<Spce-user at lists.sipwise.com>
>>>>>>> >
>>>>>>> <mailto:Spce-user at lists.**sipwise.com <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 <mailto:Spce-user at lists.**sipwise.com<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 <mailto:Spce-user at lists.**sipwise.com<Spce-user at lists.sipwise.com>
>>>>> >
>>>>> http://lists.sipwise.com/**listinfo/spce-user<http://lists.sipwise.com/listinfo/spce-user>
>>>>>
>>>>


-- 
Jeremie Chism
Triton Communications
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121114/8473de40/attachment-0001.html>


More information about the Spce-user mailing list