Actions

Difference between revisions of "SIP2SIP Transcoding using Mediant 600"

From Zenitel Wiki

(→‎Outbound IP Routing)
(→‎Cisco Call Manager Configuration)
 
(24 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{A}}
 
The Mediant 600 has the capability to transcode a SIP call from e.g. G711µ-law to G729. Here are some examples using the Mediant 600 to transcode G711µ-law to G729.  
 
The Mediant 600 has the capability to transcode a SIP call from e.g. G711µ-law to G729. Here are some examples using the Mediant 600 to transcode G711µ-law to G729.  
  
 
The examples shown are between:
 
The examples shown are between:
−
:* AlphaCom XE7 and Cisco Call Manager
+
:* AlphaCom XE and Cisco Call Manager
−
:* AlphaCom XE7 and AudioCodes MP-114/118
+
:* AlphaCom XE and AudioCodes MP-114/118
−
:* AlphaCom XE7 and Mobile VoIP GSM Gateway MV-370  
+
:* AlphaCom XE and Mobile VoIP GSM Gateway MV-370  
  
 
[[Image:SIP2SIP-M600.PNG|thumb|650px|Configuration example]]
 
[[Image:SIP2SIP-M600.PNG|thumb|650px|Configuration example]]
Line 10: Line 11:
  
 
= AlphaCom Configuration =
 
= AlphaCom Configuration =
−
''All text and pictures refer to AMC version 11.1.3.3''
 
−
<br/>
 
−
<br/>
 
−
== AlphaWeb Configuration ==
 
−
=== Assign IP address to the AlphaCom XE Ethernet port(s) ===
 
−
Log on to AlphaWeb and enter a valid IP address on the Ethernet port.
 
−
In the example below, Ethernet port 1 is used.
 
−
Consult your network administrator to obtain the IP address.
 
−
 
−
[[image:AlphaWeb Int3.PNG|thumb|left|500px|]]
 
−
<br style="clear:both;" />
 
−
 
−
=== Insert SIP Trunk licenses ===
 
−
The AlphaCom requires only 1 x SIP Trunk License for this configuration. <br/>
 
−
Log on to AlphaWeb and install the SIP Trunk license.
 
−
 
−
[[image:AXE7-InsertLicense.PNG|thumb|left|500px|]]
 
−
<br style="clear:both;" />
 
−
 
−
=== Firewall (filter) settings ===
 
−
Enable the SIP protocol on the desired Ethernet port
 
−
(default enabled for Ethernet port1).
 
−
 
−
[[image:AXE7-Filters.PNG|thumb|left|500px|]]
 
−
<br style="clear:both;" />
 
−
 
−
== AlphaPro Configuration ==
 
−
=== Create a SIP Trunk Node ===
 
−
From the AlphaPro main menu, use the ‘+’ button next to the ‘Select Exchange’ dropdown list to create a new exchange. The exchange type must be set to ‘SIP Node’.
 
−
 
−
Set the parameters as shown in the image:
 
−
 
−
[[image:Configuration guide for AudioCodes MP114 118 - Create a SIP Trunk Node.PNG|thumb|left|500px|]]
 
−
<br style="clear:both;" />
 
−
 
−
The SIP Trunk IP address must be identical to the IP address of the SIP Gateway (i.e. Mediant 600).
 
−
 
−
'''Note:''' If the AlphaCom is configured with a SIP Registar node in addition to the SIP Trunk node, the SIP Registar node must have a lower node number than the SIP Trunk node.
 
−
<br style="clear:both;" />
 
−
 
−
=== Create AlphaCom/SIP Audio links ===
 
−
''This paragraph is only relevant for AMC software 10.04 or earlier.''
 
−
 
−
From AMC 10.05 the audio links are assigned dynamically whenever needed, and there is no need to specify the links in AlphaPro. Proceed to [http://10.5.2.54/wiki/index.php/Configuration_guide_for_AudioCodes_MP114/118#Define_the_AlphaCom_.2F_SIP_routing Define the AlphaCom / SIP routing].
 
−
 
−
However, if you want to reserve VoIP channels for the SIP Gateway, you can do so by following the description below.
 
−
 
−
In '''Exchange & System > NetAudio''' use the ''Insert'' button to create one or several audio (VoIP) links between the AlphaCom and the SIP Gateway. The physical number specifies the VoIP channel and must be in the range 605 – 634 (start with 605). Normally the number of audio links will be equal to the number of phone lines connected to the SIP Gateway.
 
−
 
−
[[image:Configuration guide for AudioCodes MP114 118 - Create AlphaCom SIP Audio links.PNG|thumb|left|500px|]]
 
−
<br style="clear:both;" />
 
−
 
−
=== Define the AlphaCom / SIP routing ===
 
−
In '''Exchange & System > Net Routing''' use the ''Insert'' button to create a
 
−
route between the AlphaCom and SIP Gateway. Set '''Preferred codec'''
 
−
to ''G711u'' and '''RTP Packet Size''' to ''20 ms''.
 
−
 
−
[[image:Configuration guide for AudioCodes MP114 118 - Define the AlphaCom SIP routing.PNG|thumb|left|500px|]]
 
−
<br style="clear:both;" />
 
−
 
−
=== Prefix and Global numbers ===
 
−
 
−
The telephone line can be accessed in different ways:
 
−
* Prefix number: Dial Prefix + Phone number. “Phone number” will be called
 
−
* Integrated Prefix number: Dial Prefix + Phone number. The prefix will be included as a part of the called telephone number.
 
−
* Global number: Dial the phone number without using prefix
 
−
 
−
==== Prefix number ====
 
−
The directory number must be programmed in the AlphaCom directory table with feature 81 and Node = SIP Trunk node number (100 in this example). In the “Parameter 2” field (“Collect N more digits (SIP)” in earlier AlphaPro versions) you must enter the maximum number of digits in a phone number.
 
−
 
−
When the prefix is dialed, the AlphaCom will wait for further digits. When the number of digits specified in the “Parameter 2” field (Collect N more digits (SIP in earlier versions of AlphaPro) are collected, a call setup message is sent to the SIP gateway. If fewer digits are entered, the AlphaCom will time out after 4 seconds, and the call setup message will be sent. You can also terminate the digit collection by pressing the M-key. The call setup message will then be sent immediately.
 
−
 
−
In the example below the directory number 0 is used as a prefix.
 
  
−
[[image:Example of prefix number.PNG|thumb|left|500px|Example of prefix number]]
 
−
<br style="clear:both;" />
 
  
−
Dialing examples:
+
How to set up a SIP Trunk in the AlphaCom is described here: [[SIP trunk node - configuration]]
−
: 0 + 12345678: Telephone number 12345678 will be called
 
−
: 0 + 1234: After a 4 second timeout, telephone number 1234 will be called
 
−
: 0 + 1234 + M: Telephone number 1234 will be called
 
−
 
 
−
==== Integrated Prefix number ====
 
−
The directory number must be programmed in the AlphaCom directory table with feature 83 and Node = SIP Trunk node number (100 in this example). In the “Parameter 2” field (“Collect N more digits (SIP)” in earlier AlphaPro versions) you must enter the maximum number of digits in a phone number.
 
−
 
 
−
When the prefix is dialed, the AlphaCom will wait for further digits. When the number of digits specified in the “Parameter 2” field (“Collect N more digits (SIP)” in earlier AlphaPro versions) are collected, a call setup message is sent to the SIP gateway. If fewer digits are entered, the AlphaCom will time out after 4 seconds, and the call setup message will be sent. You can also terminate the digit collection by pressing the M-key. The call setup message will then be sent immediately.
 
−
 
 
−
In the example below the directory number 57 is used as a prefix.
 
−
 
 
−
[[image:Example of integrated prefix number.PNG|thumb|left|500px|Example of integrated prefix number]]
 
−
<br style="clear:both;" />
 
−
 
 
−
Dialing examples:
 
−
: 57 + 12345678: Telephone number 5712345678 will be called
 
−
: 57 + 1234: After a 4 second timeout, telephone number 571234 will be called
 
−
: 57 + 1234 + M: Telephone number 571234 will be called
 
−
 
 
−
==== Global number ====
 
−
The directory number must be programmed in the AlphaCom directory table with feature 83 and Node = SIP Trunk node number (100 in this example). The “Parameter 2” field (in earlier AlphaPro version “Collect N more digits (SIP)”) must be left blank.
 
−
 
 
−
When the global number is dialed, the AlphaCom will immediately send a call setup message to the SIP gateway.
 
−
 
 
−
In the example below directory number 12345678 is defined as a global number. When dialing this number a call setup message is sent to the SIP gateway, instructing it to call this phone number.
 
−
 
 
−
[[image:Example of global number.PNG|thumb|left|500px|Example of global number]]
 
−
<br style="clear:both;" />
 
−
 
 
−
=== Update the exchange ===
 
−
Log on to the exchange and update the exchange by pressing the
 
−
SendAll button.
 
  
 
= Mediant 600 Configuration =
 
= Mediant 600 Configuration =
Line 213: Line 107:
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
−
:*Proxy Set ID#1 for AlpahCom XE7
+
:*Proxy Set ID#1 for AlpahCom XE
 
::*From the "Proxy Set ID" drop-down list, select "1"
 
::*From the "Proxy Set ID" drop-down list, select "1"
 
::*In the "Proxy Address" column, enter the IP address of the AlphaCom
 
::*In the "Proxy Address" column, enter the IP address of the AlphaCom
Line 237: Line 131:
 
[[Image:M600-SetIPGroup1.PNG|left|thumb|500px|IP Group 1]]
 
[[Image:M600-SetIPGroup1.PNG|left|thumb|500px|IP Group 1]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
:*IP Group #1 for AlpahCom XE7
+
:*IP Group #1 for AlpahCom XE
 
::*From the "Index" drop-down list, select "1"
 
::*From the "Index" drop-down list, select "1"
 
::*In the "Description" field, type an arbitrary name for the IP Group (e.g. AlphaCom)
 
::*In the "Description" field, type an arbitrary name for the IP Group (e.g. AlphaCom)
 
::*From the "Proxy Set ID" drop-down list, select "1" (For this "IP Group" communicate with the "Proxy Set" of the AlphaCom)
 
::*From the "Proxy Set ID" drop-down list, select "1" (For this "IP Group" communicate with the "Proxy Set" of the AlphaCom)
 
::*In the "SIP Group Name" field, enter the IP Adress sent in the SIP Request From/To headers for this IP Group (AlphaCom's IP Adress)
 
::*In the "SIP Group Name" field, enter the IP Adress sent in the SIP Request From/To headers for this IP Group (AlphaCom's IP Adress)
−
::*Contact User = name that is sent in the SIP Request contact header for this IP Group (e.g. AXE7)
+
::*Contact User = name that is sent in the SIP Request contact header for this IP Group (e.g. AXE)
 
::*From the "IP Profile ID" drop-down list, select "1" (the IP Profile is configured later)  
 
::*From the "IP Profile ID" drop-down list, select "1" (the IP Profile is configured later)  
 
::*Submit
 
::*Submit
Line 269: Line 163:
 
[[Image:M600-CoderGroup1.PNG|left|thumb|500px|Coder Group 1]]
 
[[Image:M600-CoderGroup1.PNG|left|thumb|500px|Coder Group 1]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
:*Coder Group ID#1 for AlpahCom XE7
+
:*Coder Group ID#1 for AlphaCom XE
 
::*From the "Coder Group ID" drop-down list, select "1"
 
::*From the "Coder Group ID" drop-down list, select "1"
 
::*In the "Coder Name" drop-down list, select "G.711U-law" (Coder used by AlphaCom)
 
::*In the "Coder Name" drop-down list, select "G.711U-law" (Coder used by AlphaCom)
Line 288: Line 182:
 
[[Image:M600-IPProfile1.PNG|left|thumb|500px|Profile ID 1]]
 
[[Image:M600-IPProfile1.PNG|left|thumb|500px|Profile ID 1]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
:*Profile ID#1 for AlpahCom XE7
+
:*Profile ID#1 for AlpahCom XE
 
::*From the "Profile ID" drop-down list, select "1"
 
::*From the "Profile ID" drop-down list, select "1"
 
::*From the "Coder Group" drop-down list, select "Coder Group 1"
 
::*From the "Coder Group" drop-down list, select "Coder Group 1"
Line 314: Line 208:
 
[[Image:CoderGroupAlphaCom.jpg|left|thumb|500px|Coder Group 1]]
 
[[Image:CoderGroupAlphaCom.jpg|left|thumb|500px|Coder Group 1]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
:*Coder Group ID#1 for AlpahCom XE7
+
:*Coder Group ID#1 for AlpahCom XE
 
::*From the "Coder Group ID" drop-down list, select "1"
 
::*From the "Coder Group ID" drop-down list, select "1"
 
::*In the "Coder Name" drop-down list, select "G.711U-law" (Coder used by AlphaCom)
 
::*In the "Coder Name" drop-down list, select "G.711U-law" (Coder used by AlphaCom)
Line 333: Line 227:
 
[[Image:M600-IPProfile1.PNG|left|thumb|500px|Profile ID 1]]
 
[[Image:M600-IPProfile1.PNG|left|thumb|500px|Profile ID 1]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
:*Profile ID#1 for AlpahCom XE7
+
:*Profile ID#1 for AlpahCom XE
 
::*From the "Profile ID" drop-down list, select "1"
 
::*From the "Profile ID" drop-down list, select "1"
 
::*From the "Coder Group" drop-down list, select "Coder Group 1"
 
::*From the "Coder Group" drop-down list, select "Coder Group 1"
Line 412: Line 306:
  
 
== Proxy Sets Table ==
 
== Proxy Sets Table ==
−
[[Image:ProxySet1.JPG|thumb|350px|Proxy Set ID1]]
 
−
[[Image:ProxySet2.JPG|thumb|350px|Proxy Set ID2]]
 
−
 
 
These "Proxy Sets" are later assigned to "IP Groups"
 
These "Proxy Sets" are later assigned to "IP Groups"
 
Note that the "Proxy Set" represents the actual destination to which the call is routed
 
Note that the "Proxy Set" represents the actual destination to which the call is routed
−
<br>
 
−
<br>
 
−
:In the "Proxy Sets Table" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Proxies,Registration,IP Groups''' submenu -> '''Proxy Sets Table''' page):<br>
 
  
−
:*Proxy Set ID#1 for AlpahCom XE7
+
:In the "Proxy Sets Table" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Proxies,Registration,IP Groups''' submenu -> '''Proxy Sets Table''' page):
 +
[[Image:ProxySet1.JPG|left|thumb|500px|Proxy Set ID1]]
 +
<br style="clear:both;" />
 +
:*Proxy Set ID#1 for AlpahCom XE
 
::*From the "Proxy Set ID" drop-down list, select "1"
 
::*From the "Proxy Set ID" drop-down list, select "1"
 
::*In the "Proxy Address" column, enter the IP address of the AlphaCom
 
::*In the "Proxy Address" column, enter the IP address of the AlphaCom
 
::*From the "Transport Type" drop-down list corresponding to the IP address entered above, select "UDP"
 
::*From the "Transport Type" drop-down list corresponding to the IP address entered above, select "UDP"
 
::*Submit
 
::*Submit
−
 
+
----
−
 
+
[[Image:ProxySet2.JPG|left|thumb|500px|Proxy Set ID2]]
 +
<br style="clear:both;" />
 
:*Proxy Set ID#2 for SIP Server
 
:*Proxy Set ID#2 for SIP Server
 
::*From the "Proxy Set ID" drop-down list, select "2"
 
::*From the "Proxy Set ID" drop-down list, select "2"
Line 438: Line 330:
  
 
== IP Group Table ==
 
== IP Group Table ==
 +
These "IP Groups" are later used by the device for routing calls
 +
  
−
These "IP Groups" are later used by the device for routing calls
+
:In the "IP Group Table" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Proxies,Registration,IP Groups''' submenu -> '''IP Group Table''' page):
−
<br>
 
−
<br>
 
−
:In the "IP Group Table" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Proxies,Registration,IP Groups''' submenu -> '''IP Group Table''' page):<br>
 
  
−
[[Image:IPGrouptable-AlphaCom.jpg|thumb|350px|IP Group 1]]
+
[[Image:IPGrouptable-AlphaCom.jpg|left|thumb|500px|IP Group 1]]
 +
<br style="clear:both;" />
 
:*IP Group #1 for AlpahCom XE7
 
:*IP Group #1 for AlpahCom XE7
 
::*From the "Index" drop-down list, select "1"
 
::*From the "Index" drop-down list, select "1"
Line 453: Line 345:
  
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
 
+
----
−
[[Image:IPGrouptable-SIPserverAccount.jpg|thumb|350px|IP Group 2]]
+
[[Image:IPGrouptable-SIPserverAccount.jpg|left|thumb|500px|IP Group 2]]
 +
<br style="clear:both;" />
 
:*IP Group #2 for SIP-Server
 
:*IP Group #2 for SIP-Server
 
::*From the "Index" drop-down list, select "2"
 
::*From the "Index" drop-down list, select "2"
Line 466: Line 359:
  
 
== IP Profiles for Voice Coders ==
 
== IP Profiles for Voice Coders ==
 +
For use transcoding it's necessary create two IP Profiles for define two types of coders used.
  
−
For use transcoding it's necessary create two IP Profiles for define two types of coders used.<br>
 
 
These profiles are later used in the "Inbound IP Routing" and "Outbound IP Routing" tables.
 
These profiles are later used in the "Inbound IP Routing" and "Outbound IP Routing" tables.
−
<br>
 
−
<br>
 
−
:In the "Coder Group Settings" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Coders And Profile Definitions''' submenu -> '''Coder Group Settings''' page):<br>
 
  
−
[[Image:CoderGroupAlphaCom.jpg|thumb|350px|Coder Group 1]]
+
 
 +
:In the "Coder Group Settings" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Coders And Profile Definitions''' submenu -> '''Coder Group Settings''' page):
 +
 
 +
[[Image:CoderGroupAlphaCom.jpg|left|thumb|500px|Coder Group 1]]
 +
<br style="clear:both;" />
 
:*Coder Group ID#1 for AlpahCom XE7
 
:*Coder Group ID#1 for AlpahCom XE7
 
::*From the "Coder Group ID" drop-down list, select "1"
 
::*From the "Coder Group ID" drop-down list, select "1"
Line 479: Line 373:
 
::*Submit
 
::*Submit
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
 
+
----
−
[[Image:CoderGroupSIPServer.jpg|thumb|350px|Coder Group 2]]
+
[[Image:CoderGroupSIPServer.jpg|left|thumb|500px|Coder Group 2]]
 +
<br style="clear:both;" />
 
:*Coder Group ID#2 for SIP Server
 
:*Coder Group ID#2 for SIP Server
 
::*From the "Coder Group ID" drop-down list, select "2"
 
::*From the "Coder Group ID" drop-down list, select "2"
Line 486: Line 381:
 
::*Note: If SIP Provider supports another Codec, please choose from the drop down list.
 
::*Note: If SIP Provider supports another Codec, please choose from the drop down list.
 
::*Submit & Burn
 
::*Submit & Burn
−
 
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
 
+
----
 
:In the "IP Profile Settings" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Coders And Profile Definitions''' submenu -> '''IP Profile Settings''' page):<br>
 
:In the "IP Profile Settings" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Coders And Profile Definitions''' submenu -> '''IP Profile Settings''' page):<br>
  
−
[[Image:IPProfileAlphaCom.jpg|thumb|350px|Profile ID 1]]
+
[[Image:IPProfileAlphaCom.jpg|left|thumb|500px|Profile ID 1]]
 +
<br style="clear:both;" />
 
:*Profile ID#1 for AlpahCom XE7
 
:*Profile ID#1 for AlpahCom XE7
 
::*Enter the Profile name "AlphaCom"
 
::*Enter the Profile name "AlphaCom"
Line 497: Line 392:
 
::*From the "Coder Group" drop-down list, select "Coder Group 1"
 
::*From the "Coder Group" drop-down list, select "Coder Group 1"
 
::*Submit
 
::*Submit
−
 
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
 
+
----
−
[[Image:IPProfileSIPServer.jpg|thumb|350px|Profile ID 2]]
+
[[Image:IPProfileSIPServer.jpg|left|thumb|500px|Profile ID 2]]
 +
<br style="clear:both;" />
 
:*Profile ID#2 for SIP Server
 
:*Profile ID#2 for SIP Server
 
::*Enter the Profile name "SIP Server"
 
::*Enter the Profile name "SIP Server"
Line 506: Line 401:
 
::*In the "Coder Group" drop-down list, select "Coder Group 2"  
 
::*In the "Coder Group" drop-down list, select "Coder Group 2"  
 
::*Submit & Burn
 
::*Submit & Burn
−
 
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
 
  
 
== Account Table ==
 
== Account Table ==
−
[[Image:AccountTable.jpg|thumb|350px|Account Tables]]
+
These "Account Table" should be assigned to "IP Groups" for each account to control which account to call out with.
−
 
 
  
−
These "Account Table" should be assigned to "IP Groups" for each account to control which account to call out with.
 
 
Note that the "IP Groups" is made for each Account done in earlier step.
 
Note that the "IP Groups" is made for each Account done in earlier step.
−
<br>
 
−
<br>
 
−
:In the "Proxy Sets Table" page ('''Configuration''' tab -> '''Control Network''' menu -> '''SIP Definitions''' submenu -> '''Account Table''' page):<br>
 
  
 +
:In the "Proxy Sets Table" page ('''Configuration''' tab -> '''Control Network''' menu -> '''SIP Definitions''' submenu -> '''Account Table''' page):
 +
[[Image:AccountTable.jpg|left|thumb|500px|Account Tables]]
 +
<br style="clear:both;" />
 
:*Account Table for SIP Server
 
:*Account Table for SIP Server
 
::*Start line 1 in Add field and Press "Add"  
 
::*Start line 1 in Add field and Press "Add"  
Line 530: Line 421:
 
::*From the "Application Type" drop-down list, select "GW\IP2IP"
 
::*From the "Application Type" drop-down list, select "GW\IP2IP"
 
::*Submit
 
::*Submit
−
 
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
 
== Inbound IP Routing ==
 
== Inbound IP Routing ==
 +
The "IP to Trunk Group Routing Table" it used for define the routing inbound IP-to-IP calls.
  
−
The "IP to Trunk Group Routing Table" it used for define the routing inbound IP-to-IP calls.<br>
 
 
The table in which this is configured uses the IP Groups that you defined before.
 
The table in which this is configured uses the IP Groups that you defined before.
−
<br>
 
−
<br>
 
−
:In the "IP to Trunk Group Routing Table" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Routing Tables''' submenu -> '''IP to Trunk Group Routing''' page):<br>
 
  
−
[[Image:IP-to-Tel-Routing.jpg|thumb|350px|Inbound IP Routing]]
+
:In the "IP to Trunk Group Routing Table" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Routing Tables''' submenu -> '''IP to Trunk Group Routing''' page):
 +
[[Image:IP-to-Tel-Routing.jpg|left|thumb|500px|Inbound IP Routing]]
 +
<br style="clear:both;" />
  
 
:*Index#1 for AlpahCom XE7
 
:*Index#1 for AlpahCom XE7
Line 564: Line 453:
  
 
== Outbound IP Routing ==
 
== Outbound IP Routing ==
 +
The "Tel to IP Routing Table" it used for define the routing outbound IP-to-IP calls.
  
−
The "Tel to IP Routing Table" it used for define the routing outbound IP-to-IP calls.<br>
 
 
The table in which this is configured uses the IP Groups that you defined before.
 
The table in which this is configured uses the IP Groups that you defined before.
−
<br>
 
−
<br>
 
−
:In the "Tel to IP Routing" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Routing Tables''' submenu -> '''Tel to IP Routing''' page):<br>
 
−
 
−
[[Image:Tel-to-IP-Routing.jpg|thumb|350px|Outbound IP Routing]]
 
  
 +
:In the "Tel to IP Routing" page ('''Configuration''' tab -> '''Protocol Configuration''' menu -> '''Routing Tables''' submenu -> '''Tel to IP Routing''' page):
 +
[[Image:Tel-to-IP-Routing.jpg|left|thumb|500px|Outbound IP Routing]]
 +
<br style="clear:both;" />
 
:*Index#1 from AlpahCom XE7 to SIPServer
 
:*Index#1 from AlpahCom XE7 to SIPServer
 
::*Src.IPGroupID : select "1" to indicate received (inbound) calls identified as belonging to the IP Group configured for AlphaCom  
 
::*Src.IPGroupID : select "1" to indicate received (inbound) calls identified as belonging to the IP Group configured for AlphaCom  
Line 588: Line 475:
  
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
 
  
 
== Manipulation Table ==
 
== Manipulation Table ==
−
[[Image:Manipulation-table-Outgoing-call.jpg|thumb|350px|Manipulation Tel->IP Calls]]
+
This step will change the local SIP ID/Dir No to number associated to SIP accounts.
  
−
This step will change the local SIP ID/Dir No to number associated to SIP accounts.
 
−
<br>
 
−
<br>
 
 
:In the "Source Number Tel->IP" page ('''VoIP''' tab -> '''Control Network''' menu -> '''GW and IP to IP''' submenu -> '''Manipulation''' page):
 
:In the "Source Number Tel->IP" page ('''VoIP''' tab -> '''Control Network''' menu -> '''GW and IP to IP''' submenu -> '''Manipulation''' page):
−
 
+
[[Image:Manipulation-table-Outgoing-call.jpg|left|thumb|500px|Manipulation Tel->IP Calls]]
 +
<br style="clear:both;" />
 
:*Manipulation Table for Outgoing Calls
 
:*Manipulation Table for Outgoing Calls
  
 +
----
  
−
[[Image:Manipulation-table-inncoming-call.jpg|thumb|350px|Manipulation IP-> Tel Calls]]
 
  
 
This step is necessary to route inncoming call to right Extension on AlphaCom side.  
 
This step is necessary to route inncoming call to right Extension on AlphaCom side.  
−
<br>
+
 
−
<br>
 
 
:In the "Dest Number IP->Tel" page ('''VoIP''' tab -> '''Control Network''' menu -> '''GW and IP to IP''' submenu -> '''Manipulation''' page):<br>
 
:In the "Dest Number IP->Tel" page ('''VoIP''' tab -> '''Control Network''' menu -> '''GW and IP to IP''' submenu -> '''Manipulation''' page):<br>
−
 
+
[[Image:Manipulation-table-inncoming-call.jpg|left|thumb|500px|Manipulation IP-> Tel Calls]]
 +
<br style="clear:both;" />
 
:*Manipulation Table for route the inncoming call
 
:*Manipulation Table for route the inncoming call
 
::*Submit
 
::*Submit
Line 643: Line 527:
 
<br/>
 
<br/>
 
<br/>
 
<br/>
−
For configuration of the Cisco Call Manager please see [[Configuration guide for Cisco Call Manager 6]].
+
For configuration of the Cisco Call Manager please see [[Cisco Call Manager 6 configuration guide]].
  
 
The following highlighted points deviate from the standard CUCM configuration and are special for the SIP2SIP transcoding with AlphaCom using AudioCodes Mediant 600:
 
The following highlighted points deviate from the standard CUCM configuration and are special for the SIP2SIP transcoding with AlphaCom using AudioCodes Mediant 600:
  
 
== Configure a Region ==
 
== Configure a Region ==
−
[[Image:SIP2SIP-Cisco-Region.PNG|350px|thumb|Region Configuration]]
+
[[Image:SIP2SIP-Cisco-Region.PNG|left|500px|thumb|Region Configuration]]
 +
<br style="clear:both;" />
 
:System -> Region -> Add New
 
:System -> Region -> Add New
 
::*Name: Zenitel
 
::*Name: Zenitel
Line 659: Line 544:
  
 
== Configure a SIP Trunk ==
 
== Configure a SIP Trunk ==
−
[[Image:CiscoSipTrunk 1.PNG|thumb|350px|Trunk Configuration]]
+
[[Image:CiscoSipTrunk 1.PNG|left|thumb|500px|Trunk Configuration]]
−
[[Image:CiscoSipTrunk 2.PNG|thumb|350px|Trunk Configuration, continued]]
+
<br style="clear:both;" />
−
[[Image:SIP2SIP-Cisco-SIPTrunk.PNG|thumb|350px|Trunk Configuration, continued]]
+
[[Image:CiscoSipTrunk 2.PNG|left|thumb|500px|Trunk Configuration, continued]]
 +
<br style="clear:both;" />
 +
[[Image:SIP2SIP-Cisco-SIPTrunk.PNG|left|thumb|500px|Trunk Configuration, continued]]
 +
<br style="clear:both;" />
 
:Device -> Trunk -> Add New
 
:Device -> Trunk -> Add New
 
::*Trunk Type: SIP Trunk
 
::*Trunk Type: SIP Trunk
Line 689: Line 577:
  
 
== SIP settings ==
 
== SIP settings ==
−
[[Image:MV-370-SIP.PNG|thumb|SIP Settings]]
+
[[Image:MV-370-SIP.PNG|left|thumb|500px|SIP Settings]]
 +
<br style="clear:both;" />
 
In the menu '''SIP Settings -> Service Domain''', enter information for "Realm 1":
 
In the menu '''SIP Settings -> Service Domain''', enter information for "Realm 1":
 
:*'''Active''' = ON
 
:*'''Active''' = ON
Line 701: Line 590:
  
 
== Codec settings ==
 
== Codec settings ==
−
[[Image:MV-370-Codec.PNG|thumb|Codec Settings]]
+
[[Image:MV-370-Codec.PNG|left|thumb|500px|Codec Settings]]
 +
<br style="clear:both;" />
 
In the menu '''SIP Settings -> Codec Settings''', set codec priority:
 
In the menu '''SIP Settings -> Codec Settings''', set codec priority:
 
:*'''Codec Priority 1:''' = G.729
 
:*'''Codec Priority 1:''' = G.729
Line 708: Line 598:
  
  
−
[[Category:SIP]]
+
[[Category:AlphaCom - SIP Integration]]
 
[[Category:3rd party integration]]
 
[[Category:3rd party integration]]

Latest revision as of 11:39, 15 August 2022

AlphaCom icon 300px.png

The Mediant 600 has the capability to transcode a SIP call from e.g. G711µ-law to G729. Here are some examples using the Mediant 600 to transcode G711µ-law to G729.

The examples shown are between:

  • AlphaCom XE and Cisco Call Manager
  • AlphaCom XE and AudioCodes MP-114/118
  • AlphaCom XE and Mobile VoIP GSM Gateway MV-370
Configuration example


AlphaCom Configuration

How to set up a SIP Trunk in the AlphaCom is described here: SIP trunk node - configuration

Mediant 600 Configuration

A license SIP to SIP Mediation and Routing Application (SW/IP2IP/15) is required. With this license, the Mediant600 has 30 active Media Channels that can support 15 transcoding simultane sessions.

Restore to factory default settings

Reset Button


  • With a paper clip, press and hold down the Reset button (located on the CPU Module) for at least 12 seconds (no more than 25 seconds)
  • The device restores to factory default settings

Access to the embedded web server

Home Page


The default Network parameter of the Mediant 600:
  • IP Adress : 10.1.10.10
  • Subnet Mask : 255.255.0.0
  • Default Gateway : 0.0.0.0


Connect your PC directly to the device, using an Ethernet Crossover cable


Before the PC can access to the Mediant 600, the IP address of the PC must be changed to match the same subnet (e.g 10.1.10.11)


To access the embedded web server, start your internet browser (e.g. Internet Explorer) and in the address field enter 10.1.10.10


You will be prompted for a username and password (default):
  • Username: Admin
  • Password: Admin


The Home Page page should now be displayed


Note: For the rest of configuration used the tree menu in Full mode

IP Configuration

Initial configuration


RETURN TO THIS

IP Settings


In the "IP Settings" page (Configuration tab -> Network Settings menu -> IP Settings page) enter :
  • IP Adress
  • Subnet Mask
  • Default Gateway
  • Click "Submit" to apply the changes
The IP address is immediately changed when pressing Submit, but it is not permanently stored
Without resetting or powering off the device, you need to log on to the Gateway using its new IP address in order to Burn the new IP address to flash:
  • Disconnect the PC from the Gateway
  • Connect the Gateway and PC to the LAN. The PC and Gateway must be on the same sub-net
  • Restore the PC’s IP address and subnet mask to what they originally were, and re-access the Gateway using the new assigned IP address
  • Click "Burn" to permanently apply the changes

Add Software Upgrade Key

The license for SIP IP2IP must be uploaded as a Software Upgrade Key.

Software Upgrade Key


In the "Software Upgrade Key Status" page (Management tab -> Software Update menu -> Software Upgrade Key page):
  • Enter the license key in the "Add a Software Upgrade Key" field
  • Click "Add Key"
  • Burn
  • Reset the device (Device Action -> Reset -> Reset)

Enable IP-to-IP Capabilities

Applications Enabling


In the "Applications Enabling" page (Configuration tab -> Protocol Configuration menu -> Applications Enabling page):
  • From the "Enable IP2IP Application" drop-down list, select "Enable"
  • Submit & Burn
  • Wait the next step for Reset the device

Number of Media Channels

IP Media Settings


In the "IP Media Settings" page (Configuration tab -> Media Settings menu -> IP Media Settings page):
  • In the "Number of Media Channeles" field, enter the required number of media channels: 30 (maximum capacity of Mediant 600 is 60)
  • Submit & Burn
  • Reset the device (Device Action -> Reset -> Reset)

Proxy Sets Table

These "Proxy Sets" are later assigned to "IP Groups" Note that the "Proxy Set" represents the actual destination to which the call is routed

In the "Proxy Sets Table" page (Configuration tab -> Protocol Configuration menu -> Proxies,Registration,IP Groups submenu -> Proxy Sets Table page):
Proxy Set ID1


  • Proxy Set ID#1 for AlpahCom XE
  • From the "Proxy Set ID" drop-down list, select "1"
  • In the "Proxy Address" column, enter the IP address of the AlphaCom
  • From the "Transport Type" drop-down list corresponding to the IP address entered above, select "UDP"
  • Submit
Proxy Set ID2


  • Proxy Set ID#2 for MP-114
  • From the "Proxy Set ID" drop-down list, select "2"
  • In the "Proxy Address" column, enter the IP address of the MP-114
  • From the "Transport Type" drop-down list corresponding to the IP address entered above, select "UDP"
  • Submit & Burn


IP Group Table

These "IP Groups" are later used by the device for routing calls

In the "IP Group Table" page (Configuration tab -> Protocol Configuration menu -> Proxies,Registration,IP Groups submenu -> IP Group Table page):
IP Group 1


  • IP Group #1 for AlpahCom XE
  • From the "Index" drop-down list, select "1"
  • In the "Description" field, type an arbitrary name for the IP Group (e.g. AlphaCom)
  • From the "Proxy Set ID" drop-down list, select "1" (For this "IP Group" communicate with the "Proxy Set" of the AlphaCom)
  • In the "SIP Group Name" field, enter the IP Adress sent in the SIP Request From/To headers for this IP Group (AlphaCom's IP Adress)
  • Contact User = name that is sent in the SIP Request contact header for this IP Group (e.g. AXE)
  • From the "IP Profile ID" drop-down list, select "1" (the IP Profile is configured later)
  • Submit
IP Group 2


  • IP Group #2 for MP-114
  • From the "Index" drop-down list, select "2"
  • In the "Description" field, type an arbitrary name for the IP Group (e.g. MP114)
  • From the "Proxy Set ID" drop-down list, select "2" (For this "IP Group" communicate with the "Proxy Set" of the MP-114)
  • In the "SIP Group Name" field, enter the IP Adress sent in the SIP Request From/To headers for this IP Group (MP-114's IP Adress)
  • Contact User = name that is sent in the SIP Request contact header for this IP Group (e.g. MP114)
  • From the "IP Profile ID" drop-down list, select "2" (the IP Profile is configured later)
  • Submit & Burn


IP Profiles for Voice Coders

For use transcoding it's necessary create two IP Profiles for define two types of coders used.

These profiles are later used in the "Inbound IP Routing" and "Outbound IP Routing" tables.


In the "Coder Group Settings" page (Configuration tab -> Protocol Configuration menu -> Coders And Profile Definitions submenu -> Coder Group Settings page):
Coder Group 1


  • Coder Group ID#1 for AlphaCom XE
  • From the "Coder Group ID" drop-down list, select "1"
  • In the "Coder Name" drop-down list, select "G.711U-law" (Coder used by AlphaCom)
  • Submit


Coder Group 2


  • Coder Group ID#2 for MP-114
  • From the "Coder Group ID" drop-down list, select "2"
  • In the "Coder Name" drop-down list, select "G.729" (Coder used by MP-114)
  • Submit & Burn


In the "IP Profile Settings" page (Configuration tab -> Protocol Configuration menu -> Coders And Profile Definitions submenu -> IP Profile Settings page):
Profile ID 1


  • Profile ID#1 for AlpahCom XE
  • From the "Profile ID" drop-down list, select "1"
  • From the "Coder Group" drop-down list, select "Coder Group 1"
  • Submit


Profile ID 2


  • Profile ID#2 for MP-114
  • From the "Profile ID" drop-down list, select "2"
  • In the "Coder Group" drop-down list, select "Coder Group 2"
  • Submit & Burn


IP Profiles for Voice Coders

For use transcoding it's necessary create two IP Profiles for define two types of coders used.

These profiles are later used in the "Inbound IP Routing" and "Outbound IP Routing" tables.


In the "Coder Group Settings" page (Configuration tab -> Protocol Configuration menu -> Coders And Profile Definitions submenu -> Coder Group Settings page):
Coder Group 1


  • Coder Group ID#1 for AlpahCom XE
  • From the "Coder Group ID" drop-down list, select "1"
  • In the "Coder Name" drop-down list, select "G.711U-law" (Coder used by AlphaCom)
  • Submit


Coder Group 2


  • Coder Group ID#2 for MP-114
  • From the "Coder Group ID" drop-down list, select "2"
  • In the "Coder Name" drop-down list, select "G.729" (Coder used by SIP Server)
  • Submit & Burn


In the "IP Profile Settings" page (Configuration tab -> Protocol Configuration menu -> Coders And Profile Definitions submenu -> IP Profile Settings page):
Profile ID 1


  • Profile ID#1 for AlpahCom XE
  • From the "Profile ID" drop-down list, select "1"
  • From the "Coder Group" drop-down list, select "Coder Group 1"
  • Submit


Profile ID 2


  • Profile ID#2 for MP-114
  • From the "Profile ID" drop-down list, select "2"
  • In the "Coder Group" drop-down list, select "Coder Group 2"
  • Submit & Burn


Inbound IP Routing

The "IP to Trunk Group Routing Table" it used for define the routing inbound IP-to-IP calls.

The table in which this is configured uses the IP Groups that you defined before.


In the "IP to Trunk Group Routing Table" page (Configuration tab -> Protocol Configuration menu -> Routing Tables submenu -> IP to Trunk Group Routing page):
Inbound IP Routing


  • Index#1 for AlpahCom XE7
  • Dest Phone Prefix : enter the asterisk (*) symbol to indicate all destinations
  • Source Phone Prefix : enter the asterisk (*) symbol to indicate all destinations
  • Source IP Adress : enter the IP adress of the AlphaCom
  • Trunk Group ID : enter "-1" to indicate that these calls are IP-to-IP calls
  • IP Profile ID : enter "1" to assign these calls to "ProfileID#1" to use "G.711U-law"
  • Source IP Groupe ID : enter "1" to assign these calls to the IP Group pertaining to the AlphaCom
  • Index#2 for MP-114
  • Dest Phone Prefix : enter the asterisk (*) symbol to indicate all destinations
  • Source Phone Prefix : enter the asterisk (*) symbol to indicate all destinations
  • Source IP Adress : enter the IP adress of the MP-114
  • Trunk Group ID : enter "-1" to indicate that these calls are IP-to-IP calls
  • IP Profile ID : enter "2" to assign these calls to "ProfileID#2" to use "G.729"
  • Source IP Groupe ID : enter "2" to assign these calls to the IP Group pertaining to the MP-114
  • Submit & Burn


Outbound IP Routing

The "Tel to IP Routing Table" it used for define the routing outbound IP-to-IP calls.

The table in which this is configured uses the IP Groups that you defined before.


In the "Tel to IP Routing" page (Configuration tab -> Protocol Configuration menu -> Routing Tables submenu -> Tel to IP Routing page):
Outbound IP Routing


  • Index#1 from AlpahCom XE7 to MP-114
  • Src.IPGroupID : select "1" to indicate received (inbound) calls identified as belonging to the IP Group configured for AlphaCom
  • Dest. Phone Prefix : enter the asterisk (*) symbol to indicate all destinations and callers respectively
  • Dest.IPGroupID : select "2" to indicate the destination IP Group to where these calls are sent, to the MP-114.
  • IP Profile ID : enter "2" to indicate the IP Profile configured for "G.729"


  • Index#2 from MP-114 to AlphaCom XE7
  • Src.IPGroupID : select "2" to indicate received (inbound) calls identified as belonging to the IP Group configured for MP-114
  • Dest. Phone Prefix : enter the asterisk (*) symbol to indicate all destinations and callers respectively
  • Dest.IPGroupID : select "1" to indicate the destination IP Group to where these calls are sent, to the AlphaCom.
  • IP Profile ID : enter "1" to indicate the IP Profile configured for "G.711µ-law"
  • Submit & Burn


Configuration of Mediant 600 with SIP Account as End Point

A license SIP to SIP Mediation and Routing Application (SW/IP2IP) is required. This section is additional to section = Mediant 600 Configuration =

Proxy Sets Table

These "Proxy Sets" are later assigned to "IP Groups" Note that the "Proxy Set" represents the actual destination to which the call is routed

In the "Proxy Sets Table" page (Configuration tab -> Protocol Configuration menu -> Proxies,Registration,IP Groups submenu -> Proxy Sets Table page):
Proxy Set ID1


  • Proxy Set ID#1 for AlpahCom XE
  • From the "Proxy Set ID" drop-down list, select "1"
  • In the "Proxy Address" column, enter the IP address of the AlphaCom
  • From the "Transport Type" drop-down list corresponding to the IP address entered above, select "UDP"
  • Submit
Proxy Set ID2


  • Proxy Set ID#2 for SIP Server
  • From the "Proxy Set ID" drop-down list, select "2"
  • In the "Proxy Address" column, enter the IP address of the SIP server
  • From the "Transport Type" drop-down list corresponding to the IP address entered above, select "UDP"
  • Set Enable Proxy Keep Alive to "Using Register"
  • Submit & Burn


IP Group Table

These "IP Groups" are later used by the device for routing calls


In the "IP Group Table" page (Configuration tab -> Protocol Configuration menu -> Proxies,Registration,IP Groups submenu -> IP Group Table page):
IP Group 1


  • IP Group #1 for AlpahCom XE7
  • From the "Index" drop-down list, select "1"
  • In the "Description" field, type an arbitrary name for the IP Group (e.g. AlphaCom)
  • From the "Proxy Set ID" drop-down list, select "1" (For this "IP Group" communicate with the "Proxy Set" of the AlphaCom)
  • From the "IP Profile ID" drop-down list, select "1" (the IP Profile is configured later)
  • Submit


IP Group 2


  • IP Group #2 for SIP-Server
  • From the "Index" drop-down list, select "2"
  • In the "Description" field, type an arbitrary name for the IP Group (e.g. 51215382)
  • From the "Proxy Set ID" drop-down list, select "2" (For this "IP Group" communicate with the "Proxy Set" of the SIPServer)
  • If more then one Account, repeat the same above with IP Group nr not in use(e.g. IP Group nr 3)
  • From the "IP Profile ID" drop-down list, select "2". Do the same for all other IP Group associated with SIP Servers IP Groups(the IP Profile is configured later)
  • Submit & Burn


IP Profiles for Voice Coders

For use transcoding it's necessary create two IP Profiles for define two types of coders used.

These profiles are later used in the "Inbound IP Routing" and "Outbound IP Routing" tables.


In the "Coder Group Settings" page (Configuration tab -> Protocol Configuration menu -> Coders And Profile Definitions submenu -> Coder Group Settings page):
Coder Group 1


  • Coder Group ID#1 for AlpahCom XE7
  • From the "Coder Group ID" drop-down list, select "1"
  • In the "Coder Name" drop-down list, select "G.711U-law" (Coder used by AlphaCom)
  • Submit


Coder Group 2


  • Coder Group ID#2 for SIP Server
  • From the "Coder Group ID" drop-down list, select "2"
  • In the "Coder Name" drop-down list, select "G.729" (Coder used by SIP Server)
  • Note: If SIP Provider supports another Codec, please choose from the drop down list.
  • Submit & Burn


In the "IP Profile Settings" page (Configuration tab -> Protocol Configuration menu -> Coders And Profile Definitions submenu -> IP Profile Settings page):
Profile ID 1


  • Profile ID#1 for AlpahCom XE7
  • Enter the Profile name "AlphaCom"
  • From the "Profile ID" drop-down list, select "1"
  • From the "Coder Group" drop-down list, select "Coder Group 1"
  • Submit


Profile ID 2


  • Profile ID#2 for SIP Server
  • Enter the Profile name "SIP Server"
  • From the "Profile ID" drop-down list, select "2"
  • In the "Coder Group" drop-down list, select "Coder Group 2"
  • Submit & Burn


Account Table

These "Account Table" should be assigned to "IP Groups" for each account to control which account to call out with.

Note that the "IP Groups" is made for each Account done in earlier step.

In the "Proxy Sets Table" page (Configuration tab -> Control Network menu -> SIP Definitions submenu -> Account Table page):
Account Tables


  • Account Table for SIP Server
  • Start line 1 in Add field and Press "Add"
  • Set Served IP Group to 1
  • Set Served IP Trunk Group to -1
  • Set Serving IP Group same as the Serving IP group associated in IP Group used by this account.
  • Set Username and Password due to information from SIP Provider
  • From the "Register" drop-down list, select "YES"
  • Set "Contact User" to SIP ID
  • From the "Application Type" drop-down list, select "GW\IP2IP"
  • Submit


Inbound IP Routing

The "IP to Trunk Group Routing Table" it used for define the routing inbound IP-to-IP calls.

The table in which this is configured uses the IP Groups that you defined before.

In the "IP to Trunk Group Routing Table" page (Configuration tab -> Protocol Configuration menu -> Routing Tables submenu -> IP to Trunk Group Routing page):
Inbound IP Routing


  • Index#1 for AlpahCom XE7
  • Dest Phone Prefix : enter the asterisk (*) symbol to indicate all destinations
  • Source Phone Prefix : enter the asterisk (*) symbol to indicate all destinations
  • Source IP Adress : enter the IP adress of the AlphaCom
  • Trunk Group ID : enter "-1" to indicate that these calls are IP-to-IP calls
  • IP Profile ID : enter "1" to assign these calls to "ProfileID#1" to use "G.711U-law"
  • Source IP Groupe ID : enter "1" to assign these calls to the IP Group pertaining to the AlphaCom
  • Index#2 for SIP Server
  • Dest Phone Prefix : enter the asterisk (*) symbol to indicate all destinations
  • Source Phone Prefix : enter the asterisk (*) symbol to indicate all destinations
  • Source IP Adress : enter * to receive calls from all URL/IP adresses of the SIP server
  • Trunk Group ID : enter "-1" to indicate that these calls are IP-to-IP calls
  • IP Profile ID : enter "2" to assign these calls to "ProfileID#2" to use "G.729"
  • Source IP Groupe ID : enter "2" to assign these calls to the IP Group pertaining to the SIP Server
  • Note: Enter Sorce IP Group nr of the every account you register in Accout Table in next step
  • Submit & Burn


Outbound IP Routing

The "Tel to IP Routing Table" it used for define the routing outbound IP-to-IP calls.

The table in which this is configured uses the IP Groups that you defined before.

In the "Tel to IP Routing" page (Configuration tab -> Protocol Configuration menu -> Routing Tables submenu -> Tel to IP Routing page):
Outbound IP Routing


  • Index#1 from AlpahCom XE7 to SIPServer
  • Src.IPGroupID : select "1" to indicate received (inbound) calls identified as belonging to the IP Group configured for AlphaCom
  • Dest. Phone Prefix : enter the asterisk (*) symbol to indicate all destinations and callers respectively
  • Dest.IPGroupID : select "2" to indicate the destination IP Group to where these calls are sent, to the SIP-Server
  • IP Profile ID : enter "2" to indicate the IP Profile configured for "G.729"
  • Note: Enter a new line with "Source Phone Prefix" set to Extension and "Dest. IP Group ID" to associated SIP account. This to control which SIP Account the each extension is using.
  • Index#2 from SIP Server to AlphaCom XE7
  • Src.IPGroupID : select "2" to indicate received (inbound) calls identified as belonging to the IP Group configured for MP-114
  • Dest. Phone Prefix : enter the asterisk (*) symbol to indicate all destinations and callers respectively
  • Dest.IPGroupID : select "1" to indicate the destination IP Group to where these calls are sent, to the AlphaCom.
  • IP Profile ID : enter "1" to indicate the IP Profile configured for "G.711µ-law"
  • Submit & Burn


Manipulation Table

This step will change the local SIP ID/Dir No to number associated to SIP accounts.

In the "Source Number Tel->IP" page (VoIP tab -> Control Network menu -> GW and IP to IP submenu -> Manipulation page):
Manipulation Tel->IP Calls


  • Manipulation Table for Outgoing Calls


This step is necessary to route inncoming call to right Extension on AlphaCom side.

In the "Dest Number IP->Tel" page (VoIP tab -> Control Network menu -> GW and IP to IP submenu -> Manipulation page):
Manipulation IP-> Tel Calls


  • Manipulation Table for route the inncoming call
  • Submit


AudioCodes MP-114/118 Configuration

All text and pictures refer to version 5.80

For configuration of the MP114/118 please see Configuration guide for AudioCodes MP114/118, v5.4 and higher.

The following highlighted points deviate from the standard MP114/118 configuration and are special for the SIP2SIP transcoding with AlphaCom using AudioCodes Mediant 600:

SIP Parameters

In the Proxy & Registration page (Configuration tab -> Protocol Configuration menu -> Protocol Definition submenu -> Proxy & Registration page item) set the ‘Use Default Proxy’ field to ‘Yes’.
  • Proxy Name must be blank
  • Gateway Name must be blank
  • Click the Proxy Set Table button. In the ‘Proxy Address’ field enter the IP address of the Mediant 600.
  • Set 'Transport Type' to 'UDP'.

SIP Parameters.jpg

  • Press Submit to save changes

Audio Codec

Select the voice coder in 'Coders Table' page (Configuration tab -> Protocol Configuration menu -> Protocol Definition submenu -> Coders page item).
  • From the drop-down list select G.729

MP114-Coders.JPG

  • Press Submit to save changes

Cisco Call Manager Configuration

All text and pictures refer to version 6.1.2

For configuration of the Cisco Call Manager please see Cisco Call Manager 6 configuration guide.

The following highlighted points deviate from the standard CUCM configuration and are special for the SIP2SIP transcoding with AlphaCom using AudioCodes Mediant 600:

Configure a Region

Region Configuration


System -> Region -> Add New
  • Name: Zenitel
  • Press Save
  • Under Modify Relationships to other Regions select Zenitel.
  • Select Audio Codec to G.729
  • Press Save
  • Press Reset/Restart


Configure a SIP Trunk

Trunk Configuration


Trunk Configuration, continued


Trunk Configuration, continued


Device -> Trunk -> Add New
  • Trunk Type: SIP Trunk
  • Device Protocol: SIP
  • Press Next
  • Device Name: AlphaCom
  • Description: AlphaCom
  • Device Pool: Zenitel
  • Media Resource Group List: AlphaCom_MRGL
  • Enable: 'Media Termination Point Required'
  • Calling Search Space: DefaultUser
  • Destination Adress: The IP adress of the Mediant 600
  • SIP Trunk Security Profile: AlphaCom
  • SIP Profile: Standard SIP Profile
  • Press Save
  • Press Reset/Restart


Mobile VoIP GSM Gateway MV-370

All text and pictures refer to version 6.693.t

For configuration of the MV-370 please see Configuration guide for Mobile VoIP.

The following highlighted points deviate from the standard MV-370 configuration and are special for the SIP2SIP transcoding with AlphaCom using AudioCodes Mediant 600:

SIP settings

SIP Settings


In the menu SIP Settings -> Service Domain, enter information for "Realm 1":

  • Active = ON
  • User Name = Any text, used for Caller ID. This text will be shown in the display on incoming calls from the GSM network, together with the telephone number
  • Proxy Server = IP address of the Mediant 600

Status will show Not Registered.

Enable DTMF signalling by SIP INFO method:

  • SIP Settings > DTMF Setting: Enable Send DTMF SIP Info

Codec settings

Codec Settings


In the menu SIP Settings -> Codec Settings, set codec priority:

  • Codec Priority 1: = G.729

Leave the rest as is.

Retrieved from "https://wiki.zenitel.com/w/index.php?title=SIP2SIP_Transcoding_using_Mediant_600&oldid=230684"