Re: [asterisk-users] SIP Debugging Information..

2012-11-27 Thread Matthew J. Roth
Michael L. Young wrote:

> If I am reading this right, it looks like a BYE is coming in from
> the far end, Bandwidth.com.


Prior to that, Asterisk retransmits the OK to Bandwidth.com's INVITE
twice.  It doesn't look like Bandwidth.com receives any of them,
because they never respond with an ACK.  Since, from Bandwidth.com's
perspective, the call is never setup, they terminate it with a BYE.

It could just be a NAT issue, but there are two things I really don't
understand about the SIP dialog:

1) It starts with an ACK from Bandwidth.com.  Is it possible that
   the debugging output is missing the beginning of the dialog?

2) Every timestamp is "Nov 23 15:43:13".  I don't think the SIP
   session timers on either end should be expiring quickly enough
   for this to happen.

Do other calls originating from Bandwidth.com work properly?  If so,
comparing the SIP from a working call to a failed call may be
revealing.

Regards,

Matthew Roth
InterMedia Marketing Solutions
Software Engineer and Systems Developer

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] SIP Debugging Information..

2012-11-24 Thread Michael L. Young
- Original Message -
> From: "Howard Leadmon" 
> To: asterisk-users@lists.digium.com
> Sent: Saturday, November 24, 2012 3:19:10 PM
> Subject: [asterisk-users] SIP Debugging Information..
> 
> 
>  I did a little googling, but didn't seem to find anything specific
>  to
> answer the question.   I am trying to debug some calls on an Asterisk
> system
> (AsteriskNow) that are dropping, and when the general logs didn't
> nail
> anything I turned on SIP Debugging on the trunk to the provider.
> Basically the complaint is that when some call in, regardless of if
> the call
> is answered, or if Vmail answers it, it drops the calls in a matter
> of
> seconds.   The strange thing is, that the system processes many
> hundreds of
> calls daily, but only a couple specific incoming callers are seeing
> the
> drops.  I would have thought a NAT issue, but why does this only
> affect a
> specific group of incoming callers, the rest go about their business
> just
> fine.  I think thinking bandwidth.com is mucking something up, but
> again I
> have no specific proof one way or another, so why the debugging.
> 
>  When one of the problem callers is dropped, in the SIP debugging I
>  see:
> 
>   chan_sip.c: Scheduling destruction of SIP dialog
> '285991942_79966325@192.168.27.72' in 6400 ms (Method: BYE)
> 
>  
> Is this the remote end (ie bandwidth.com) dropping the call, or is
> the local
> Asterisk server dropping the call?

[snip]
> ---
> [Nov 23 15:43:13] VERBOSE[5127] chan_sip.c:
> <--- SIP read from UDP:216.82.224.202:5060 --->
> BYE sip:4104159270@10.98.4.36:5060 SIP/2.0
> Record-Route: 
> Record-Route: 
> Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bKe902.53bde7e.0
> Via: SIP/2.0/UDP 67.231.4.93;branch=z9hG4bKe902.32697e93.0
> Via: SIP/2.0/UDP 192.168.27.72:5060;branch=z9hG4bK0bBac8c2c3cb90659df
> From: ;tag=gK0b66d829
> To: ;tag=as0850c6db
> Call-ID: 285991942_79966325@192.168.27.72
> CSeq: 297 BYE
[snip]

If I am reading this right, it looks like a BYE is coming in from the far end, 
Bandwidth.com.

Michael
(elguero)

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] SIP Debugging Information..

2012-11-24 Thread Howard Leadmon

 I did a little googling, but didn't seem to find anything specific to
answer the question.   I am trying to debug some calls on an Asterisk system
(AsteriskNow) that are dropping, and when the general logs didn't nail
anything I turned on SIP Debugging on the trunk to the provider.
Basically the complaint is that when some call in, regardless of if the call
is answered, or if Vmail answers it, it drops the calls in a matter of
seconds.   The strange thing is, that the system processes many hundreds of
calls daily, but only a couple specific incoming callers are seeing the
drops.  I would have thought a NAT issue, but why does this only affect a
specific group of incoming callers, the rest go about their business just
fine.  I think thinking bandwidth.com is mucking something up, but again I
have no specific proof one way or another, so why the debugging.

 When one of the problem callers is dropped, in the SIP debugging I see:

  chan_sip.c: Scheduling destruction of SIP dialog
'285991942_79966325@192.168.27.72' in 6400 ms (Method: BYE)

 
Is this the remote end (ie bandwidth.com) dropping the call, or is the local
Asterisk server dropping the call?


 For any that care to look at all the gory details, here is a chunk of the
debugging output:


[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: 
<--- SIP read from UDP:216.82.224.202:5060 --->
ACK sip:4104159233@10.98.4.36:5060 SIP/2.0
Record-Route: 
Record-Route: 
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bKebf3.453cc5a5.2
Via: SIP/2.0/UDP 67.231.8.93;branch=z9hG4bKebf3.315d4e14.3
Via: SIP/2.0/UDP 192.168.37.72:5060;branch=z9hG4bK0eB7f5f0b80116aa493
From: ;tag=gK0e4bc97f
To: ;tag=as6974aee7
Call-ID: 353260172_48597606@192.168.37.72
CSeq: 11346 ACK
Max-Forwards: 68
Content-Length: 0

<->
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: --- (12 headers 0 lines) ---
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: 
<--- SIP read from UDP:216.82.224.202:5060 --->
INVITE sip:4104159233@10.98.4.36:5060 SIP/2.0
Record-Route: 
Record-Route: 
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bKfbf3.9d9b1065.0
Via: SIP/2.0/UDP 67.231.8.93;branch=z9hG4bKfbf3.c159a6a.0
Via: SIP/2.0/UDP 192.168.37.72:5060;branch=z9hG4bK0eB7f601a4d116aa493
From: ;tag=gK0e4bc97f
To: ;tag=as6974aee7
Call-ID: 353260172_48597606@192.168.37.72
CSeq: 11347 INVITE
Max-Forwards: 68
Contact: 
Content-Length: 235
Content-Disposition: session; handling=required
Content-Type: application/sdp

v=0
o=Sonus_UAC 22153 5058 IN IP4 192.168.37.72
s=SIP Media Capabilities
c=IN IP4 67.231.8.102
t=0 0
m=audio 6576 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=maxptime:20
<->
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: --- (15 headers 11 lines) ---
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Sending to 216.82.224.202:5060
(NAT)
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Found RTP audio format 0
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Found RTP audio format 101
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Found audio description format
PCMU for ID 0
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Found audio description format
telephone-event for ID 101
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Capabilities: us - 0x104
(ulaw|g729), peer - audio=0x4 (ulaw)/video=0x0 (nothing)/text=0x0 (nothing),
combined - 0x4 (ulaw)
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Non-codec capabilities (dtmf):
us - 0x1 (telephone-event|), peer - 0x1 (telephone-event|), combined - 0x1
(telephone-event|)
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Peer audio RTP is at port
67.231.8.102:6576
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: 
<--- Transmitting (NAT) to 216.82.224.202:5060 --->
SIP/2.0 100 Trying
Via: SIP/2.0/UDP
216.82.224.202;branch=z9hG4bKfbf3.9d9b1065.0;received=216.82.224.202;rport=5
060
Via: SIP/2.0/UDP 67.231.8.93;branch=z9hG4bKfbf3.c159a6a.0
Via: SIP/2.0/UDP 192.168.37.72:5060;branch=z9hG4bK0eB7f601a4d116aa493
Record-Route: 
Record-Route: 
From: ;tag=gK0e4bc97f
To: ;tag=as6974aee7
Call-ID: 353260172_48597606@192.168.37.72
CSeq: 11347 INVITE
Server: FPBX-2.9.0(1.8.15.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO,
PUBLISH
Supported: replaces
Contact: 
Content-Length: 0


<>
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Audio is at 11444
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Adding codec 0x4 (ulaw) to SDP
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: Adding non-codec 0x1
(telephone-event) to SDP
[Nov 23 15:43:13] VERBOSE[5127] chan_sip.c: 
<--- Reliably Transmitting (NAT) to 216.82.224.202:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP
216.82.224.202;branch=z9hG4bKfbf3.9d9b1065.0;received=216.82.224.202;rport=5
060
Via: SIP/2.0/UDP 67.231.8.93;branch=z9hG4bKfbf3.c159a6a.0
Via: SIP/2.0/UDP 192.168.37.72:5060;branch=z9hG4bK0eB7f601a4d116aa493
Record-Route: 
Record-Route: 
From: ;tag=gK0e4bc97f
To: ;tag=as6974aee7
Call-ID: 353260172_48597606@192.168.37.72
CSeq: 11347 INVITE
Server: FPBX-2.9.0(1.8.15.1)
Allow: INVITE, ACK, CANC