[Spce-user] Outbound time out
Jeremie Chism
jchism2 at gmail.com
Wed Nov 14 13:44:42 EST 2012
Thanks. I am thoroughly pleased with this software. Most of the issues I experienced are due to a learning curve on my end. I am very excited to move forward with this product.
Sent from my iPhone
On Nov 14, 2012, at 12:35 PM, Andreas Granig <agranig at sipwise.com> wrote:
> Hi Jeremie,
>
> As a reminder, please always keep the communication on-list (unless
> you're explicitely asked to send potentially sensitive data), so the
> emails get archived and other people can search them and find solutions
> for issues which already got solved in the past.
>
> Thanks,
> Andreas
>
> On 11/14/2012 07:26 PM, Skyler wrote:
>> No problem. A point of etiquette though, since yer learning.
>>
>> 3 emails up I provided step-by-step commands to capture live logs/ngrep
>> into files and how to email those files as attachments. All from your
>> box. Please learn that by sending to yourself and use it for future
>> comms here. Long copy/paste logs in multiple emails is a real PIA to
>> follow and takes twice as long to determine the solution. ;)
>>
>>
>> Skyler
>>
>> On 11/14/2012 10:18 AM, Jeremie Chism wrote:
>>> Sorry for all the problems. Guess Im learning though. Thanks for
>>> sticking in here with me.
>>>
>>>
>>> On Wed, Nov 14, 2012 at 12:13 PM, Skyler <skchopperguy at gmail.com
>>> <mailto:skchopperguy at gmail.com>> wrote:
>>>
>>> yep that's it. I was about to ask if you had aaddress disabled in
>>> your config.yml
>>>
>>>
>>>
>>> On 11/14/2012 10:08 AM, Jeremie Chism wrote:
>>>
>>> I think i found the problem. I was looking in addresses. I
>>> disabled
>>> aaddress and now the call is staying up. Will this cause other
>>> problems?
>>>
>>>
>>>
>>> On Wed, Nov 14, 2012 at 11:44 AM, Skyler <skchopperguy at gmail.com
>>> <mailto:skchopperguy at gmail.com>
>>> <mailto:skchopperguy at gmail.com
>>> <mailto:skchopperguy at gmail.com>__>> wrote:
>>>
>>> So here's what you can do to get everything needed into my
>>> mailbox
>>> quick and easy :)
>>> sudo ngrep-sip b -d any -qt -W byline >
>>> /tmp/live-ngrep-cap &
>>> sudo tail -f /var/log/ngcp/kamailio-proxy.__log >
>>> /tmp/live-proxy-log
>>> --perform test call--
>>> Ctrl+c (to kill the tail process)
>>> fg 1
>>> Ctrl+c (to kill the ngrep process)
>>> cd /tmp
>>> (uuencode live-ngrep-cap live-ngrep-cap.txt && uuencode
>>> live-proxy-log live-proxy-log.txt) | mail -s "[Spce-user]
>>> Files you
>>> requested" skchopperguy at gmail.com
>>> <mailto:skchopperguy at gmail.com> <mailto:skchopperguy at gmail.com
>>> <mailto:skchopperguy at gmail.com>__>
>>>
>>>
>>>
>>> On Wed, Nov 14, 2012 at 9:09 AM, Jeremie Chism
>>> <jchism2 at gmail.com <mailto:jchism2 at gmail.com>
>>> <mailto:jchism2 at gmail.com <mailto:jchism2 at gmail.com>>>
>>> wrote:
>>>
>>> I saw that to. I'm getting everything that you needed
>>> instead of
>>> what I sent you. Sorry.
>>>
>>> Sent from my iPhone
>>>
>>> On Nov 14, 2012, at 10:59 AM, Skyler
>>> <skchopperguy at gmail.com <mailto:skchopperguy at gmail.com>
>>> <mailto:skchopperguy at gmail.com
>>> <mailto:skchopperguy at gmail.com>__>> wrote:
>>>
>>> You see the INFO: <script>: New request - M=BYE
>>> R=sip:127.0.0.1:5080 <http://127.0.0.1:5080>
>>> <http://127.0.0.1:5080/>
>>>
>>> At some point before this your box is sending
>>> replies to
>>> itself instead of to your subscriber. I'm trying to
>>> figure out
>>> what is happening before the new request and why.
>>> One way is
>>> to see the entire log of the call and not just the
>>> end of the
>>> call.
>>> S.
>>>
>>> On Wed, Nov 14, 2012 at 8:41 AM, Jeremie Chism
>>> <jchism2 at gmail.com <mailto:jchism2 at gmail.com>
>>> <mailto:jchism2 at gmail.com <mailto:jchism2 at gmail.com>>> wrote:
>>>
>>> after looking into it more, I dont think that
>>> is what you
>>> need. I see two Call ID's in the call example
>>> i sent in
>>> the prior email. I thought the call ID toward
>>> the end
>>> would be the same throughout the entire call.
>>>
>>>
>>> On Wed, Nov 14, 2012 at 10:14 AM, Skyler
>>> <skchopperguy at gmail.com
>>> <mailto:skchopperguy at gmail.com>
>>> <mailto:skchopperguy at gmail.com
>>> <mailto: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
>>> <mailto:skchopperguy at gmail.com>
>>> <mailto:skchopperguy at gmail.com
>>> <mailto: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>
>>> <mailto:skchopperguy at gmail.com
>>> <mailto:skchopperguy at gmail.com>__>
>>> <mailto:skchopperguy at gmail.com
>>> <mailto:skchopperguy at gmail.com>
>>>
>>> <mailto: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 <mailto:jbonilla at sipwise.com>>
>>>
>>> <mailto:jbonilla at sipwise.com <mailto:jbonilla at sipwise.com>
>>>
>>> <mailto:jbonilla at sipwise.com <mailto:jbonilla at sipwise.com>>>
>>>
>>>
>>> <mailto:jbonilla at sipwise.com <mailto: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 <mailto:jchism2 at gmail.com>>
>>>
>>> <mailto:jchism2 at gmail.com <mailto:jchism2 at gmail.com>
>>>
>>> <mailto:jchism2 at gmail.com <mailto:jchism2 at gmail.com>>>
>>>
>>>
>>> <mailto:jchism2 at gmail.com <mailto: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 <http://72.21.14.34:5060>
>>>
>>> <http://72.21.14.34:5060>
>>> ->
>>> 107.7.157.250:5060 <http://107.7.157.250:5060>
>>>
>>> <http://107.7.157.250:5060>
>>> BYE
>>> sip:ngcp-lb at 107.7.157.250
>>> <mailto:sip%3Angcp-lb at 107.7.157.250>
>>>
>>> <mailto:sip%3Angcp-lb at 107.7.__157.250
>>> <mailto:sip%253Angcp-lb at 107.7.157.250>>
>>>
>>> <mailto:lb at 107.7.157.250 <mailto:lb at 107.7.157.250>
>>>
>>> <mailto:lb at 107.7.157.250 <mailto:lb at 107.7.157.250>>>
>>>
>>>
>>> <mailto:lb at 107.7.157.250 <mailto: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>
>>>
>>> <mailto:Spce-user at lists.__sipwise.com
>>> <mailto:Spce-user at lists.sipwise.com>>
>>>
>>> <mailto:Spce-user at lists.
>>> <mailto:Spce-user at lists.>__sipw__ise.com <http://sipwise.com>
>>>
>>> <mailto:Spce-user at lists.__sipwise.com
>>> <mailto:Spce-user at lists.sipwise.com>>>
>>>
>>> <mailto:Spce-user at lists.
>>> <mailto:Spce-user at lists.>__sipw__ise.com <http://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>>
>>>
>>>
>>>
>>>
>>> ___________________________________________________
>>>
>>> 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>>
>>>
>>> <mailto:Spce-user at lists.
>>> <mailto:Spce-user at lists.>__sipw__ise.com <http://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>>
>>>
>>>
>>>
>>> ___________________________________________________
>>>
>>> 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>>
>>> <mailto:Spce-user at lists.
>>> <mailto:Spce-user at lists.>__sipw__ise.com <http://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>>
>>>
>>>
>>>
>>>
>>> --
>>> Jeremie Chism
>>> Triton Communications
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Jeremie Chism
>>> Triton Communications
>>>
>>>
>>>
>>>
>>> --
>>> Jeremie Chism
>>> Triton Communications
>>
>> _______________________________________________
>> 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