[cisco-voip] cisco-voip Digest, Vol 52, Issue 69

May, Simon Simon.May at ihs.com
Mon Jun 11 01:54:22 EDT 2007


It was my mistake.

I was receiving a call on an ISDN trunk, using a dialpeer to push it to
a CME router, however there was a dialpeer configured on that router
that sent it back to the originator, dropping the preceding 9.

Debugged the dialpeers on both routers to see it actually happening.

Fixed now ...

Simon

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of
cisco-voip-request at puck.nether.net
Sent: 10 June 2007 17:00
To: cisco-voip at puck.nether.net
Subject: cisco-voip Digest, Vol 52, Issue 69

Send cisco-voip mailing list submissions to
	cisco-voip at puck.nether.net

To subscribe or unsubscribe via the World Wide Web, visit
	https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
	cisco-voip-request at puck.nether.net

You can reach the person managing the list at
	cisco-voip-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."


Today's Topics:

   1. Re: CME ISDN Voice Problem (Paul Choi)


----------------------------------------------------------------------

Message: 1
Date: Sun, 10 Jun 2007 04:28:22 -0700 (PDT)
From: Paul Choi <asobihoudai at yahoo.com>
Subject: Re: [cisco-voip] CME ISDN Voice Problem
To: "May, Simon" <Simon.May at ihs.com>, cisco-voip at puck.nether.net
Message-ID: <112314.25521.qm at web57207.mail.re3.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1

How did you fix it?

Paul
--- "May, Simon" <Simon.May at ihs.com> wrote:

> I've fixed this, so please ignore.
> 
>  
> 
> Sinon
> 
>  
> 
> ________________________________
> 
> From: May, Simon 
> Sent: 10 June 2007 05:33
> To: 'cisco-voip at puck.nether.net'
> Subject: CME ISDN Voice Problem
> 
>  
> 
> The following is a Q.931 debug of a failed incoming
> call ... any ideas
> why it is failing, and any resolution?
> 
> Why is the called party converted from 920 to 20?
> 
>  
> 
>  
> 
> Jun  9 12:07:09.580: ISDN Se0/0/0:23 Q931: RX <-
> SETUP pd = 8  callref =
> 0x1C4E 
> 
>         Bearer Capability i = 0x8090A2 
> 
>                 Standard = CCITT 
> 
>                 Transfer Capability = Speech  
> 
>                 Transfer Mode = Circuit 
> 
>                 Transfer Rate = 64 kbit/s 
> 
>         Channel ID i = 0xA98381 
> 
>                 Exclusive, Channel 1 
> 
>         Facility i = 0x9F8B0100A10802012A0201008400 
> 
>         Calling Party Number i = 0x1180,
> '447980788157' 
> 
>                 Plan:ISDN, Type:International 
> 
>         Called Party Number i = 0x80, '920' 
> 
>                 Plan:Unknown, Type:Unknown
> 
> Jun  9 12:07:09.600: ISDN Se0/0/0:23 Q931:
> pak_private_number: Invalid
> type/plan 0x0 0x0 may be overriden; sw-type 3
> 
> Jun  9 12:07:09.600: ISDN Se0/0/0:23 Q931: Applying
> typeplan for sw-type
> 0x3 is 0x2 0x1, Called num 
> 
> Jun  9 12:07:09.600: ISDN Se0/0/0:23 Q931: TX ->
> CALL_PROC pd = 8
> callref = 0x9C4E 
> 
>         Channel ID i = 0xA98381 
> 
>                 Exclusive, Channel 1
> 
> Jun  9 12:07:09.600: ISDN Se0/0/0:23 Q931: TX ->
> SETUP pd = 8  callref =
> 0x03CC 
> 
>         Bearer Capability i = 0x8090A2 
> 
>                 Standard = CCITT 
> 
>                 Transfer Capability = Speech  
> 
>                 Transfer Mode = Circuit 
> 
>                 Transfer Rate = 64 kbit/s 
> 
>         Channel ID i = 0xA98397 
> 
>                 Exclusive, Channel 23 
> 
>         Calling Party Number i = 0x1180,
> '447980788157' 
> 
>                 Plan:ISDN, Type:International 
> 
>         Called Party Number i = 0xA1 
> 
>                 Plan:ISDN, Type:National
> 
> Jun  9 12:07:09.724: ISDN Se0/0/0:23 Q931: RX <-
> RELEASE_COMP pd = 8
> callref = 0x83CC 
> 
>         Cause i = 0x80DA - Segmentation error
> 
> Jun  9 12:07:09.740: ISDN Se0/0/0:23 Q931:
> pak_private_number: Invalid
> type/plan 0x0 0x0 may be overriden; sw-type 3
> 
> Jun  9 12:07:09.744: ISDN Se0/0/0:23 Q931: Applying
> typeplan for sw-type
> 0x3 is 0x2 0x1, Called num 20
> 
> Jun  9 12:07:09.744: ISDN Se0/0/0:23 Q931: TX ->
> SETUP pd = 8  callref =
> 0x03CD 
> 
>         Bearer Capability i = 0x8090A2 
> 
>                 Standard = CCITT 
> 
>                 Transfer Capability = Speech  
> 
>                 Transfer Mode = Circuit 
> 
>                 Transfer Rate = 64 kbit/s 
> 
>         Channel ID i = 0xA98397 
> 
>                 Exclusive, Channel 23 
> 
>         Calling Party Number i = 0x1180,
> '447980788157' 
> 
>                 Plan:ISDN, Type:International 
> 
>         Called Party Number i = 0xA1, '20' 
> 
>                 Plan:ISDN, Type:National
> 
> Jun  9 12:07:09.824: ISDN Se0/0/0:23 Q931: RX <-
> RELEASE_COMP pd = 8
> callref = 0x83CD 
> 
>         Cause i = 0x809C - Invalid number format
> (incomplete number)
> 
> Jun  9 12:07:09.844: ISDN Se0/0/0:23 Q931: TX ->
> DISCONNECT pd = 8
> callref = 0x9C4E 
> 
>         Cause i = 0x809C - Invalid number format
> (incomplete number)
> 
> Jun  9 12:07:09.924: ISDN Se0/0/0:23 Q931: RX <-
> RELEASE pd = 8  callref
> = 0x1C4E
> 
> Jun  9 12:07:09.924: ISDN Se0/0/0:23 Q931: TX ->
> RELEASE_COMP pd = 8
> callref = 0x9C4E
> 
>  
> 
> Simon May
> 
> Simon.may at ihs.com
> 
> > _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 



       
________________________________________________________________________
____________Ready for the edge of your seat? 
Check out tonight's top picks on Yahoo! TV. 
http://tv.yahoo.com/


------------------------------

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


End of cisco-voip Digest, Vol 52, Issue 69
******************************************


More information about the cisco-voip mailing list