How to Connect to my SIP Carrier with Voice Elements
When you demo our Voice Elements Platform, it will automatically configure everything so that you are able to make and receive calls using Inventive Labs SIP Service.
While the Inventive Labs SIP Service is a reliable, low-cost option, if you are outside the US, you would be better served to look for alternative SIP carriers, as we are unable to provide reasonable rates for International service.
The two most common forms of authentication for SIP service are IP based authentication and SIP registration. Both forms of authentication are supported by the Voice Elements Platform. Regardless of the type of authentication type that you are using with your carrier, you will need to review the settings below:
The relevant settings you will need to modify in the HmpElementsServer.exe.config are below:
RTP Media IP
RtpMediaIp controls the IP address to use for the Audio (RTP).
<setting name="RtpMediaIp" serializeAs="String"> <value>10.10.1.125</value> </setting>
HmpIp controls what IP address the SIP (Call Control) traffic can be expected to use:
<setting name="HmpIp" serializeAs="String"> <value>10.10.1.125</value> </setting>
Unless, you have a specific reason for doing so, it’s recommended to always use the same IP address for the two settings above.
HmpPort controls which port the SIP (Call Control) traffic can be expected to use. This is most commonly port 5060. Unless you are positive that your SIP carrier expects you to use a different port number, use port 5060:
<setting name="HmpPort" serializeAs="String"> <value>5060</value> </setting>
The Voice Elements Platform has built in NAT capability. What this means is that if you configure your router appropriately, HMP Elements should be able to seamlessly traverse your router and communicate with your SIP carrier.
The ExternalIp setting controls which IP address will show up in the “FROM” section in SIP Packets:
<setting name="ExternalIp" serializeAs="String"> <value>10.10.1.125</value> </setting>
You will need to modify the following settings in your VoiceElementsServer.exe.config to work with your SIP carrier. All of the settings are inside the CTI32NetLib.Properties.Settings Section.
Hmp Default Destination Host
HmpDefaultDestinationHost specifies the default IP address that Voice Elements will send it’s calls to. You should put your carriers’ Border Controller (or any IP address that they have specified to connect to) in this field.
<setting name="HmpDefaultDestinationHost" serializeAs="String"> <value>188.8.131.52</value> </setting>
Hmp Default Source User
HmpDefaultSourceUser specifies the default Caller ID setting used when placing calls. Certain carriers require that this setting be a phone number that they have assigned to you. This setting gets overridden when specifying the OriginatingPhoneNumber from your application:
<setting name="HmpDefaultSourceUser" serializeAs="String"> <value>0000000000</value> </setting>
Hmp Default Source Host
HmpDefaultSourceHost specifies the default source IP address when placing calls. Generally, you should always specify the external IP address of your Voice Elements Server in this field:
<setting name="HmpDefaultSourceHost" serializeAs="String"> <value>192.168.1.145</value> </setting>
Hmp Default Destination Port
HmpDefaultDestinationPort specifies the Port that you will send SIP traffic to. This setting is used in conjunction with the HmpDefaultDestinationHost.
<setting name="HmpDefaultDestinationPort" serializeAs="String"> <value>5060</value> </setting>
Hmp Default Source Port
HmpDefaultSourcePort specifies the default port that you send SIP traffic from. This should match the HmpPort setting from your HmpElementsServer.exe.config setting.
<setting name="HmpDefaultSourcePort" serializeAs="String"> <value>5060</value> </setting> </CTI32NetLib.Properties.Settings>
IP Based Authentication
When using IP based authentication, your carrier will send calls to the IP address and port combination that you have specified.
IP based authentication can be very easy to set up if you have a static IP address, and your carrier supports it. In fact, this is the type of authentication that the Inventive Labs SIP service uses.
When using IP Based Authentication, you will need to specify all of the settings above. It can be useful to perform a wireshark trace to capture traffic between your server and machine if you have any trouble placing, or receiving calls.
In contrast to IP based authentication, SIP Registration relies on Register packets that contain authentication information that is used to validate your server with your carrier. To use SIP Registration, all of the settings above apply. In addition, you should use these settings when setting up the Voice Elements Platform to work with your SIP Carrier.
More questions? Give us a call!
If you would like to schedule a free consultation with a Voice Elements engineer, please send a request to Support.