[cisco-voip] "Resource unavailable, unspecified" from CallManager (solved!)
Andrius Kislas
andrius-conf at elsis.lt
Fri Nov 24 08:54:48 EST 2006
I have sent debugs, but files were too big and still waiting for
moderator approval :).
The problem is solved.
The source of this problem was very unusual. I had a wrong .1q
configuration on this router. As far as I know 10 mbps eth interfaces do
not support trunking. But this router allowed me to configure
subinterfaces. But it didn't allow me to place "h323-gateway voip"
commands in the subinterface. So I had to use Ethernet0/0 for these
commands. So this wrong configuration led to the "resource unavailable"
disconnect from CM. Now I've removed subintarfaces and it works correct.
Andrius
Rodrigo Villagran wrote:
> could you send a degub of a sucessfull call??? the call for a region its
> tryn to use g729 instead of g711 in the CM??
> what do you mean with:
> "Looking at h225 debug and comparing successful with unsuccessful call, I
> can see that router is not sending any capabilities to CallManager!!" the
> router not send capabilities to CM??
>
> where the number 2106 its?? behind a router??
>
> greetings
> Rodrigo
>
> -----Mensaje original-----
> De: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net]En nombre de Andrius Kislas
> Enviado el: Jueves, 23 de Noviembre de 2006 14:30
> Para: cisco-voip at puck.nether.net
> Asunto: [cisco-voip] "Resource unavailable, unspecified" from
> CallManager
>
>
> Hi,
>
> I have a problem that I cannot solve myself. Asking for your help.
>
> CCM 4.1(3) is calling to Cisco 2610 H.323 router. Router is connected to
> PBX using BRI lines. q931 debug shows me:
>
> ISDN BR1/0: TX -> SETUP pd = 8 callref = 0x34
> Bearer Capability i = 0x9090A3
> Channel ID i = 0x89
> Calling Party Number i = 0x01, 0x81, '7095', Plan:ISDN,
> Type:Unknown
> Called Party Number i = 0x81, '2106', Plan:ISDN, Type:Unknown
> Sending Complete
> ISDN BR1/0: RX <- CALL_PROC pd = 8 callref = 0xB4
> Channel ID i = 0x89
> ISDN BR1/0: RX <- ALERTING pd = 8 callref = 0xB4
> Progress Ind i = 0x8582 - Destination address is non-ISDN
> ISDN BR1/0: RX <- CONNECT pd = 8 callref = 0xB4
> Connected Number i = 0x098032313036
> ISDN BR1/0: TX -> CONNECT_ACK pd = 8 callref = 0x34
> %ISDN-6-CONNECT: Interface BRI1/0:1 is now connected to 2106
> %ISDN-6-DISCONNECT: Interface BRI1/0:1 disconnected from 2106 , call
> lasted 5 seconds
> ISDN BR1/0: TX -> DISCONNECT pd = 8 callref = 0x34
> Cause i = 0x82AF - Resource unavailable, unspecified
>
>
> I get _"Resource unavailable, unspecified"_ from CallManager.
> Troubleshooting docs say that mostly this is the problem with codec
> mismatch. I have doublechecked and played with "Regions" alot. Tried
> G711 and G729. Nothing helped. After comparing successful and
> unsuccessful calls' detailed traces, I can see these strings in
> CallManager's trace:
>
>
> MediaManager(88365) - prepareInitialConnectionList, Party1CapCount=5
> Party2CapCount=0
> <...>
> LogicalChannels - getLCN: failed to get LCN based on mediaType
> |<CLID::StandAloneCluster><NID::10.196.1.2>
> MediaManager(88365) - wait_AuConnectErrorInd - send disconn to 1
> MXs|<CLID::StandAloneCluster><NID::10.196.1.2><CT::2,100,87,89019.1><IP::><D
> EV::>
> MediaManager(88365) - wait_AuConnectErrorInd - remain
> mConnCount=1|<CLID::StandAloneCluster><NID::10.196.1.2><CT::2,100,87,89019.1
>> <IP::><DEV::>
> MediaManager(88365) - wait_AuConnectErrorInd - only 1 MX reported
> error...going
> away.|<CLID::StandAloneCluster><NID::10.196.1.2><CT::2,100,87,89019.1><IP::>
> <DEV::>
> MediaCoordinator -
> wait_AuConnectErrorInd|<CLID::StandAloneCluster><NID::10.196.1.2><CT::2,100,
> 87,89019.1><IP::><DEV::>
> MediaCoordinator - wait_AuConnectErrorInd - removing MediaManager(88365)
> from connection
> list|<CLID::StandAloneCluster><NID::10.196.1.2><CT::2,100,87,89019.1><IP::><
> DEV::>
>
> I think the important part is "Party2CapCount=0".
>
> Looking at h225 debug and comparing successful with unsuccessful call, I
> can see that router is not sending any capabilities to CallManager!!
>
> Inbound and outbound dial-peers are these:
>
>
> dial-peer voice 10000 voip
> corlist incoming In-FromCM
> incoming called-number .
> voice-class codec 99
> !
>
> dial-peer voice 50000 pots
> corlist outgoing Out-FromCMandSRST
> destination-pattern 21..
> progress_ind alert enable 8
> port 1/0/0
> forward-digits all
>
> where voice class is:
> voice class codec 99
> codec preference 1 g729r8
> codec preference 2 g729br8
> codec preference 3 g711alaw
> codec preference 4 g711ulaw
> !
>
>
> Does anyone have experience with such situation. Probably router thinks
> it can't handle any codec. Why? What other debug or show commands can be
> useful for me?
>
> Here is BRI and DSP information:
> interface BRI1/0
> no ip address
> isdn switch-type basic-net3
> isdn overlap-receiving
> isdn protocol-emulate network
> isdn layer1-emulate network
> isdn incoming-voice voice
> isdn sending-complete
> isdn static-tei 0
> !
> interface BRI1/1
> no ip address
> isdn switch-type basic-net3
> isdn overlap-receiving
> isdn protocol-emulate network
> isdn layer1-emulate network
> isdn incoming-voice voice
> isdn sending-complete
> isdn static-tei 0
>
>
> xxxxxxx#show voice dsp
>
> DSP DSP DSPWARE CURR BOOT PAK
> TX/RX
> TYPE NUM CH CODEC VERSION STATE STATE RST AI VOICEPORT TS ABORT
> PACK COUNT
> ==== === == ======== ======= ===== ======= === == ========= == =====
> ============
> C542 001 01 g711ulaw 3.4.52 IDLE idle 0 0 1/0/0.1 NA 0
> 21873/22762
> C542 002 01 g711ulaw 3.4.52 IDLE idle 0 0 1/0/0.2 NA 0
> 534/571
> C542 003 01 g711ulaw 3.4.52 IDLE idle 0 0 1/0/1.1 NA 0
> 21660/21721
> C542 004 01 g711ulaw 3.4.52 IDLE idle 0 0 1/0/1.2 NA 0
> 533/530
>
> If needed, I have detailed CallManager traces, ccapi inout debug, h225
> debug.
>
> Any help would be greatly appreciated!
> Andrius
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
More information about the cisco-voip
mailing list