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. And see here for current known issues.

New Member

Internal calls not completing to CCM 6 w/MGCP PRI gateway

I cut our CCME environment over to a CCM 6.0 system today, and I am having a really hard time getting inbound DID working.

The CCM is connected to the PSTN with a PRI through a 2821 MGCP gateway. Outbound calls are working fine, even passing the correct CLID digits that I programmed in the External Phone Number Mask for each DN.

The problem is, I cannot get incoming calls working at all. Whenever I call one of my DID numbers, I get a canned "You have reached a non-working number" message which I think is coming from the CO after the CCM rejects the call.

I have been going through the CUCM6 System Guide and CUCM6 Admin Guide to no avail.

How do you configure incoming DID in this type of system? Unfortunately, our DID numbers do not match any digits with their extensions, so the external phone number masks are set to the DID number. This gets passed correctly as CLID on outbound calls.

Please let me know if I haven't provided enough information. :)

Thanks,

Chris

3 REPLIES
New Member

Re: Internal calls not completing to CCM 6 w/MGCP PRI gateway

Here is output from 'debug idsn q931' on the gateway for a successful outbound call, and then the unsuccessful inbound call between the same two devices:

Here is the successful outbound call:

000627: Nov 3 16:45:04.586 Pacific: ISDN Se0/3/0:23 Q931: TX -> SETUP pd = 8 c

allref = 0x0002

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Net Specific Fac i = 0x00F3

Calling Party Number i = 0x0181, '2424020'

Plan:ISDN, Type:Unknown

Called Party Number i = 0x80, '5706441'

Plan:Unknown, Type:Unknown

000628: Nov 3 16:45:04.886 Pacific: ISDN Se0/3/0:23 Q931: RX <- CALL_PROC pd =

8 callref = 0x8002

Channel ID i = 0xA98381

Exclusive, Channel 1

000629: Nov 3 16:45:05.582 Pacific: ISDN Se0/3/0:23 Q931: RX <- PROGRESS pd = 8

callref = 0x8002

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

000630: Nov 3 16:45:13.106 Pacific: ISDN Se0/3/0:23 Q931: TX -> DISCONNECT pd =

8 callref = 0x0002

Cause i = 0x8090 - Normal call clearing

000631: Nov 3 16:45:13.142 Pacific: ISDN Se0/3/0:23 Q931: RX <- RELEASE pd = 8

callref = 0x8002

000632: Nov 3 16:45:13.158 Pacific: ISDN Se0/3/0:23 Q931: TX -> RELEASE_COMP pd

= 8 callref = 0x0002

And here is the failed incoming call:

000624: Nov 3 16:44:25.986 Pacific: ISDN Se0/3/0:23 Q931: RX <- SETUP pd = 8 c

allref = 0x0015

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Calling Party Number i = 0x2183, '5095706441'

Plan:ISDN, Type:National

Called Party Number i = 0xC1, '2424020'

Plan:ISDN, Type:Subscriber(local)

000625: Nov 3 16:44:25.994 Pacific: ISDN Se0/3/0:23 Q931: TX -> RELEASE_COMP pd

= 8 callref = 0x8015

Cause i = 0x8081 - Unallocated/unassigned number

** on a completely unrelated note, it looks like I need to change the outbound B-channel allocation to bottom-up since inbound calls are using top-down.

New Member

Re: Internal calls not completing to CCM 6 w/MGCP PRI gateway

I believe I have resolved this issue. I created a translation pattern that translates 2424020 to 200. Now internal ext. 200 rings when a call is placed to 2424040. That is exactly what I wanted.

So, is this the correct way to do DID/DOD when your DID numbers and extensions don't match digits? Use the External Phone Number mask for passing the CLID outbound and use a Translation Pattern for routing inbound calls?

Thanks,

Chris

Re: Internal calls not completing to CCM 6 w/MGCP PRI gateway

This largely depends on the complexity of your dialplan and the range of incoming digits or DDI ranges on the voice port.

For example if you have only a single number incoming as you have described above, you can configure the gateway to have 0 significant digits and configure the prefix DN to be 200. You will just need to ensure that the MGCP gateway CSS can call 200.

However if you have a branch network with multiple gateways, then I would recommend being consistent and configure each branch digit transformations in the same manor.

It is not always as straight forward as in your case, and the DID will not always match your dial-plan. For example you main have several completely different numbers incoming on your gateway therefore translation patterns is the only way forward.

You need to be cautious about overlaping translations when you have multiple MGCP gateways.

It this instance, you will need to configure a different partion for each gateway and assign this to your translation pattern. Then configure a unique gateway css which includes this translation pattern partition.

This will ensure that only the incoming digits on this gateway are matched against the specific translation pattern.

For example if you have two gateways both with the same incoming number 242020, then one translation pattern can be configured to translate to 200 and another to 300. Because translation is assigned to a different partion these can be assigned to the respective gateway css.

Regards

Allan.

Please rate helpful posts.

279
Views
0
Helpful
3
Replies