[cisco-voip] Calls from the PSTN getting 'No circuit/channelavailable'
Jason Aarons (US)
jason.aarons at us.didata.com
Sat May 12 14:00:14 EDT 2007
Fractional PRI isn't supported on MGCP. Workaround set all channels in
your pri-group timeslots, then busyout the out of service b-channels.
Example
interface Serial0/0/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-dms100
isdn incoming-voice voice
isdn service b_channel 11 state 2
isdn service b_channel 12 state 2
isdn service b_channel 13 state 2
isdn service b_channel 14 state 2
isdn service b_channel 15 state 2
isdn service b_channel 16 state 2
isdn service b_channel 17 state 2
isdn service b_channel 18 state 2
isdn service b_channel 19 state 2
isdn service b_channel 20 state 2
isdn service b_channel 21 state 2
isdn service b_channel 22 state 2
isdn bind-l3 ccm-manager
no cdp enable
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Kalle Tetto
Sent: Saturday, May 12, 2007 1:33 PM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Calls from the PSTN getting 'No
circuit/channelavailable'
Hi, I had this often before, try to play around with bchan order. change
from bottom up to top down. I also had, that I simply could not use any
of 4 channels out of 30. So contact also your telco and ask for the
channels and if they have any problem.
I have also seen, that someone has bought 16 channels and the telco only
had 12 delivered.
So I think it is a isdn layer 3 channel selection problem, of a channel
that simply not exists.
Cheers
pedro marques schrieb:
> Hi,
>
> I have a CCM running 4.2 connecting through MGCP to a 2821 Gateway.
> After some debugging and traces enabled on the CCM I noticed that the
> calls that are getting disconnected from the PSTN all fall in the
first
> 5 channels of the E1 PRI.
>
> These are the relevant commands on the 2821:
>
> controller E1 0/0/0
> pri-group timeslots 1-16 service mgcp
> !
> interface Serial0/0/0:15
> no ip address
> isdn switch-type primary-net5
> isdn incoming-voice voice
> isdn bind-l3 ccm-manager
> isdn bchan-number-order ascending
> no cdp enable
> !
> ccm-manager mgcp
> ccm-manager config server <CCM ip address>
> !
> mgcp
> mgcp call-agent <CCM ip address> service-type mgcp version 0.1
> mgcp dtmf-relay voip codec all mode out-of-band
> mgcp package-capability rtp-package
> mgcp default-package line-package
> mgcp sdp simple
> !
> mgcp profile default
>
> These are two snippets from a 'debug isdn q931':
>
> *May 10 11:32:02.582: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8
callref
> = 0x007F
> Sending Complete
> Bearer Capability i = 0x9090A3
> Standard = CCITT
> Transfer Capability = 3.1kHz Audio
> Transfer Mode = Circuit
> Transfer Rate = 64 kbit/s
> Channel ID i = 0xA18384
> Preferred, Channel 4
> Progress Ind i = 0x8183 - Origination address is non-ISDN
> Calling Party Number i = 0x0083, 'calling party number'
> Plan:Unknown, Type:Unknown
> Called Party Number i = 0x81, 'called party number'
> Plan:ISDN, Type:Unknown
> *May 10 11:32:02.602: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8
> callref = 0x807F
> Channel ID i = 0xA98384
> Exclusive, Channel 4
> *May 10 11:32:02.602: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8
> callref = 0x807F
> Cause i = 0x80A2 - No circuit/channel available
> *May 10 11:32:02.790: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8
> callref = 0x007F
> *May 10 11:32:02.802: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8
> callref = 0x807F
>
>
> *May 10 11:33:35.062: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8
callref
> = 0x0057
> Sending Complete
> Bearer Capability i = 0x9090A3
> Standard = CCITT
> Transfer Capability = 3.1kHz Audio
> Transfer Mode = Circuit
> Transfer Rate = 64 kbit/s
> Channel ID i = 0xA18383
> Preferred, Channel 3
> Progress Ind i = 0x8283 - Origination address is non-ISDN
> Calling Party Number i = 0x0083, 'calling party number'
> Plan:Unknown, Type:Unknown
> Called Party Number i = 0x81, 'called party number'
> Plan:ISDN, Type:Unknown
> *May 10 11:33:35.086: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8
> callref = 0x8057
> Channel ID i = 0xA98383
> Exclusive, Channel 3
> *May 10 11:33:35.086: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8
> callref = 0x8057
> Cause i = 0x80A2 - No circuit/channel available
>
> In attachment I include a file (copy of ccm00000065.txt) that has the
> relevant information taken from a CCM Trace log and run through Voice
> Log Translator.
>
> With all this information I went to check the MGCP Gateway
configuration
> in CCMAdmin. Some of the configuration elements included on the E1
> endpoint configuration page and that are somewhat confusing me (mind
you
> that this is an inherited configuration) are as follows:
>
> Channel Selection Order: BOTTOM_UP (since the configuration on the
> gateway's interface Serial0/0/0:15 is for bchan-number-order
ascending,
> shouldn't these parameters match by using the TOP_DOWN option?)
>
> Channel IE Type: Use Number When 1B (This is an option that I don't
> fully understand. Any help on this would be appreciated. But to what I
> understand, and since the E1 PRI configuration is only used for half a
> primary (15 channels) shouldn't this parameter be set to 'Timeslot
Number'?)
>
> TIA
>
>
> --
> Pedro Miguel Marques
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
More information about the cisco-voip
mailing list