'Nailing Down' TDM / IP Endpoints
Discussion
This article describes how to make a fixed assigment of specific TDM ports or channels on a Dialogic DMG 1000-series or DMG 2000-series Media Gateway to specific IP endpoints, as well as fixing specific IP endpoints to specific TDM channels.
For example, to nail a specific PBX port (e.g. extension 221) to a specific IP endpoint (IP telephone or IP soft-phone, for example 192.168.1.30) and vice-versa.
This article describes the basics requirements for accomplishing this type of routing using V6.0.128 software.
The PBX integration used in the following examples was Nortel Norstar MICS 0x32.
Nailing Down Inbound TDM Ports to a Specific IP destination (IP phone)
Create a VOIP Host Group that points to each of the IP phones that you want to send calls to.
Add a host group name (or change the default entry). You can use the person’s name that the calls will be going to as well as the IP phones extension (e.g. 239 - Dave Bergquist - .30).
Leave Load-Balanced and Fault Tolerance set to false
Add the IP address of the IP phone in the Host List box
Click on Submit at the bottom of the page.
Create the TDM trunk groups for each port. Create a trunk group for each channel connected to the gateway.
Click on Add Trunk Group
Change the name to match the port / user (e.g. if port 1, extension 221 is going to Dave Bergquist, name it “221 – Dave Bergquist”.
Selection Direction and Selection Mode can remain unchanged.
Under Port/Channel Content, assign a port to each user. This designates the port that is used for each trunk group for incoming and outgoing calls (specified later).
Create an Inbound TDM Rule that points to each of the VoIP Endpoints that you just created. This rule takes calls that are intended for extension 221, and routes them to the IP endpoint 221@xxx.xxx.xxx.xxx
Click on Add Rule and give the new rule a label (e.g. 221 – Dave Bergquist).
Set Request Type to 'any'
Trunk group needs to be configured to match the port assigned to this user. So in the example below, extension 221 – Dave Bergquist should point to the trunk group created for port 1. So now if calls come in on port 1, it will be routed to its VoIP endpoint for this user.
You do not need to create any CPID Matching Rules.
For outbound routes, set the Outbound Destination to VoIP
For the Host Group, select the VoIP host group that was created in step 1a.
You do not need to create any CPID manipulation rules (use as needed).
Nailing down VoIP Endpoints to a Specific TDM Extension Number / Channel
Using the TDM Trunk Groups that were created in step 2 above, you need to create Inbound VoIP rules for each IP endpoint that will be placing calls internally and externally to the PBX. For example, calls that come in from VoIP user 221@xxx.xxx.xxx.xxx and you want them to go to another user on or off switch.
Click on Add Rule. Start by labeling the rule with the first user's information (e.g. 221 – Dave Bergquist)
Request type is set to 'any'.
Originating VoIP Host Address has to be set to the VoIP user's IP address. If this is set incorrectly, the VoIP call coming into the DMG may not route, or be routed incorrectly. This is what allows the VoIP call to hit the correct rule.
Under CPID matching, put in the calling extension number of the VoIP user (must match the From Header of the Invite).
Under Outbound Routes, Device Selection, Outbound Destination, select TDM
Under Trunk Group, select the user’s trunk port. (e.g. 221 – Dave Bergquist Port 1).
Click on Submit.