SIP to SIP - Initial Configuration
- Kelli Higdon
Â
Â
The diagram below displays a call scenario where transcoding is being achieved. The call scenarios are the following:
The first call scenario is where the SIP Client calls the IP Phone by dialing 508-555-9876. The call is routed through the IMG 2020 and the G.711 codec is replaced with a G.729 codec.* The second call scenario is where the IP Phone calls the SIP Client by dialing the number 617-555-1234, the call is routed through the IMG 2020 and the G.729 codec is replaced with a G.711 codec.The diagram below displays the scenarios. The procedure will describe how to configured the IMG 2020 to accomplish the scenarios described above. The procedure starts with creating the IMG 2020 node and goes through each of the steps needed. Use the procedure as a guide to creating your own configuration.
Â
Â
Configure the Physical IMG 2020 Node
Start by connecting to the IMG 2020 and creating the IMG 2020 Node object. Follow procedure below to configure the physical node object.
Right click on the Dialogic object and select New IMG 2020. Enter a name in the Name field that identifies this node.
Select the Media Mode from the drop down menu in the Media Mode field.
Click on the Commit icon and the Node object will automatically get populated with information from the IMG 2020. Refer to the topic for feature and functionality information on this object.
Create IP and SIP Profiles
Some of the objects such as TDM DS-1's, Packet Facilities, and External Signaling Gateways need to be associated with a specific profile that was previously configured. The profiles are created and linked to each of the items. Follow procedure below to create each of the Profiles.
Right click on the Dialogic object and select New Profiles. The Profiles object is a container object and no configuration is needed here. Refer to the Profiles topic for more information on this object.
Right click on the Profiles object and select New IP Profiles. The IP Profiles object is a parent or container object also. No configuration is needed in this object. Refer to the IP Profiles topic for more information on this object.
Right click on the IP Profiles object and select New IP Profile. The IP Profile being configured will be used on the incoming leg of the IMG 2020. In this example it will be labeled IP_Profile_G711. This profile will be used later in the procedure when creating channel groups. Refer to the IP Profile topic for more information on configuring the individual fields within this object.
Right click on IP Profile and select New Vocoder Profile. A Vocoder Profile object will get created. Select a Payload type from the drop down menu and modify the object as needed. Refer to the Vocoder Profile topic for more information on configuring this object. In this example, G.711 ulaw was selected.
Right click on the IP Profiles object and select New IP Profile again. This IP Profile will be used on the outgoing leg of the IMG 2020. In this example it will be labeled IP_Profile_G729. This profile will be used later in the procedure when creating channel groups. For more information refer to IP Profile topic.
Right click on IP Profile just created and select New Vocoder Profile. A Vocoder Profile object will get created. Select a Payload type from the drop down menu and modify the object as needed. Refer to the Vocoder Profile topic for more information on configuring this object. In this example, G.729 was selected.
Right click on the Profiles object and select New SIP Profiles. The SIP Profiles object is a parent or container object. No configuration is needed in this object. Refer to the SIP Profiles topic for more information on this object.
Right click on the SIP Profiles object created and select New SIP Profile. The first SIP Profile that gets created is a default profile and cannot be modified.
The first SIP Profile created is a default SIP Profile and cannot be modified. The user can either use the default profile as configured or created a second profile that can be modified as described in next step below.
Right click on the SIP Profiles again and select New SIP Profile again. The SIP Profile that now appears can be modified for your specific network needs. Either accept the Default name in the Name field or modify the name to a name that identifies this SIP Profile. In this example the default name of SIP_Profile_1 was accepted. Refer to the SIP Profile - SGP topic for more information on configuring this object.
(OPTIONAL)
Right click on the SIP Profile object and select New SIP Advanced Settings. A SIP advanced settings object will appear and display more SIP parameters that can be configured to be associated with the SIP Profile being created above. Refer to the SIP Profile - Advanced Settings topic for more information on configuring the individual fields.
Right click on the SIP Profile object again and select any of the remaining SIP features from the drop down menu. These features will be associated with the SIP Profile being created above. The SIP Profile object being created will be used later when configuring SIP Signaling, External Gateways, or ENUM Servers. Refer to the Configure SIP Profile Options topic for a list of optional objects that can get configured.
Once all the IP and SIP profile objects have been created and configured, they need to be downloaded to the IMG 2020. Click on the Profiles object which will have a yellow exclamation point on the Icon which indicates the configuration has not been sent to the IMG 2020. Click on the Download Profiles button in the Profiles object pane and the Profiles configuration will be sent to the IMG 2020.
Configure SIP Signaling Stack
Configure the SIP Signaling stack that will be used by IMG 2020. The SIP stack must be created for each IMG 2020 physical node.
Right click on the IMG 2020 physical node object and select New Signaling. The Signaling object that appears is a parent or container object. No configuration needed within this object. Refer to the Signaling topic for more information on this object.
Right click on the Signaling object and select New SIP. A SIP signaling object gets created. The SIP Signaling IP address automatically takes the IP address of the CTRL interface on rear of IMG 2020. This can be modified as needed by selecting a different IP address from the drop down menu of all IP addresses configured that will allow SIP signaling to be processed. Â Refer to SIP Signaling - SIP topic for more information on configuring each of the individual fields.
Configure the Network Interface <Control> to be used for Signaling
To enable the IMG 2020 to function over an IP network the Source Endpoints in the IMG 2020 must have an IP address assigned to them, and then must be configured to communicate through a specific interface on the rear of the IMG 2020. The steps below describe the configuration needed to configure the Source Endpoint "Services" and then configure which network interface to process the CPU signaling information through.
Right click on the Physical Node and select New Network. The IP Network object is a parent or container object and no configuration is applied here. Refer to the IP Network Interface topic for more information on this object.
Right click on the IP Network object that is created and select New IP Address. In the Source Endpoint field select Services from drop down menu.
In the Logical Interface field, select Control from the drop down menu. In this procedure, the SIP signaling will be processed through the Control Interface.
Enter an IP address into the IP address field. This will be the IP address of the SIP Signaling Services resource being configured.
In the Default Gateway field enter the IP address of the default gateway that is communicating with the SIP Signaling Service resource endpoint. Refer to the IP Address topic for information on configuring each of the individual fields.Â
Configure the Network Interface Data A to be used for RTP
To enable the IMG 2020 to function over an IP network the Source Endpoint Resources in the IMG 2020 must have an IP address assigned to them, and must be configured to communicate through a specific interface on the rear of the IMG 2020. The steps below describe the configuration needed to configure the Source Endpoint "Media 0" and then configure which network interface to process the Media 0 resource RTP information through.
Right click on the IP Network object that is created and select New IP Address. In the Source Endpoint field select Media 0 from drop down menu.
In this example, the Source Endpoint configured, will process the data through the Data A interface. Select Data A from the drop down menu of the Logical Interface field. Data A corresponds to the interface on the rear of the IMG 2020 labeled Data A.
In the procedure, the Source Endpoint selected was Media 0. Typically, Media 0 is an Endpoint for RTP data. The Media object uses a group of DSP Resources in the IMG 2020 for processing RTP data.
Enter an IP address into the IP Address field. The IP address entered will be given to the DSP Resources and will process the data through the Data A interface. This resource will be used to process RTP data.
In the Default Gateway field enter the IP address of the Default Gateway that the IMG 2020 is connected to. Refer to the topic for more information on configuring each of the individual fields in this object.Â
Create Facility Object (VoIP Packet Facilities)
Right click on the IMG 2020 physical node object and select New Facility. The Facility object is a parent or container object and no configuration is needed in the object. Refer to the Facility topic for more information on this object.
Right click on the Facility object and select New Packet Facilities. The Packet Facilities object is a container object also. Refer to the Packet Facilities topic for more information on this object.
Â
Once all functionality above has been configured, continue on to the SIP to SIP - Configure Media topic.