This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies.

Read our privacy policy> 

Enterprise 1  Language | user_3557305 | Log Out

Huawei Enterprise
Community Forums Groups Collections Rewards FAQ 
Support Community

 Community  Forums  Unified Communication and IP Telephony  Sip trunk between U19xx a...

Sip trunk between U19xx and Cisco Call maanger Highlighted

Created: Mar 25, 2018 07:40:16 Latest reply: Mar 25, 2018 09:39:04  2947  4  13  0

View the author #1

emad

Overview :
  
This post describe the integration between the Huawei U19xx and Cisco CUCM 9 25 0

A- Huawei eSpace U1960 Configuration

1. Traditional PBX Interworking Scenario Follow Chat
The scenario of interconnecting the unified gateway with Cisco CUCM is applicable when enterprise subscribers who already
use Cisco CUSC call manager. Through interconnection between the unified gateway and the CUCM, the subscribers under
original PBXs remain unchanged, and the VoIP service and other supplementary services can be provided. The U1960 is used as Post
an example.
Background RECOMMENDED
This topic describes the traditional PBX and the Cisco CUSM interworking scenario.
Configuration Scenario
1 how to make call restriction in weekends
This topic describes the configuration objective, network, and data plan for the SIP trunk for PBX interworking scenario.
Configuring Boards

This topic describes how to configure boards in the web management system based on the actual hardware configuration.
After the boards are configured, you can perform operations such as number allocation and trunk configuration. 2 Huawei IP Phones not getting registered ...
Configure User Numbers

This topic describes how to configure SIP user numbers based on the data plan.
Configuring Trunks

This topic describes how to configure the office routes, prefixes, and trunks based on the data plan.
Configuring the Automatic Switchboard

This topic describes how to configure the automatic switchboard by running the VU script and configure the automatic
switchboard number. After the automatic switchboard is configured, outer-office users hear an announcement when
dialing the automatic switchboard number.
Verification

This topic describes how to verify the intra-office calls, calls between unified gateway users and original PBX users,
calls between unified gateway users and external users, calls between original PBX users and external users, and
automatic switchboard after the data configuration is complete.
Troubleshooting

This topic describes the methods for troubleshooting after the data configuration is complete.
1.1 Background
This topic describes the IPBX eSpace U1960 and the Cisco CUCM interworking scenario.
IP PBX
The IP private branch exchange (IPBX) uses the IP protocol to provide internal call services.
Description
The IPBX interworking allows the IP users to reduce costs and enjoy more services. The interworking between the unified
gateway and IPBX provides the voice over IP (VoIP) and other supplementary services for original traditional PBX users and
IPPBX users.

NOTE:
Original PBX is short for original traditional PBX in the following part of this document.
2. Configuration Scenario
This topic describes the configuration objective, network, and data plan for the traditional IPBX interworking scenario.
Target
You can configure scenarios based on customers' requirements. The scenario configuration listed in Table 1 is used as examples
in this topic.

Table 1 Configuration Objective

Intra-office · Original IPBX number segment: 5000-5019

number segment · New number segment: 7000-7019
 Long number · Original PBX number segment: 83785000-83785009, as the long numbers of 5000 to 5009. New PBX number
segment segment: 68905000-68905009
· New number segment: 68907000-68907009, as the long numbers of 7000 to 7009
The last four digits of a long number forms the short number. Users without a long number are non-Direct Dialing
In (DID) users.
Other numbers · Original main number: 83785888 New main number: 68905888
· New main number: 68907888

Dialing mode · Intra-office: The calling party makes a call by dialing a 4-digit short number. The short number of the calling
party is displayed to the called party.
· Outgoing: Make an outgoing call by dialing the called number without a prefix. For the DID user, the long
number of the calling party is displayed. For the non-DID user, the new main number is displayed.
· Incoming: The calling party dials main number + extension number to call a non-DID user, and dials the long
number to call a DID user.
NOTE:
The newly added PBX and unified gateway users make outgoing calls through the network of carrier B. For the new DID users,
the long number of the calling party is displayed. For the non-DID user, the new main number is displayed.

Trunk type · Interconnection with carrier A: The PRA trunk is used.

· Interconnection with carrier B: The PRA trunk is used.
· Interconnection with cisco CUCM IPBX: The SIP trunk is used.
In this example, the PRA and SIP trunk are used. The R2, SS7 (including ISUP and TUP), and QSIG trunks can
also be used. In actual scenarios, negotiate with users and carriers to determine the trunk type.
Networking
Figure 1 shows the typical interworking scenario of the Cisco CUCM.
Figure 1 Typical networking for interconnecting the unified gateway with traditional PBXs

· All calls of users are dialed in or out through the network of carrier B, and make an outgoing call by dialing the called
number without a prefix. Calls are re-routed upon routing failure. When carrier B's routing fails, carrier A's network route is
used to route calls.
· unified gateway users can directly dial the short numbers and long numbers under the original PBX.
Data Planning
Before configuration, you need to plan the data based on the networking and user requirements.
1. Plan the user numbers

Table 2 Plan the user numbers

Short Number Segment Long Number Segment Associated Device Remarks

5000–5009 83785000–83785009 Cisco CUCM Original DID users

5010–5019 - Cisco CUCM Original non-DID user

7000–7009 68907000–68907009 unified gateway New DID users

7010–7019 - unified gateway New non-DID user

- 83785888 unified gateway Original main number

- 68907888 unified gateway New main number

2. Plan the IP address

Table 3 Plan the IP address

NE IP Address Subnet Mask Gateway IP Address

unified gateway 192.168.10.10 255.255.255.0 192.168.10.1

NMS 192.168.10.11 255.255.255.0 192.168.10.1

 Table 3 Plan the IP address

NE IP Address Subnet Mask Gateway IP Address

Cisco CUCM 192.168.10.12 255.255.255.0 192.168.10.1

3. Plan the trunk data

Based on the installation of boards and E1/T1 cables, plan the trunk data, as described in Table 4.

Table 4 PRA trunk data planning

E1/T1 Slot Number E1/T1 Port Number Office Direction Office Direction Peer Office
Selection Code

2 0 0 0 Carrier B

2 1 1 1 Carrier A

4. Plan the prefix

Table 5 Plan the prefix

Prefix Prefix Type Office Direction Called Number Calling Number Change Remarks
Selection Code Change

68907 Intra-office prefix - - - -

0 National toll call prefix 0 - · Index 1 means that the Dial without a
entire number is changed prefix to make
to the new main number. outgoing calls t
· Use the long number and the network of
short number. carrier B.

00 International toll call 0 - · Index 1 means that the Dial without a

prefix entire number is changed prefix to make
to the new main number. outgoing calls t
· Use the long number and the network of
short number. carrier B.

1-9 Local call prefix 0 - · Index 1 means that the Dial without a
entire number is changed prefix to make
to the new main number. outgoing calls t
· Use the long number and the network of
short number. carrier B.

8378 Local call prefix 2 - - Make an outbo

call to cisco
CUCM.

022 Local call prefix 2 - - Make an outbo

call to cisco
CUCM.

68905 Local call prefix 2 - - Make an outbo

call to cisco
CUCM.
3. Configuring Boards
This topic describes how to configure boards in the web management system based on the actual hardware configuration. After
the boards are configured, you can perform operations such as number allocation and trunk configuration.
Procedure
1. Log in to the unified gateway web management system.
2. Choose System > Board Configuration.
3. Click the slots and select boards from the displayed drop-down list box.

NOTE:
The board type that you select must be the same as that in the slot on the unified gateway.

4. Click OK.
5. Click Data Save in the upper right corner of the web management system.

NOTICE:
The unsaved configurations will be deleted after the device is restarted.
4. Configure User Numbers
This topic describes how to configure SIP user numbers based on the data plan.
Procedure
1. Log in to the unified gateway web management system.
2. Add 10 DID users whose numbers start from 7000 (long number: 68907000) in a batch.
a. Choose User > SIP User.
 b. Click Create, and set the relevant parameters, as shown in Figure 1.
Figure 1 Configuring a DID user

c. Click OK.
3. Add 10 non-DID users whose numbers start from 7010 in a batch.
a. Choose User > SIP User.
b. Click Create, and set the relevant parameters, as shown in Figure 2.
Figure 2 Configuring a non-DID user number

c. Click OK.
4. Click Data Save in the upper right corner of the web management system.

NOTICE:
The unsaved configurations will be deleted after the device is restarted.
5. Configuring Trunks
This topic describes how to configure the office routes, prefixes, and trunks based on the data plan.
Procedure
1. Log in to the unified gateway web management system.
2. Configure number change indexes.
Add the following number change indexes:
· Add number change index 0, which is used to delete the first digit of the called number when an outgoing call is made.
· Add number change index 1, which is used to change the calling number of a non-DID user to the switchboard number
68907888 when an outgoing call is made.
· Add number change index 2, which is used to delete the first three digits of the called number when an outgoing call is
made.
· Add number change index 3, which is used to configure the calling number change for re-routing, specifically, changing
the calling numbers to the main number of the PBX.
To add a number change index, proceed as follows:
e. Choose Trunk > Office Route Configuration > Number Change Index.
f. Click Create, and set the relevant parameters, as shown in Figure 1.
Figure 1 Configuring number change index 0

g. Click OK.
h. Click Create, and configure number change index 1, as shown in Figure 2.
 Figure 2 Configuring number change index 1

i. Click Create, and configure number change index 2, as shown in Figure 3.

Figure 3 Configuring number change index 2

j. Click Create, and configure number change index 3, as shown in Figure 4.

Figure 4 Configuring number change index 3

3. Configure office routes and office route selection codes.

In this scenario, the office routes and office route selection codes are the same and planned as follows:
· Connection to carrier B's network: 0. Whether to select a new route based on the standby office route selection code 1
corresponding to the failure processing index if the call fails to be routed according to the office route selection code 0.
· Connection to carrier A's network: 1.
· Connection to the traditional PBX: 2.
To configure office routes and office route selection codes, proceed as follows:
c. Choose Trunk > Office Route Configuration > Office Route Selection Code.
d. Click Create, and configure office route selection code 1, as shown in Figure 5.
Figure 5 Configuring the office route selection code to 1

e. Click Create, and configure office route selection code 2, as shown in Figure 6.
Figure 6 Configuring the office route selection code to 2

f. Choose Trunk > Office Route Configuration > Failure Processing Index.
g. Click Create, and set the relevant parameters, as shown in Figure 7.
Figure 7 Configuring failure processing index 0

h. Click OK.
i. Choose Trunk > Office Route Configuration > Office Route Selection Code.
j. Click Create, and set the relevant parameters, as shown in Figure 8.
 Figure 8 Configuring the office route selection code to 0

k. Click OK.
l. Choose Trunk > Office Route Configuration > Office Route.
m. Click Create, and set the relevant parameters, as shown in Figure 9.
Figure 9 Setting the office route number to 0

n. Click OK.
o. Click Create, and configure office route 1, as shown in Figure 10.
Figure 10 Setting the office route number to 1

p. Click Create, and configure office route 2, as shown in Figure 11.

Figure 11 Setting the office route number to 2

4. Configure the number mapping.

· Map numbers 68905000-83785009 to original user numbers 83785000-83785009 in the PBX.
· Map the number 68905888 to the cisco CUCM switchboard number 83785888.
· Map numbers 0225000-0225019 to the cisco CUCM user numbers 5000-5019. When unified gateway users directly dial
the short numbers under the original PBX, the prefix 022 is added to the short numbers through the number mapping.
c. Choose Trunk > Office Route Configuration > Number mapping.
d. Click Create, and set the relevant parameters, as shown in Figure 12.
Figure 12 Configuring the number mapping

e. Click OK.
Repeat step 4.a to step 4.c to configure other number mappings. Set the relevant parameters by referring to Table 1.

Table 1 Number mapping parameters

Internal Number External Number

83785000-83785009 68905000-68905009

83785888 68905888

0225000-0225019 5010-5019

5. Configure intra-office prefixes.

When an intra-office subscriber or an external subscriber dials an intra-office number, the unified gateway analyzes whether
the called party is an intra-office subscriber based on this prefix.
68907: Long number analysis prefix, based on which the unified gateway analyzes whether the called party is an intra-office
subscriber when an intra-office or external subscriber dials the long number of an intra-office subscriber.
. Choose Trunk > Prefix Configuration.
a. Click Create, and set the relevant parameters, as shown in Figure 13.
 Figure 13 Configure prefix 68907

b. Click OK.
6. Configure outgoing prefixes are routed out from the network of carrier B.
· Configure the outgoing prefixes 0 to 9, All outgoing calls are routed out from the network of carrier B through unified
gateway. Make an outgoing call by dialing the called number without a prefix. The office direction selection code is 0.
For DID subscribers, the long number is displayed; for non-DID subscribers, the main number is displayed.
· Configure the outgoing prefixes 1 to 9, All outgoing calls are routed out from the network of carrier B through unified
gateway. Make an outgoing call by dialing the called number without a prefix. The office direction selection code is 0.
For DID subscribers, the long number is displayed; for non-DID subscribers, the main number is displayed.
· The short numbers under the PBX (start with 5) or unified gateway (start with 7) may be the same as the first several
digits of the local number, so prefix 5 and 7 must be configured as the intra-office or local call prefix. The office route
selection code corresponding to the prefix is 0 and the corresponding office route is that of the unified gateway. The
intra-office and inter-office numbers sent by the PBX are processed by the unified gateway.
· Configure outgoing prefix 5 to enable unified gateway subscribers to call PBX subscribers' short numbers. PBX
subscribers can make outgoing calls that are routed out from the network of carrier B through unified gateway.
· Configure outgoing prefix 7 to enable the unified gateway subscribers to call each others' 4-digit short number and make
prefix-free outgoing calls.
e. Choose Trunk > Prefix Configuration.
f. Click Create, and set the relevant parameters, as shown in Figure 14.
Figure 14 Configure prefix 0

g. Click OK.
Repeat step 6.a to step 6.c to add international toll call prefix 00 and local prefixes 1 to 4, 6, 8, and 9.
h. Click Create, and configure prefix 5, as shown in Figure 15.
 Figure 15 Configure prefix 5

i. Click Create, and configure prefix 7. The parameters values of prefix 7 is the same as that of prefix 5.
7. Configure a prefix for the subscribers under the unified gateway to dial the subscribers under the original PBX.
· Configure prefix 8378: Long number prefix for the subscribers under the unified gateway to dial the long numbers under
the original PBX through the PRA trunk. During actual deployment, configure this prefix according to the distribution of
the original numbers of customers.
· Configure prefix 022: Short number prefix for the subscribers under the unified gateway to directly dial the short
numbers under the PBX.
· Configure prefix 68905: Intra-office users can dial the long numbers on the new number segment to call the DID users
under the original PBX.
c. Choose Trunk Management > Prefix Configuration.
d. Click Create, and set the relevant parameters, as shown in Figure 16.
Figure 16 Configure prefix 8378

e. Click OK.
f. Click Create, and configure prefix 022, as shown in Figure 17.
 Figure 17 Configuring prefix 022

g. Click Create, and configure prefix 68905, as shown in Figure 18.

Figure 18 Configure prefix 68905

8. Configure the Trunk.

· Configure the PRA trunk through which the unified gateway connects to carrier B's network.
Add a PRA link. Set the link number to 0, slot number to 7, E1/T1 port number to 0, and position to user. This parameter
must be set through negotiations with the peer office. Different values must be set for the two offices.
· Configure the PRA trunk through which the unified gateway connects to carrier A's network.
Add a PRA link. Set the link number to 1, slot number to 7, E1/T1 port number to 1, and position to user. This parameter
must be set through negotiations with the peer office. Different values must be set for the two offices.
· Configure the SIP trunk for interworking with the original PBX.
c. Choose Trunk > Trunk Configuration > PRA.
d. Click Add A Peer Office.
e. Click the connection line to configure the Trunk. Set the relevant parameters, as shown in Figure 19.
Figure 19 Configuring the PRA trunk

f. Click OK.
The PRA trunk is connected to carrier B's network.
g. Click Add A Peer Office.
h. Click the connection line to configure the Trunk. Set the relevant parameters, as shown in Figure 20.
 Figure 20 Configuring the PRA trunk

i. Click OK.
j. Choose Trunk > Trunk Configuration > SIP.
k. Click Add A Peer Office.
l. Click the connection line to configure the Trunk. Set the relevant parameters, as shown in Figure 21.
Figure 21 Configuring the SIP trunk

m. Click OK.
The SIP trunk is connected to the original PBX.
9. Configure the clock source.
· If the unified gateway connects to an upper-level device through the E1/T1 trunk, clock source configuration ensures
that time on the unified gateway and the upper-level device are synchronized. This prevents frame slip (voice packet
loss).
· If the unified gateway connects to multiple devices through E1/T1 trunks, configure the clock source on any of these
devices. The unified gateway will synchronize time with this device.
· If the unified gateway provides the clock source, you do not need to configure the clock source.
In this example, the unified gateway uses carrier B's time.
c. Choose System > Clock Source Configuration.
d. From the Select clock source drop-down list box, select the Peer device.
Configure the active clock source as prompted based on the installation information about the E1/T1 trunk connected to
the peer device, as shown in Figure 22.
Figure 22 Configuring the clock source

e. Click OK.
10. Click Data Save in the upper right corner of the web management system.

NOTICE:
The unsaved configurations will be deleted after the device is restarted.
Follow-up Procedure
In the actual scenario, if the dialing mode of the customer is dialing without prefix, that is, making outgoing calls by directly
dialing the called number, and if an intra-office short number is the same as the first several digits of a local call number, change
the call attribute of the outgoing prefix to Local or Intra-Office Call (interlocal). Set the minimum number length to the
number length for intra-office numbers and the maximum number length to the number length for outer-office numbers. At the
same time, set the WaitNextNumTimerLen parameter.
6. Configuring the Automatic Switchboard
This topic describes how to configure the automatic switchboard by running the VU script and configure the automatic
switchboard number. After the automatic switchboard is configured, outer-office users hear an announcement when dialing the
automatic switchboard number.
Procedure
1. Configure the automatic switchboard service.
Configure a VU number 68907888. An external subscriber hears the prompt tones played by the automatic switchboard
when dialing this number.
2. Run the following command to configure the calling number change rule, so that the unified gateway will not change
calling numbers when PBX users call unified gateway users.
config protocol pra officeno 2 supportclipredeal no

3. Run the following command to enable the software parameter whose ID is 342.
config softargu type 342 value 1

NOTE:
You must enable the software parameter whose ID is 342 when the intra-office or local call prefix, number mapping, and call forwarding functions
are used together. Otherwise, the intra-office or local call prefix will not perform the second number analysis.
When a unified gateway user directly dials a short number under the PBX, for example, 5000, the second number analysis is performed. During the
second number analysis, number 5000 is mapped to 0225000. Then outgoing calls are made by dialing the prefix 022.

4. Data save.
a. In the command tree, choose System Management > Operator Management.
b. Double-click Save.

7. Verification
This topic describes how to verify the intra-office calls, calls between unified gateway users and original PBX users, calls
between unified gateway users and external users, calls between original PBX users and external users, and automatic
switchboard after the data configuration is complete.
After the data configuration is complete, verify that the configured service can be used normally.
1. Verify the intra-office calls.
The intra-office users, such as the user 7000 and user 7001, can call each other normally.
2. Verify the call between an unified gateway user and a user of the original PBX.
· An unified gateway user such as 7000 can talk to a user of the original PBX normally, and the short number is displayed
on the phone of the called party.
· A user of the original PBX such as 5000 can talk to an unified gateway user normally, and the number 83785000 is
displayed on the phone of the called party.
3. Verify the call between an unified gateway user and an external user.
· The DID user 7000 can talk to an external user normally by dialing external user number, and the calling number
68907000 is displayed on the phone of the called party.
· The non-DID user 7010 can talk to an external user normally by dialing external user number, and the calling number
68907888 is displayed on the phone of the called party.
· An external user can talk to the user 7000 normally by dialing 68907000.
· An external user dials 68907888, hears the VU prompt tone, and then dials the extension number 7010. The phone of the
user 7010 rings, and the conversation is normal.
4. Verify the call between a user of the original PBX and an external user.
· The DID user 5000 can talk to an external user normally by dialing external user number, and the calling number
68905000 is displayed on the phone of the called party.
· An external user can talk to user 5000 normally by dialing 83785000.
· The non-DID user 5010 can talk to an external user normally by dialing external user number, and the calling number
68905888 is displayed on the phone of the called party.
· An external user dials 83785888, hears the VU prompt tone, and then dials the extension number 5010. The phone of the
user 5010 rings, and the conversation is normal.
· An external user dials 68907888, hears the VU prompt tone, and then dials the extension number 5010. The phone of the
user 5010 rings, and the conversation is normal.
8. Troubleshooting
This topic describes the methods for troubleshooting after the data configuration is complete.
1. Intra-office call exceptions
· If the prompt tone "The number you dialed does not exist." is played, see Calling Party and Called Party Cannot Hear Each Other
to solve the problem.
· If the phone of the called party does not ring or another phone rings after the calling party makes a call, see ONLY Number
to solve the problem.
cannot be bound

2. Exceptions of calls between the unified gateway and original PBX subscribers
· If the prompt tone "The number you dialed does not exist." is played after an unified gateway subscriber calls a
subscriber of the original PBX, see Number Is Displayed Abnormally to solve the problem.
· If an exception occurs when a subscriber of the original PBX calls an unified gateway subscriber, see 1 to solve the
problem.
3. Exceptions of calls between the unified gateway and external subscribers
· If the prompt tone "The number you dialed does not exist." is played after a direct-call subscriber of the unified gateway
calls an external subscriber, see Number Is Displayed Abnormally to solve the problem.
· If an exception occurs when an external subscriber calls a subscriber unified gateway, see 1 to solve the problem.
4. Exceptions of calls between the original PBX and external subscribers
· If the prompt tone "The number you dialed does not exist." is played when a subscriber of the original PBX calls a
PSTN subscriber, see Number Is Displayed Abnormally to solve the problem.
· If the calling number fails to be displayed correctly on the phone of the called party, see Number Is Displayed Abnormally to
solve the problem.
 · If an exception occurs when an external subscriber calls a subscriber of the original PBX, see 1 to solve the problem.
· If an external subscriber cannot hear the prompt tone after dialing the switchboard number, see Voice Prompt Faults to solve
the problem.
B- Cisco CUCM Configuration :
Overview :
Note:
IF you already have a CCUM preconfigured so you can start directly from the SIP trunk configuration .[step F]

The high level steps for configuring CUCM are as follows:

1. Create a partition.
2. Create a calling search space.
3. Define translation patterns.
D. Configure SIP Profile
Configure SIP Trunk Security Profile [Optional ]
5. Provision a SIP trunk.
6. Configure Route Group
7. Configure Route List
8. Set up route pattern.
The following sections describe the CUCM configuration steps in more detail. And we only add the minimum configuration to configure the
SIP trunk .
Configuring Cisco Unified Communications Manager V7.X to V11.x
Let’s dive into the configuration steps for CUCM. The connectivity between CUCM and the Huawei AR2200 is referred to as SIP trunk to
conform to Cisco’s terminology.
1. Create a Partition
A CUCM partition contains a list of route patterns. Partitions facilitate call routing by dividing the route plan into logical subsets that are
based on organization, location, and call type. For details about partitions, see "Partitions and Calling Search Spaces" in the CUCM System
Guide.
This partition is specific to the SIP trunk that connects Office Communications Server to CUCM. It will store route pattern and translation
pattern rules that are specific to handling incoming traffic to CUCM from the “ Huawei AR Route”. For our example, this partition is named
"Huawei_SIP_PT_Local ".
To create a CUCM partition
1. From your CUCM Administration console, click Call Routing, click Class of Control, and then click Partition (Figure 2).
Figure 2. Opening the partitions screen

2. Click Add New to create a new partition as showing in Figure 3.

Figure 3. Adding a new
partition
 
3. In the Name field,
specify the name of the
partition and a
description as shown in
Figure 4. We’ve specified
" Huawei_SIP_PT_Local ".
Figure 4. Name and
description of the partition

4. Click Save,
 

Note:

Whether a partition is required in a particular environment may depend on the rules required. Verify this with your CUCM
administrator.
2.Create a Calling Search Space
A CUCM calling search space is an ordered list of route partitions. Calling search spaces determine which partitions and the order in which
they are searched when CUCM routes a call. In our example, this calling search space is named " Huawei_SIP_CSS_Local " and is assigned to
the “Huawei_SIP_PT_Local” partition created earlier.
To create a calling search space
1. From the CUCM Administration console, click Call Routing, click Class of Control, and then click Calling Search Space (Figure 7).
Figure 7. Opening the Calling Search Space Configuration screen

2. Click Add New to create a new calling search space. Specify a name for the calling search space. In our example, the new calling
search space is " Huawei_SIP_CSS_Local ".
3. Select the “Huawei_SIP_PT_Local” partition, and then click the down arrow to move it to the Selected Partitions area to assign this
calling search space to the Huawei_SIP_PT_Local partition (Figure 8).
Figure 8. Assigning the
Huawei_SIP_CSS_Local
calling search space to
the
Huawei_SIP_CSS_Local
4. Click Save to insert this
calling search space into
the CUCM configuration.
 
 
 
3.Define
Translation
Patterns
Next, translation patterns must be defined and assigned to the newly created partition. Translation patterns manipulate dial strings before a
call is routed.
The translation patterns we’ll define are specific for handling inbound calls to the CUCM that come from Office Communications Server. A
translation pattern converts dial strings for calls sent by the “Huawei AR router ” where the TO field matches the pattern. CUCM then uses
the translated dial string to determine how to route the call.
One or more translation patterns must be defined depending on your needs. At a minimum, you need to define at least two translation
patterns:
A translation pattern for incoming calls from Office Communications Server that are destined for the PSTN. This allows Office
Communicator users who are enabled for Enterprise Voice to dial out externally.
A translation pattern for incoming calls from Office Communications Server that are destined for CUCM-assigned phone numbers.
This allows Office Communicator users to dial Cisco phones within the organization.
If users are allowed to dial international numbers, you have to define a third translation pattern. Consider creating translation patterns for
emergency numbers (for example, 911).
Office Communications Server to PSTN Translation Pattern
The first translation pattern (called 3316986xxxx, which means the TO string starting with33 followed by 9 digits as shown in Figure 9)
transforms all calls from Office Communications Server that are destined to a domestic PSTN number.
On your CUCM Administration console, click Call Routing, click Translation Pattern (Figure 9), and then click Add New to create a new
translation pattern configuration.
Figure 9. Opening the Translation Pattern Configuration screen

The translation pattern is assigned to the Huawei_SIP_PT_Local partition that you previously created.
The period (.) is a separator that indicates that all digits before the period are to be discarded.
Figure 10. Configuring a new translation pattern
 
 
 
Configure SIP Profile
Step 1 From Cisco Unified CM Administration, choose Device > Device Settings > SIP Profile.
Step 2 Perform either of the following steps:
• To create a new profile, click Add New.
• To select an existing profile, click Find and select a SIP profile.
Step 3 Complete the fields in the SIP Profile Configuration window. For help with the fields, refer to the online help.
Step 4 Click Save.

4.Configure SIP Trunk Security Profile [Optional ]

Step 1 In Cisco Unified CM Administration, choose System > Security > SIP Trunk Security Profile.
Step 2 Perform either of the following steps:
a) To select an existing profile, click Find and select an existing profile.
b) To create a new profile, click Add New.
Step 3 Complete the fields in the SIP Trunk Security Profile Configuration window. For detailed field descriptions,
refer to the online help.
Step 4 Allow the ping on the configuration
Step 5 Click Save
5.Provision a SIP Trunk
A SIP trunk to the “Huawei AR router” is created on the CUCM and is assigned the “Huawei_SIP_CSS_Local” calling search space that was
created earlier. The SIP trunk uses SIP over TCP, which requires port 5060.
The CUCM SIP trunk is established to the IP address of the “Huawei AR” that represents the gateway listening IP address.
In our example, the trunk name is Katmia_SIP-TR, and the “Huawei AR ” gateway listening IP address is 10.39.2.1
To create a new SIP trunk
1. On the CUCM Administration console, click Device, and then click Trunk (Figure 12).
Figure 12. Adding a new trunk
2. Click Add New, and then on the Trunk Type list, select SIP Trunk. Select SIP as the Device Protocol, and then click Next (Figure 13).
Figure 13. Configuring the SIP trunk

3. Specify the Device Name (in our example, Katmia_SIP-TR), the Calling Search Space (in our example, Huawei_SIP_CSS_Local), the ,
the Destination Address to match the “Huawei AR” gateway listening IP address (in our example, 192.168.10.10), and Destination
Port (in our example, 5060).
Table 1 lists the required Trunk Configuration settings and their values (Figure 14).
Table 1. Required Trunk Configuration settings

To successfully communicate with the Huawei AR, CUCM must use the codec, G.711. The device pool default setting in CUCM 7.1 is
configured to use the G.711 codec. The Device Pool setting shown in Table 1 and Figure 14 should be set to "Default". If your CUCM
default device pool does not use G.711 as the codec, you will need to use a device pool that uses G.711.
Figure 14. Trunk Configuration settings

4. Click Save, and then reset the trunk by clicking the Reset icon at the top of the Trunk Configuration page to activate the SIP trunk
changes.
 
 
 
6. Configure Route Group
Step 1 From Cisco Unified Communications Manager Administration, choose Call Routing > Route/Hunt > Route
Group.
The Route Group Configuration window appears.
Step 2 Choose one of the following options:
• To add a new route group, click the Add New button.
• To modify the settings for an existing route group, enter the search criteria, click Find, and choose aroute group from the resulting list for Ex
[192.168.10.10].
The Route Group Configuration window appears.
Step 3 Configure the fields in the Route Group Configuration window. See the online help for more information
about the fields and their configuration options.
Step 4 Click Save.
 

 
7.Configure Route List
Communications Manager uses the order in the route list to search for available devices for outgoing calls.
A route list can contain only route groups and local route groups.
When an outbound call is sent out through route list, the route list process locks the outbound device to
prevent sending an alerting message before a call is completed. After the outbound device is locked, the
Hunt List stops hunting down the incoming calls.

 
 
Step 1 In Cisco Unified Communications Manager Administration, choose Call Routing > Route/Hunt > Route
List.
Step 2 Choose one of the following options:
• To add a new route list, click the Add New button.
• To modify the settings for an existing route list, enter the search criteria, click Find, and choose a route
list from the resulting list.
Step 3 Configure the fields in the Route List Configuration window. See the online help for more information about
fields and their configuration options.
Step 4 To add a route group to the route list, click the Add Route Group button.
Step 5 From the Route Group drop-down list, choose a route group to add to the route list.
Step 6 Click Save.
Step 7 Click Apply Config.
 
 
 
 
 
 
 
 
8.Set Up Route Pattern: CUCM to Office Communications Server
Route patterns are designed for routing calls from CUCM to the “ Huawei AR “  over the SIP trunk so that users who are using a Cisco IP
phone can call Office Communicator users. The route patterns determine which calls are sent to the SIP trunk based on a pattern match of
the phone number in the TO field. Route patterns can also perform transformations of the dial strings for the TO and the FROM fields.
To set up the route pattern
1. From the CUCM Administration console, click Call Routing, click Route/Hunt, and then click Route Pattern (Figure 15).
2. Click Add New, and then configure the route pattern.
Figure 15. Opening the Route Pattern screen

For example, if you want users who are using a Cisco IP phone to be able to dial an Office Communicator user using a 4-digit extension,
create a route pattern that is associated to the Katmia_SIP-TR SIP trunk that you created earlier that instructs CUCM to route to the
“Huawei AR” all calls that match the TO dial string with the pattern 7! . In this case, no transformation of the dial strings in the TO and the
FROM fields is necessary. This route pattern configuration is illustrated in Figure 16.
Figure 16. Route pattern
 
You will need to define multiple CUCM routing patterns if you have different Office Communications Server numbering formats for specific
offices or geographic locations.
That completes your introduction to configuring a SIP trunk on Cisco’s Unified Communications Manager (also known as CallManager).

9.Verification
Item Expected Result Possible Fault Cause

Outgoing call Calls can be made properly, and the calling
number is correctly displayed. For ex, user
2000 can make an through the AT0 trunk
connected to the Huawei U19xx through
SIP Trunk , and call [0 + called no]
· The outgoing call prefix is incorrectly
configured.
· The outgoing trunk is incorrectly
configured.

Incoming call Calls can be made properly. For example, an N/A

outer-office user can dial 83785888 and then
dial 5000 as prompted to connect to user
5000.

From group: Unified Communication and IP Telephony

 Helpful (13)  Favorite(0)  Share  Report

Salah Created Mar 25, 2018 07:49:52   (0)  2#

Great , very helpful topic ...

:)

rabee Created Mar 25, 2018 07:58:27   (0)  3#

I think it is a good reference and we can use it as a documentation :):)

 Jaber Created Mar 25, 2018 09:15:53   (0)  4#

Very useful information

gululu Admin Created Mar 25, 2018 09:39:04   (0)  #5

very good !Thanks

Comment

What 's on your mind?

Advanced Send

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that
may bring legal risks to all parties, including but are not limited to the following:
Politically sensitive content
Content concerning pornography, gambling, and drug abuse
Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks,
copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your
own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."

  
 Huawei Website | Support | About Huawei | Privacy | Terms of Use
Huawei Enterprise | Huawei Carrier Forum | Training & Certification
Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.