[cisco-voip] Q.931 disconnect problem

Thu Jul 31 02:05:56 EDT 2008

Need to see the entire "debug isdn q931"...cannot tell you what is going
on without that.  The disconnect cause alone does not tell the whole
story, just the reason the switch/gateway gives.

You can see bearer cap in the TX->SETUP in the debug...like this:

18:39:29.425: ISDN BR0: TX -> SETUP
    pd = 8  callref = 0x10
18:39:29.433:
         Bearer Capability i = 0x8890  <---
18:39:29.441: Channel ID i = 0x83
18:39:29.449:
         Keypad Facility i = '5558888'
18:39:29.822: ISDN BR0: RX <- CALL_PROC
    pd = 8  callref = 0x90

You can decode that, or get someone in TAC to do it for you, and figure
out why your switch does not support that.  That or change the bearer
cap with a isdn call-type (or something like that) command.

joshd.

________________________________

From: Tseveendorj Ochirlantuu [mailto:tseveendorj at gmail.com] 
Sent: Wednesday, July 30, 2008 11:16 PM
To: Josh Duffek
Subject: Re: [cisco-voip] Q.931 disconnect problem

Thank you guys

I saw that URL before and cooperated with telco guys but they told me
that problem came from your side. 

I'm testing "Recovery on timer expiry". Didn't see that error from log
after increased interdigit timeouts on my gateway. After that
configuration I faced new logs :(

Cause i = 0x82FF - Interworking error; unspecified
Cause i = 0x82C1 - Bearer capability not implemented

Thank you for any helps :)

I would like to experiencing on VoIP very much indeed.

Best regards,
Tseveen

On Thu, Jul 31, 2008 at 11:53 AM, Josh Duffek <joshd at tredent.com> wrote:

Tseveen,

Here is a good page for decoding isdn disconnect cause codes:

http://www.cisco.com/en/US/tech/tk801/tk379/technologies_tech_note09186a
008012e95f.shtml

The first octet, 0x82, is:

82-the public network near the local user (the switch your device is
connected to)

And "e6 - recovery on timer expiry" means, something like, it was
expecting a response or whatever from us and it did not get that in the
specified amount of time(sh isdn timer if you want to see how they are
setup on yours)...so it send us a disconnect.  Maybe we have a bad route
for that particular number or something...not sure.

Like Michael is saying, if you post the whole "debug isdn q931", and
"debug isdn event" might be helpful...we can probably tell you what is
actually going on with the call.  "sh isdn active", and "sh isdn
service" for PRIs are good to have as well.

joshd @

Tredent.com

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Michael
Thompson
Sent: Wednesday, July 30, 2008 5:36 AM
To: 'Tseveendorj Ochirlantuu'
Cc: cisco-voip at puck.nether.net

Subject: Re: [cisco-voip] Q.931 disconnect problem

Can you give the rest of the Q.931 debug feedback?  It looks like it may
be a T3XX timer.  Things like interdigit timer (T.302), etc may show a
feedback like that if someone started to dial a number while offhook and
stopped dialing.

This is purely conjecture (both of my responses are to be honest)
without more info.

MT

________________________________

From: Tseveendorj Ochirlantuu [mailto:tseveendorj at gmail.com] 
Sent: Wednesday, July 30, 2008 2:41 AM
To: Michael Thompson
Subject: Re: [cisco-voip] Q.931 disconnect problem

Hi Michael,

Thank you for very quick reply and explanation.

I'm newbie on VoIP. Please, can you explain what is the reason I got
following error?

  Cause i = 0x82E6 - Recovery on timer expiry

Thank you.

On Wed, Jul 30, 2008 at 1:54 PM, Michael Thompson
<mthompson729 at gmail.com> wrote:

Are you experiencing some specific issue or are you must seeing these
logs and expressing concern?

If it's the latter, it may be as simple as someone calling a number that
is a DID on the PRI but doesn't have a DN on the phone system.

Let's assume you have a call come in on your DID block of 248.555.1XXX.
Let's say the last 4 digits (subscriber) are 1133.  if there's no
extension 1133 on your PBX, your result will be 'number unassigned'.

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tseveendorj
Ochirlantuu
Sent: Wednesday, July 30, 2008 1:47 AM
To: cisco-voip at puck.nether.net
Cc: cisco-nsp at puck.nether.net
Subject: [cisco-voip] Q.931 disconnect problem

Hi guys,

This gateway used for call terminating. I have found following log on my
gateway. These are come from debug isdn q931.

part of entire log: 

    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x8090 - Normal call clearing 
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x8491 - User busy 
    Cause i = 0x82E6 - Recovery on timer expiry
    Cause i = 0x82E6 - Recovery on timer expiry
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x82E6 - Recovery on timer expiry
    Cause i = 0x82E6 - Recovery on timer expiry
    Cause i = 0x8491 - User busy
    Cause i = 0x8090 - Normal call clearing 
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x8090 - Normal call clearing
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x8491 - User busy 
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x8491 - User busy
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
    Cause i = 0x8090 - Normal call clearing 
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x8090 - Normal call clearing 
    Cause i = 0x8290 - Normal call clearing
    Cause i = 0x8290 - Normal call clearing

My question is

1. What kind of reason following errors occurred ?
2. How to solve that ?

  Cause i = 0x809E - Response to STATUS ENQUIRY or number unassigned 
  Cause i = 0x82E6 - Recovery on timer expiry

Thanks for any help.

Best regards,
Tseveen.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080730/bced2750/attachment-0001.html>