Outbound calls on VoIP lines

When placing an outgoing call the IP address or domain of the destination or Switch/PBX or VoIP Provider relaying the call needs to be specified.

For example, when dialing another extension on the VoIP Switch/PBX the number dialed would be of the format: extension@ip_address_of_voip_switch

eg:

2043@10.1.1.11

According to how the VoIP switch is set up, the "extension" could also be an external phone number.

when dialing another number through a VoIP provider, the VoIP providers SIP server domain/address needs to be specified: telnumber@sipprovider

eg:

15551231234@callcentric.com

 

When making an outgoing call on a VoIP line it is usually necessary to specify the CallerID to be used on the outgoing call. This advises the switch relaying the VoIP call as to which account/subscriber is making the call. The CallerID on outgoing calls can be specified using the <CallerID> tag on the Options field when loading the outgoing call, and is in this format: <CallerID>accountnumber@voipprovider</CallerID>

 

For example, to place a call through a FreeSWITCH PBX which is installed on a server with IP of 10.1.1.11, and with which the user/extension 1010 has been registered by VoiceGuide, the following entry would need to be placed in the Options field:

<CallerID>1010@10.1.1.11</CallerID>

Sometimes just user ID (or the registered telephone number) is sufficient, eg:

<CallerID>5625551234</CallerID>

 

And to place a call through a VoIP provider with which the account was registered by VoiceGuide, an entry that includes the domain name of the provider may need to be used. For example, with CallCentric, this may need to be used:

<CallerID>12345678@callcentric.com</CallerID>

 

Also, on outbound calls the VoIP Switch will often require to authenticate the user before allowing the outbound call to be made. To allow HMP to process the authentication request it is necessary to specify the VoIP Line registration and authentication parameters. Please see the VoIP Line Registraton section.
In particular, the entry in the section may need to be set to allow HMP to authenticate outgoing calls correctly.

 

If specific headers need to be added/modified in the outgoing SIP INVITE packet then these can also be specified in the Call Options field when loading the outgoing call. To add a SIP header a "<sip-header>" entry needs to be specified in the Call Options field.
eg: to add a "Remote-Part-ID" header, this entry could be added to the Call Options field:

<sip-header>Remote-Part-ID: "Flowroute" <sip:1234567890@sip.flowroute.com>

"sip-session-expires" and "sip-min-se" entries can also be specified, like this:

<sip-session-expires>999</sip-session-expires>
<sip-min-se>55</sip-min-se>

(or these could be just added using the "<sip-header>" approach)

 

Multiple headers can be specified. Below is a valid Call Options entry:

<CallerID>12121212</CallerID>
<sip-session-expires>999</sip-session-expires>
<sip-min-se>55</sip-min-se>
<sip-header>Remote-Part-ID: "Flowroute" <sip:123412341234@sip.flowroute.com;party=calling;screen=yes;privacy=on</sip-header>
<sip-header>X-Tag: mySpecialCallTag123</sip-header>
<sip-header>Diversion: <sip:333344445555@sip.mycarrier.com>

 

The WireShark protocol analyzer can be used to capture the traces of the actual SIP messages sent.