Situation: When setting up an HMP system to be able to route through a Cisco Unified Communications Manager server, there are

several steps to ensure that it routes calls properly between the two systems. This guide walks through setting up the basic routing so that bi-directional routing is possible between the two IP systems using SIP. Reason for this guide: This guide will help setting up basic interoperability between HMP and CUCM servers for the basis of testing this configuration. Instructions: This guide will be using our local CUCM system as a guide, as most CUCMs should have at least the basic components (Device Pools, Calling Search Spaces, etc.) configured. Obviously, additional configuration may be needed if setup is complex. Well, to start off, we need a SIP Trunk Security Profile. You can use a security profile that matches the settings below, but we'll walk you through setting up a simple one to start off. To create the SIP Trunk Security Profile, go to System > Security Profile > SIP Trunk Security Profile. Once the page is loaded, click the "Add New" Button. You should see this screen:

The only setting that needs to be changed from the default is the Outgoing Transport Type. The default is TCP; change this to UDP. Once done, enter in a Name and Description into the trunk for identification purposes (ex. HMP Non-secure Profile), then click "Save". Now that we have a SIP Trunk Security Profile, we'll need to set up a SIP trunk. This trunk will symbolize the virtual connection between the HMP and CUCM system. To do this, log into the CUCM HTTPS interface, then choose Device, then Trunk from the drop down menu. From there, you will see a button labelled "Add New". Two boxes with drop-down values will appear. Choose these following values:

Trunk Type : SIP Trunk (set this first) Device Protocol: SIP (will be the only choice) Once this is done, press Next. You'll see a screen that lists all the parameters of a SIP trunk. We'll start with the Device Information Section. Device Information

Device Name : This is merely a label for the trunk so that it is recognizable when viewing all trunks. Since you may have several trunks, including several HMP trunks, be as specific as possible when labeling the trunk Description: This allows the user to enter more detail about the trunk. Details about location, endpoint resources, even physical location might be a good idea. Device Pool: This field is part of the Cisco Unified Communications Manager's resource organization system. Depending on how complex the CUCM configuration, there may be several. Device Pools share resources such as Music On Hold and Media Termination Points. Be sure you assign your Trunk to the right Device Pool. In this example, we'll be picking the only one we have, which is Big House Device Pool. Common Device Configuration: This is only used if setting up multiple devices of the same type with the same settings. Since we are not, this is set to "None"

Call Classification: Leave this set to System Default. Media Resource Group List: Media Resource Group Lists share resources such as Music On Hold and Media Termination Points. Be sure you assign your Trunk to the right MRGL. If this trunk will not be using any of those resources, then you can leave it as "None". However, for this configuration, we've chosen "Big House MRG List" Location: Location is used to identify where in a network a device is located so that bandwidth can be allocated. Since normally this trunk will want all bandwidth that is available, we select Hub_None. This is default value that designates no bandwidth limit on the trunk. AAR Group: This is to set up an alternative routing when bandwidth allocation becomes an issue. Since this is a basic setup, we'll leave it at < None> Packet Capture Mode: This is used for troubleshooting encryption. Leave it set to None Packet Capture Duration: As this is also related to Packet Capture Mode, leave it set to 0. Media Termination Point Required: If any sort of audio transcoding needs to occur between the stream incoming to the CUCM and the HMP system, you'll want this checked. It will route the stream through the CUCM instead of the stream going straight to the HMP system from the transmission endpoint. Retry Video Call as Audio: This option only affects Video endpoints on the CUCM that are calling into the trunk. Leave it checked. Transmit UTF-9 for Calling Party Name: This sets if the HMP system can accept and translate Unicode information. For this simple setup, leave it unchecked. Now, skip down to the Call Routing Information. Leave all other settings at default except for: Calling Search Space: This setting decides what calls will reach the trunk, as it controls the route patterns that handle the numbers dialed. Set this to the CSS of which the inbound devices are members. After this is set, skip down to the SIP Information: Sip Information

Destination Address: This would be the Destination Address of the Trunk (the HMP system). The value entered here should be a V4 dotted IP address, fully qualified domain name (FQDN), or DNS SRV record (if Destination Address is an SRV is checked). Destination Address is an SRV: If the Destination Address is an SRV record, this box must be checked. Otherwise, leave unchecked. Destination Port: Set this value to 5060. MTP Preferred Originating Codec: If you have set MTP required value, then you can adjust this to the protocol of your choice. Otherwise, this field is grayed out. Presence Group: Set this to Standard Presence Group as it will not apply for this test. SIP Trunk Security Profile: Set this to the appropriate profile for the trunk. If only the default "Non Secure SIP Trunk Profile" exists, then be sure to modify it so that the Outgoing Transport Type is UDP. Rerouting, Out-of-Dialog Refer, and SUBSCRIBE Calling Search Space: Set these all to the appropriate Calling Search Space that was set in previous fields. If you wish to handle these situations differently, set to the appropriate CSS. Sip Profile: Use the SIP Trunk Security Profile we set up earlier in this entry (i.e. HMP Non-secure Profile), or a profile matching the settings shown earlier. DTMF Signaling Method: Setting this to No Preference will allow it to use whichever the HMP system has available. Once all these fields have been entered, click the "Save" button. The system will then prompt you to use the Reset button. We'll do that later. First, we need to set up which numbers, when dialed, will be routed to the HMP SIP trunk. To do that, go to the top menu and hover over "Call Routing". Then choose

"Route/Hunt", then "Route Patterns". In this menu, click "Add New", and we'll add a new numbering system to route to the HMP. After clicking "Add New", you should see this screen:

We'll go through the important fields to let you know what to set. Route Pattern: This is where you'll set the pattern by which the CUCM system will match up the dialed number to decide whether to route that call through to the desired endpoint. Like most match strings, there are various special characters. We'll cover a couple of the most commonly used special characters: X - matches any single digit 0-9 (ex. 123XXX would match any dialed number from 123000 to 123999) ! - matches any number of digits 0-9 (ex. 91! would match 910 to 91999999 etc.) [] - matches a single digit of any number within the brackets. The numbers can either be a range ([1-5]) or random single numbers ([1568]). [^] - matches a single digit NOT within the brackets (as before, it can be range or list of single digits). For more special characters, refer to your CUCM Online Help Route Partition: This will restrict the access to this route pattern to all other connection points within the partition. Be sure that, if you use this parameter, that the source of the calls destined for this trunk are in the same Route Partition. Description: Be sure to put in a good description so this Route Pattern can be easily identified later. Gateway/Route List: This is where you choose the destination of the Route Pattern. Since we are building this route for the HMP server, choose the name of the SIP Trunk you created earlier.

The rest of the values should be left at their defaults, or changed to your own custom parameters. After you've finished changing the necessary settings, click "Save". As you'll see by the dialog box, this will also reset your SIP Trunk for you. That's all there is to setting up a simple HMP Trunk! The CUCM should now send all calls that match the route pattern to your HMP Box using SIP.

Related Products All versions of HMP that use SIP on all O/Ses. Glossary of Acronyms / Terms CUCM - Cisco Unified Communications Manager SIP - Session initial Protocol CSS - Calling Search Space MRG(L) - Media Resource Group (List)