Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Inbound Call - Unallocated number error with digit change

Status
Not open for further replies.

dudecrush

IS-IT--Management
Apr 2, 2007
468
US
Hello - I've got Call Manager 9.1, and I've got something perplexing me...

I have two locations - a West Towne (location dial prefix 016) and a Middleton (location dial prefix 011). Middleton is a Slave to West Towne, meaning that it get's it's phone numbers from the West Towne DID's. West Towne is an MGCP gateway, while Middleton is H.323.

I have a DID block into West Towne: XXX-829-2272 to 2280. I want to convert XXX-829-2278 (0162278 in Call Manager) into 0112278 for use in Middleton.

When I place 0162278 on a test phone, it rings fine. When I convert it to 0112278, I get an "Unallocated Number" error on the router, and a "Number no longer in service" message that plays from the phone co.

Clearly, I'm missing something but I'm not clear as to what. I would think the dialed number analyzer would send the call to 0112278 since it's the closet match. I thought this might be a missing translation pattern, but there is a translation pattern with the config 011#. (discard pre-dot). I thought it might perhaps be the dial peers, but we are doing the same thing with other converted numbers and have no problems.

Here is the failed call output from the West Towne...

Apr 5 12:12:07: ISDN Se0/1/0:23 Q931: RX <- SETUP pd = 8 callref = 0x3D52
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x2183, '6xx23x2022'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '2278'
Plan:Unknown, Type:Unknown
Apr 5 12:12:08: ISDN Se0/1/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xBD52
Cause i = 0x8081 - Unallocated/unassigned number

Any ideas?
 
I would create a translation pattern of xxx-829-2278 or whatever your DID scheme is coming in, to the 0112278.

Certifications:
A+
Network+
CCENT
CCNA Voice
TVOICE
CAPPS
 
That's funny, because I did actually do that. I created translation pattern 011.2278 (strip anything pre-dot), which I though for sure would work but it didn't. THe west towne gateway is set to prefix any call with 016, with 4 significant digits. However, the router output shows 016 stripped off as the prefix DN, leaving me with 4 significant digits - 2278. So I'm wondering who is stripping the digits? The gateway (router) or the translation pattern (call manager)? I'm guessing the translation pattern, but why doesn't RTMT find the call - even if it failed? So my thought is the gateway is doing this. That's why I'm confused.
 
If I understand correctly you have 011.2278 translating to 0162278? That should work assuming it is hitting that. There might be something else in play. DNA would show you all matches. If nothing else is in play then most likely the gateway is stripping it.

Certifications:
A+
Network+
CCENT
CCNA Voice
TVOICE
CAPPS
 
gnrslash4life: Other way around - 0162278 to 0112278. When I changed DN 0162278 to 0112278, I expected DNA to find the closest match and send the call to the DN. I was missing a step.

After a TAC call, I figured it out. The problem was the way I thought the call flow worked.

I thought this was happening: Outside Caller >> Gateway - GW adds prefix >> CUCM >> Translation Pattern - translation pattern strips prefix >> CM Can't Find Number >> Sends Call back to GW.

I thought this because When I saw "Called Party Number i = 0x80, '2[highlight #FCE94F]278[/highlight]'", on the gateway with no dial prefix assigned, I'd assumed this was coming back from CUCM after the prefix was stripped. I couldn't understand why it couldn't find 0112278 even though it was in CUCM.

In reality, this is what was happening: Outside Caller >> Gateway >> Call stopped at Gateway.

The number 2278 wasn't coming back from CUCM at all. There was no DN with 0162278, so the GW assigned no prefix and the call died there.

What I needed to do was create a special translation pattern:
016.2278 > Strip 016 (Pre-dot) > prefix outgoing calls with 011

This, in turn, sends the call to 0112278.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top