Definity G3 PBX R6 Cisco Call Manager DCS and UDP

[CiscoIPTelcoGuy]

This question is for Buckweet or anyone else who can help resolve this. I am installing a Cisco Call Manager and connecting it to a Definity G3 PBX using a DS1 circuit pack connected to a 6608 T1 (PRI) gateway.

Right now the trunk link is up and configured using B8ZS and ESF and ATT 5ESS. The protocol side is user and on the Definity side its network.

If I create extensions that are not in the dial-plan of the definity, the definity is using udp with 4-digit extensions, I can route calls using the route pattern to extensions on the pbx and through the pbx to the pstn. However, what I really want to accomplish is to be able to share the dial plan between the two switches.
I really want to be able to pull extensions off the definity and program and register them on the call manager.
I don't want to have to change the ars table on the definity or the route plan to isolate blocks of extensions and then register them to the call-manager.
Also I don't want to have to dial a fac to route the calls to the call-manager. I want users to be able to transparently dial a 4 digit extension and reach the call manager and vice versa.

 

[lopes1211]

I'm not sure I understand the question since the transparent way is to use UDP which you say you've already done. You have to update the UDP table when extensions move between the 2 PBX's. If you aren't networked with anything else, a workaround could be to define all extensions in the PBX UDP table to point to the Cisco. On the "change dialplan" form you can set "UDP extension search order" to "local-extensions-first". In this scenario, whenever an extension is dialed, the Definity looks for it in the Definity, if it's not found, it then searches the UDP table. If you've defined the UDP table to point EVERYTHING to the Cisco, it sounds like it will do what you want. You'll need Buckweet for ideas on the Cisco side. Keep in mind that this config will only work while you're not networked to anything else. If so, the next PBX you network with will need it's own range of extensions but the Cisco-Definity part will continue to work the same. -CL

 

[CiscoIPTelcoGuy]

The definity g3 pbx is connected to two other definity g3 pbx's. The PBX's are using udp and have udp codes to route calls to extensions on the other pbx's via a trunk route pattern.

My question is if I remove a station from the pbx say an extension that is 4-digit 6648. If i configure a udp extension in the pbx to route to a route pattern will this get me to the call-manager.

 

[lopes1211]

Yes, UDP will function fine no matter what you route to. Call Manager, fax server, video conf, ras, etc makes no difference. Definity to Definity gives you some extra's as far as networking but UDP call routing work great no matter what you integrate with. Just add a UDP entry for the Cisco just like the ones are setup for the other Definity's. -CL

 

[CiscoIPTelcoGuy]

There is no where on the call manager side for me to identify the call-manager pbx with a udp code.

Can you give me an example of a udp extension for example 6648 and how you would configure that in the definity to route to a a trunk-group 99.

 

[lopes1211]

Do a "list aar analysis" and paste the 1st page of results to start with. Then we can walk you through a little easier. -CL

 

[CiscoIPTelcoGuy]

How does aar analysis route the udp call. I can dial the tac code for the trunk-group and reach the trunk or I can put a feature code and get to the trunk, however I dont' want users to have to know if the extensions are on the call manager and if they have to dial a code or not.

Essentially the problem or the configuration issue I need to have resolved is how to bind a trunk-group to a udp code. Is this in the route-pattern, is it in the trunk-group configuration.

 

[lopes1211]

I wanted to see your existing aar table so I wasn't just speaking in generalizations but here I go. You essentially create a UDP code. Let's say 222. Enter 222 in the UDP table for all of the extensions you need to go to the Cisco. Do a change "aar analysis 222". Assuming it's not already used, add the entry 222 min7 max7 assuming 4-digit extensions, call type aar, and point it to a route pattern. The route pattern will use the Cisco trunk group as it's 1st choice and delete 3-digits. What happens is.....user dials 1234. The Definity looks for ext 1234. When it doesn't find it, it searches the UDP table. If 1234 is in the table with a UDP code (lets say 222) the PBX prefixes the 222 onto the call and becomes 222-1234. The aar analysis table looks for routing choices for a 222-xxxx call where the call is pointed to a route pattern. The route pattern deletes 3 digits (the 222) and sends 1234 to the Cisco. -CL