[cisco-voip] Cisco Channel Usage question
Joseph Mays
mays at win.net
Wed Mar 12 15:44:27 EDT 2008
Here is the config for the controller I am trying to hit a specific DS0 on.
controller T1 1/0:5
framing sf
ds0-group 0 timeslots 1-24 type e&m-fgb mf dnis
description Greenwood POP Trunk3 - (479) 546-0000
----- Original Message -----
From: "Wes Sisk" <wsisk at cisco.com>
To: "Joseph Mays" <mays at win.net>
Cc: <cisco-voip at puck.nether.net>
Sent: Wednesday, March 12, 2008 3:26 PM
Subject: Re: [cisco-voip] Cisco Channel Usage question
> Joseph,
>
> controller T1 1/0/0:1
> shutdown
> framing sf
> ds0-group 0 timeslots 1-24 type e&m-fgb mf dnis
> !
> controller T1 1/0/0:2
> shutdown
> framing sf
> ds0-group 0 timeslots 1-24 type e&m-fgb mf dnis
> !
>
> For this example you would have to break out the ds0-group into multiple
> ds0-groups. With that you get one voice port per ds0-group. With that
> you get granularity down to ds0 level.
>
> /Wes
>
> Joseph Mays wrote:
>> Actually, I think I figured it out. I'm trying to figure out why calls
>> to 800 numbers aren't working (gets a "call cannot be completed as
>> dialed" message). I thought the problem was a telco configuration
>> problem, but in talking with them, when they were asking me to send
>> the call across specific channels, that's what showed up when I was
>> tracking the call to see if it the right channel. They immediately
>> said that was evidence the AS5400 was configured wrongly.
>>
>> In fact, testing shows that you always get that channel number when a
>> call is not completed. Dial a number that works and hang up while it's
>> ringing, before the other end answers, and here's what you'll see --
>>
>> 025533: Mar 12 11:57:00.883 CST: %CALLTRKR-6-CALL_RECORD:
>> ct_hndl=7497, service=None, origin=Originate, category=Other, DS0
>> slot/port/ds1/chan=-1/-1/-1/-1, called=4796388094, calling=5460015,
>> resource slot/port=(n/a)/(n/a), userid=(n/a), ip=0.0.0.0,
>> mask=0.0.0.0, account id=(n/a), setup=03/12/2008 11:56:33, conn=0.00,
>> phys=0.00, service=0.00, authen=0.00, init-rx/tx b-rate=0/0, rx/tx
>> chars=0/0, time=10.63, disc subsys=CSM, disc code=0x2, disc
>> text=Received an unexpected onhook event
>>
>> Call the exact same number, let the other end answer, and you get --
>>
>> 025520: Mar 12 11:48:49.191 CST: %CALLTRKR-6-CALL_RECORD:
>> ct_hndl=7494, service=None, origin=Originate, category=Other, DS0
>> slot/port/ds1/chan=1/0/5/5, called=4796388094, calling=5460015,
>> resource slot/port=(n/a)/(n/a), userid=(n/a), ip=0.0.0.0,
>> mask=0.0.0.0, account id=(n/a), setup=03/12/2008 11:48:11, conn=24.72,
>> phys=0.00, service=0.00, authen=0.00, init-rx/tx b-rate=0/0, rx/tx
>> chars=0/0, time=28.19, disc subsys=CSM, disc code=0x2, disc
>> text=Received an unexpected onhook event
>>
>> So I still think the issue is a telco switch problem. The bogus
>> channel assignment is just showing up because calls aren't being
>> completed.
>>
>> Followup question. Can I direct a call to a specific ds0 channel by
>> referencing it in the target. So if I want to direct the call to, say,
>> the last channel of the DS1, would ....
>>
>> dial-peer voice 8800 pots
>> destination-pattern 800.......
>> no digit-strip
>> port 1/0:5:23
>>
>> ... work?
>>
>>
>> ----- Original Message ----- From: "Wes Sisk" <wsisk at cisco.com>
>> To: "Joseph Mays" <mays at win.net>
>> Cc: <cisco-voip at puck.nether.net>
>> Sent: Wednesday, March 12, 2008 1:43 PM
>> Subject: Re: [cisco-voip] Cisco Channel Usage question
>>
>>
>>> Joseph,
>>>
>>> Actually 'voip ccapi inout' may not be a good idea on a gateway of
>>> your scale. At this point I'd say open a TAC case for more granular
>>> investigation.
>>>
>>> /Wes
>>>
>>> Wes Sisk wrote:
>>> Hi Jospeh,
>>>
>>> Yep, that was misread on my part, no COR. Sorry. Need to see the debug
>>> voip ccapi inout and config for the voice port.
>>>
>>> /wes
>>>
>>> Joseph Mays wrote:
>>> There do not seem to be any corlists defined.
>>>
>>> nas01#show run | include cor
>>> calltracker call-record terse
>>> spe call-record modem
>>> dial-peer cor custom
>>> nas01#show run | include custom
>>> resource-pool profile customer Greenwood
>>> resource-pool profile customer Hackett
>>> resource-pool profile customer Fax
>>> resource-pool profile customer NullDNIS
>>> resource-pool profile customer interoffice
>>> dial-peer cor custom
>>> nas01#
>>>
>>>
>>> ----- Original Message ----- From: "Wes Sisk" <wsisk at cisco.com>
>>> To: "Joseph Mays" <mays at win.net>
>>> Cc: <cisco-voip at puck.nether.net>
>>> Sent: Wednesday, March 12, 2008 12:16 PM
>>> Subject: Re: [cisco-voip] Cisco Channel Usage question
>>>
>>>
>>> I see you have a COR list applied. Is the incoming peer/outgoing
>>> peer permitted by the COR?
>>>
>>> /Wes
>>>
>>> Joseph Mays wrote:
>>> Wes --
>>>
>>> 'show dial-plan number 8009466382' on the router to see what
>>> you get.
>>> other useful debugs:
>>> debug voip ccapi inout
>>> Thanks for the input. I was using debug voip ccapi inout
>>> before, but
>>> didn't try it in this latest event. I'll give it a shot. I included
>>> the output of 'show dial-plan number 8009466382' in my initial
>>> posting to the list, but I'll put it in again here --
>>>
>>> nas01#show dialplan number 8009466382
>>> Macro Exp.: 8009466382
>>>
>>> VoiceEncapPeer8800
>>> peer type = voice, information type = voice,
>>> description = `',
>>> tag = 8800, destination-pattern = `800.......',
>>> answer-address = `', preference=0,
>>> CLID Restriction = None
>>> CLID Network Number = `'
>>> CLID Second Number sent
>>> source carrier-id = `', target carrier-id = `',
>>> source trunk-group-label = `', target trunk-group-label = `',
>>> numbering Type = `unknown'
>>> group = 8800, Admin state is up, Operation state is up,
>>> incoming called-number = `', connections/maximum = 0/unlimited,
>>> DTMF Relay = disabled,
>>> huntstop = disabled,
>>> in bound application associated: 'DEFAULT'
>>> out bound application associated: ''
>>> dnis-map =
>>> permission :both
>>> incoming COR list:maximum capability
>>> outgoing COR list:minimum requirement
>>> Translation profile (Incoming):
>>> Translation profile (Outgoing):
>>> incoming call blocking:
>>> translation-profile = `'
>>> disconnect-cause = `no-service'
>>> type = pots, prefix = `',
>>> forward-digits default
>>> session-target = `', voice-port = `1/0:5:0',
>>> direct-inward-dial = disabled,
>>> digit_strip = disabled,
>>> register E.164 number with GK = TRUE
>>> fax rate = system, payload size = 20 bytes
>>>
>>> Time elapsed since last clearing of voice call statistics never
>>> Connect Time = 0, Charged Units = 0,
>>> Successful Calls = 2, Failed Calls = 0, Incomplete Calls = 0
>>> Accepted Calls = 0, Refused Calls = 0,
>>> Last Disconnect Cause is "10 ",
>>> Last Disconnect Text is "normal call clearing (16)",
>>> Last Setup Time = 92636869.
>>> Matched: 8009466382 Digits: 3
>>> Target:
>>>
>>> nas01#
>>> _______________________________________________
>>> 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
>>>
> _______________________________________________
> 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