Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Outgoing Translation Pattern

I have a translation set to 9.1847.xxxxxxx . this is for outgoing calls to area code 847. Our primary # and all of our facilities are in the 847 area code and we must dial the area code even when calling locally. When I try to dial a number, 847-879-8500, I get a fast busy signal. Any other 847 number works, it seems it's just this one number that isn't working. Any idea on where to start troubleshooting?

Thanks.

21 REPLIES
Blue

Re: Outgoing Translation Pattern

try to find out on what digit the call is going to fast-busy.

put the phone on speaker-phone. dial the numbers one at a time so you can clearly hear the fast-busy when the digit that invokes it is pressed.

if it is the last digit, then you may be 'stepping on the dialPlan'. a term used to state that the dialPlan has inconsistencies.

if it is not the last digit, you may have a bad xlation pattern or it may be stepping on the dialPlan. doesn't sound like it but i'm not sure since i can't see your dialPlan.

also, you may want to try to use CalledPartyMask on a phone for testing, instead of the xlation pattern. see if this gives you the same symptoms.

the best thing to do first though is to determine what digit the fast-busy is being invoked by.

let us know the results and any other symptoms.

also, is 847.897.8500 a shared line? is it in a huntGroup? is it part of an attendentConsole or the likes? is it just one DN on one users phone?

Re: Outgoing Translation Pattern

847.897.8500 is an outside number to a vendor of ours, it should route out to the PSTN.

the busy signal is on the last digit

Re: Outgoing Translation Pattern

Still having trouble with this. Need some assistance to find out why only this number cannot be dialed, but any other 847-xxx-xxx works. very strange.

Re: Outgoing Translation Pattern

we have an 85xx translation pattern w/ a 1500 Called Party Transform Mask. 1500 is our main number, perhaps this is causing the problem?

Re: Outgoing Translation Pattern

Take CCM detailed traces from both calls and take a look to the digit analysis.

HTH

//Jorge

Re: Outgoing Translation Pattern

not quite sure how to do all that. I found the CCM trace logs, but not sure how to do digit analysis.

is there a way to set this outgoing pattern to just straight dial 847-879-8500 or just create a new one to match each digit dialed?

Re: Outgoing Translation Pattern

debug isdn q931

debug isdn q931 is ON.

*Mar 1 00:23:09.911: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0025

Bearer Capability i = 0x8090A2

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98397

Exclusive, Channel 23

Calling Party Number i = 0x21, 0x81, '8479297151'

Plan:ISDN, Type:National

Called Party Number i = 0x80, '18478798500'

Plan:Unknown, Type:Unknown

*Mar 1 00:23:10.015: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8025

Cause i = 0x80A2 - No circuit/channel available

W3662-01#

*Mar 1 00:23:10.019: ISDN Se1/1:23 Q931: TX -> SETUP pd = 8 callref = 0x0026

Bearer Capability i = 0x8090A2

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98397

Exclusive, Channel 23

Calling Party Number i = 0x21, 0x81, '8479297151'

Plan:ISDN, Type:National

Called Party Number i = 0x80, '18478798500'

Plan:Unknown, Type:Unknown

*Mar 1 00:23:10.127: ISDN Se1/1:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8026

Cause i = 0x80A2 - No circuit/channel available

Bronze

Re: Outgoing Translation Pattern

Looks like you don't have any available B-channels for this number. Could be all your B-channels are in use. Also can you post your dial-peers config and channels status.

Can you dial that number from cell phone to see if is a valid number.

New Member

Re: Outgoing Translation Pattern

Have you tried using the Dialed Number Analyzer to verify that calls to the problematic number actually follow the same path and use the same gateway/trunk as calls to other numbers in the same area code? It sure looks to me like it is being treated differently if it's only that one number that is having a problem.

Re: Outgoing Translation Pattern

I do not have dialed number analyzer, running CCM 3.3(2). is there a way to install DNA?

Re: Outgoing Translation Pattern

config attached

dialing from a cell phone works, the # is valid.

Re: Outgoing Translation Pattern

try to set calling party Plan and Type

to unknown.

(are you using H323 or MGCP?)

Re: Outgoing Translation Pattern

Using H323

Re: Outgoing Translation Pattern

I think this is already set

Called Party Number i = 0x80, '18478798500'

Plan:Unknown, Type:Unknown

*Mar 1 00:23:10.127: ISDN Se1/1:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8026

Cause i = 0x80A2 - No circuit/channel available

Silver

Re: Outgoing Translation Pattern

I don't think you should need the 1 if you are calling in the same area code, maybe there is something weird about the office interconnect for where this number goes, maybe you could try stripping the 1 - you could maybe do a specific route pattern for that one number, so you don't affect anything else. We have had trouble with calling individual numbers occasionally, I don't remember the clear we got, but the called party did not accept calls without cid, and we were not sending any. The no ckt/channel available seems very strange, unless it is getting passed back to you by the CO that leaving him, he has no path.

Mary Beth

Re: Outgoing Translation Pattern

Hi,

The number you are trying to call is of : Infinity Monitoring - right?

Try calling another number of their's and see if that works. Will it be possible for you to collect the output of a successfull call to any other 847 area code number (or another number of Inf Monitoring) and a failed call to this particualr number? If yes, please post the output here and let's see if we can find something.

If you say that other calls to the same area code work, then I dont think it's an issue with the Plan and Type. This company seems to be in IL. Are you in the same state?

Regards,

Suman Bhattacharya

Re: Outgoing Translation Pattern

Correct on Infinity monitoring.

We are in the same state (IL). The 847 area code requires users to dial 847 even if they reside within the same area code.

I posted the error we receive when trying to call Infinity in a response a few posts up, its attached as a file.

Calling a cell phone 847 yields the following:

*Mar 6 22:42:01.396: ISDN Se1/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0x8E9F

Cause i = 0x82FF - Interworking error; unspecified

Progress Ind i = 0x8281 - Call not end-to-end ISDN, may have in-band info

*Mar 6 22:42:02.336: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0EA0

Bearer Capability i = 0x8090A2

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98392

Exclusive, Channel 18

Calling Party Number i = 0x21, 0x81, '8479297151'

Plan:ISDN, Type:National

Called Party Number i = 0x80, '18477028000'

Plan:Unknown, Type:Unknown

W3662-01#

*Mar 6 22:42:02.648: ISDN Se1/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8EA0

Channel ID i = 0xA98392

Exclusive, Channel 18

W3662-01#

*Mar 6 22:42:03.796: ISDN Se1/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x8E9F

*Mar 6 22:42:03.796: ISDN Se1/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0E9F

*Mar 6 22:42:03.908: ISDN Se1/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x8D83

*Mar 6 22:42:03.948: ISDN Se1/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0D83

*Mar 6 22:42:04.596: ISDN Se1/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x038E

Cause i = 0x8090 - Normal call clearing

*Mar 6 22:42:04.600: ISDN Se1/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x838E

*Mar 6 22:42:04.648: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x038E

W3662-01#

*Mar 6 22:42:04.696: ISDN Se1/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x8E9E

*Mar 6 22:42:04.696: ISDN Se1/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0E9E

W3662-01#

*Mar 6 22:42:06.596: ISDN Se1/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0x8EA0

Progress Ind i = 0x8288 - In-band info or appropriate now available

W3662-01#

*Mar 6 22:42:12.348: ISDN Se1/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x8EA0

*Mar 6 22:42:12.348: ISDN Se1/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0EA0

W3662-01#

*Mar 6 22:42:14.696: ISDN Se1/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x16D1

Cause i = 0x8090 - Normal call clearing

*Mar 6 22:42:14.696: ISDN Se1/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x96D1

*Mar 6 22:42:14.748: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x16D1

*Mar 6 22:42:15.540: ISDN Se1/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x0EA0

Cause i = 0x8090 - Normal call clearing

W3662-01#

*Mar 6 22:42:15.796: ISDN Se1/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x8EA0

*Mar 6 22:42:15.796: ISDN Se1/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0EA0

W3662-01#

*Mar 6 22:42:17.344: ISDN Se1/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x0E9F

Cause i = 0x8090 - Normal call clearing

*Mar 6 22:42:17.596: ISDN Se1/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x8E9F

*Mar 6 22:42:17.596: ISDN Se1/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0E9F

Re: Outgoing Translation Pattern

If you are in the same state, why are we using the preceeding 1 in the number we are trying to dial?

Normally all servie providers accept 1 for long distance calls.

So, just try to modify the route pattern in Callmanager and specify just the number starting with the area code (do not use 1) and dial only the phone number and see how that works.

Regards,

Suman Bhattacharya

Re: Outgoing Translation Pattern

I have done that with no luck. Residents within the 847 area code, MUST dial 1+847 even when dialing a local number within the same area code. It has to do with an FCC mandated overlay (http://64.233.167.104/search?q=cache:YHaNXTCUtHQJ:www.areacode-info.com/headline/2002/il020208.pdf+847+area+code+and+dialing+1&hl=en&gl=us&ct=clnk&cd=3)

I am clueless as to why only this one number is not getting through.

Thank you for your responses.

Re: Outgoing Translation Pattern

Still no luck with this, is there anything else to check?

Re: Outgoing Translation Pattern

Can you post the gateway configuration?

Did you call the service provider and discuss this with them? Tell them that after you dial this number, you are receiving a "No Channel/Circuit Available" message.

Regards,

Suman

364
Views
0
Helpful
21
Replies