Re: [asterisk-users] ISDN Cause Code 47 Errors

2014-01-23 Thread Dale Noll
Thanks Richard and Andres.

I had come to the same conclusion, however the provider was fairly snarky
in saying is was my equipment.

We were able to replace the Cisco 2800 with a Cisco 2900 series and the
problem appears to have been resolved.

Thanks again, I always appreciate another set of eyes just in case I missed
something.

Dale



On Wed, Jan 22, 2014 at 11:57 AM, Andres and...@telesip.net wrote:


 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI
 Span: 4  TEI=0 Call Ref: len= 2 (reference 6918/0x1B06) (Sent from
 originator)
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI
 Span: 4  Message Type: RELEASE COMPLETE (90)
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI
 Span: 4  [08 02 80 af]
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI
 Span: 4  Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare:
 0  Location: User (0)
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI
 Span: 4   Ext: 1  Cause: Resource unavailable, unspecified
 (47), class = Network Congestion (resource unavailable) (2) ]

   My guess is your provider did not have a free voice channel to pass
 audio at some leg in the call.  There could be multiple legs in the call
 and one of them had 'Network Congestion'.

 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI
 Span: 4 Received message for call 0xb750d598 on link 0x9b33f2c TEI/SAPI 0/0
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI
 Span: 4 -- Processing IE 8 (cs0, Cause)
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI
 Span: 4 q931.c:8567 post_handle_q931_message: Call 6918 enters state 0
 (Null).  Hold state: Idle
 [Jan 14 12:56:04] VERBOSE[13262] sig_pri.c: [Jan 14 12:56:04] Span 4:
 Processing event PRI_EVENT_HANGUP
 [Jan 14 12:56:04] VERBOSE[13262] sig_pri.c: [Jan 14 12:56:04] -- Span
 4: Channel 0/2 got hangup, cause 47


  Richard





 --
 Technical Supporthttp://www.cellroute.net


 --
 _
 -- 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

-- 
_
-- 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] ISDN Cause Code 47 Errors

2014-01-22 Thread Richard Mudgett
On Mon, Jan 20, 2014 at 5:16 PM, Dale Noll dn...@wi.rr.com wrote:

 We fairly recently switched service providers for our 4 PRI circuits.
 Since that time, we started to notice some failed inbound calls. These
 calls terminate with an ISDN cause code 47 'resource unavailble'. Most of
 the time I see this error on the first or second channel on the second span
 in a trunk group (This is the providers trunk group for hunting, not an
 Asterisk trunk group).  All the PRIs are setup as individual spans, we are
 not using NFAS. If the provider sets the hunt method to 'least recently
 used channel', then I can receive calls on other channels on the secondary
 span, it is just the first 2 that consistently fail.

 We have had occasion where the error occurs on first span. If enough calls
 come in at the same time, callers who happen to land on channel 3 or above
 are OK. When the problem happens on the first span, if we physically
 disconnect the first span(RED alarm), the calls hunt to the second span and
 all calls seem to process properly. The only way to clear the cause 47
 errors from the first span is a power cycle on the provider equipment.
 Power cycling my equipment does not solve the problem, only when I cycle
 their equipment.

 The provider says the cause 47 is coming from my equipment, yet the 'core
 set debug on' log, unless I am reading it wrong, says it is coming from
 their side.

 I have a second server as a backup. Both servers have identical hardware
 and software. When switching to the backup server, the problem remains.

 I had the same setup on the previous provider, except using NFAS, and did
 not have this problem.

 Am I reading the log correctly?


Yes.  Asterisk has accepted the selected channel and CONNECTed the
call.  It is the peer that is disconnecting the call with cause 47.  This
really
appears to be a problem in the providers equipment.


 Do I have something setup incorrectly?


I don't see anything wrong.


 Is there any way to get even lower level debugging on the PRI?


Not really.  The problem is at layer 3 (Q.931) not layer 2 (Q.921).
Turning on
intense PRI debug will add nothing but noise to the debug log.

snip

===
 Log sample with ISDN debug on
 ===
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  Protocol Discriminator: Q.931 (8)  len=87
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  TEI=0 Call Ref: len= 2 (reference 6918/0x1B06) (Sent from originator)
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  Message Type: SETUP (5)
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  [04 03 80 90 a2]
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  Bearer Capability (len= 5) [ Ext: 1  Coding-Std: 0  Info transfer
 capability: Speech (0)
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4   Ext: 1  Trans mode/rate: 64kbps,
 circuit-mode (16)
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4 User information layer 1: u-Law (34)
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  [18 03 a9 83 82]
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  Channel ID (len= 5) [ Ext: 1  IntID: Implicit  Other(PRI)  Spare: 0
  Exclusive  Dchan: 0
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4ChanSel: As indicated in following octets
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4Ext: 1  Coding: 0  Number Specified  Channel
 Type: 3
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4Ext: 1  Channel: 2 Type: CPE]
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  [1c 1d 9f 8b 01 00 a1 17 02 01 1f 02 01 00 80 0f 43 65 6c 6c 20 50 68
 6f 6e 65 20 20 20 57 49]
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  Facility (len=31, codeset=0) [ 0x9F, 0x8B, 0x01, 0x00, 0xA1, 0x17,
 0x02, 0x01, 0x1F, 0x02, 0x01, 0x00, 0x80, 0x0F, 'Cell Phone   WI' ]
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  [28 0f 43 65 6c 6c 20 50 68 6f 6e 65 20 20 20 57 49]
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  Display (len=15) [ Cell Phone   WI ]
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  [6c 0c 21 80 34 31 34 33 33 31 32 34 37 30]
 [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
 4  Calling Number (len=14) [ Ext: 0  TON: National Number (2)  NPI:
 ISDN/Telephony Numbering Plan (E.164/E.163) (1)
 [Jan 14 12:56:04] VERBOSE[13262] 

Re: [asterisk-users] ISDN Cause Code 47 Errors

2014-01-22 Thread Andres



[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04]
PRI Span: 4  TEI=0 Call Ref: len= 2 (reference 6918/0x1B06) (Sent
from originator)
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04]
PRI Span: 4  Message Type: RELEASE COMPLETE (90)
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04]
PRI Span: 4  [08 02 80 af]
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04]
PRI Span: 4  Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU)
standard (0)  Spare: 0  Location: User (0)
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04]
PRI Span: 4   Ext: 1  Cause: Resource unavailable, unspecified
(47), class = Network Congestion (resource unavailable) (2) ]

My guess is your provider did not have a free voice channel to pass 
audio at some leg in the call.  There could be multiple legs in the call 
and one of them had 'Network Congestion'.


[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04]
PRI Span: 4 Received message for call 0xb750d598 on link 0x9b33f2c
TEI/SAPI 0/0
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04]
PRI Span: 4 -- Processing IE 8 (cs0, Cause)
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04]
PRI Span: 4 q931.c:8567 post_handle_q931_message: Call 6918 enters
state 0 (Null).  Hold state: Idle
[Jan 14 12:56:04] VERBOSE[13262] sig_pri.c: [Jan 14 12:56:04] Span
4: Processing event PRI_EVENT_HANGUP
[Jan 14 12:56:04] VERBOSE[13262] sig_pri.c: [Jan 14 12:56:04]
-- Span 4: Channel 0/2 got hangup, cause 47



Richard






--
Technical Support
http://www.cellroute.net

-- 
_
-- 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