DID Provisioning Providers
A DID service provider delivers real PSTN numbers for various countries, depending on the availability, and will make sure to route calls to your instance and also allow your instance to make calls
Restcomm and Provisioning Providers
The Restcomm integration with provision providers allows users to search, register and release DIDs as well as make and received calls. For some provision providers it is also possible to send and received SMS via SMS enabled DIDs.
Restcomm is supporting the following DID provisioning providers:
Configuring Restcomm for a certain provider
To configure Restcomm for one of the above providers you have to edit the restcomm.conf file located at $RESTCOMM_HOME/bin/restcomm/restcomm.conf (https://github.com/Mobicents/RestComm/blob/master/release/config-scripts/as7-config-scripts/restcomm/restcomm.conf).
In the restcomm.conf file you will find the following:
# DID Provision provider variable declarations PROVISION_PROVIDER='' # values: VI (VoipInnovation), BW (Bandwidth), NX (Nexmo), VB (Voxbone) #Username and password for all supported DID provision providers DID_LOGIN='' DID_PASSWORD='' # VoipInnovation Endpoint ID DID_ENDPOINT='' #Bandwidth SiteId and AccountId DID_SITEID='' DID_ACCOUNTID=''
Explanation of each property:
- PROVISION_PROVIDER: Choose a value from: VI (VoipInnovation), BW (Bandwidth), NX (Nexmo), VB (Voxbone)
- DID_LOGIN: Username (login) for the DID provision provider
- DID_PASSWORD: Password for the DID provision provider
- DID_ENDPOINT: Used for VoipInnovation only for the Endpoint ID
- DID_SITEID: Used for Bandwidth as the Site Id
- DID_ACCOUNTID: Used for Bandwidth as Account Id
According to the above values, the restcomm.xml (https://github.com/Mobicents/RestComm/blob/master/restcomm/restcomm.application/src/main/webapp/WEB-INF/conf/restcomm.xml) will be configured as follows:
<phone-number-provisioning class="org.mobicents.servlet.restcomm.provisioning.number.vi.VoIPInnovationsNumberProvisioningManager"> <callback-urls> <voice url="" method="" /> <sms url="" method="" /> <fax url="" method="" /> <ussd url="" method="" /> </callback-urls> <voip-innovations> <login></login> <password></password> <endpoint></endpoint> <uri>https://backoffice.voipinnovations.com/api2.pl</uri> </voip-innovations> <bandwidth> <username></username> <password></password> <accountId></accountId> <siteId></siteId> <uri>https://api.inetwork.com/v1.0</uri> </bandwidth> <nexmo> <api-key></api-key> <api-secret></api-secret> <uri>https://rest.nexmo.com/</uri> </nexmo> <voxbone> <username></username> <password></password> <uri>https://api.voxbone.com/ws-voxbone/services/rest</uri> </voxbone> </phone-number-provisioning>
SMS
For SMS (if the provider supports SMS messages), auto-config scripts will properly configure Restcomm to the provider outbound proxy.
For SMS (if the provider supports SMS messages), auto-config scripts will properly configure Restcomm to the provider outbound proxy.
Termination (incoming calls)
For Termination (incoming calls) there is nothing needed from Restcomm side. Network/firewall setup is needed to allow traffic from each provider.
Origination (outbound calls)
For Origination (outbound calls) outbound proxy you will need to do the following settings in restcomm.conf:
For Origination (outbound calls) outbound proxy you will need to do the following settings in restcomm.conf:
For Nexmo:
# Address for outbound calls OUTBOUND_PROXY='sip.nexmo.com' OUTBOUND_PROXY_USERNAME='NEXMO_USERNAME' OUTBOUND_PROXY_PASSWORD='NEXMO_PASSWORD'
For VoipInnovations:
# Address for outbound calls OUTBOUND_PROXY='64.136.174.30' OUTBOUND_PROXY_USERNAME='' OUTBOUND_PROXY_PASSWORD=''
For Bandwidth:
# Address for outbound calls OUTBOUND_PROXY='ot.bandwidth.com' OUTBOUND_PROXY_USERNAME='' OUTBOUND_PROXY_PASSWORD=''
The post Restcomm – DID provisioning provider configuration appeared first on Telestax Docs Online.