Destination – Various Ways to Reach Out To the World of Devices!

The complete magic of TringMe’s platform is to unify various forms of communication over varying devices. These are all categorized as destinations and are accepted in APIs which take destination as a parameter. Let’s look at all the types of destination that are supported and format in which it needs to be specified in API:

Destination parameters

The destination can be specified for call and channel as provided below.

Parameters
Destination Type API Destination Format
Phone (worldwide mobile or landline) Valid phone number (prefixed with country code. For e.g. to call US, the phone number should start with a ‘1’ (as in 18585551212 to call a number in San-Diego, US)
SIP
  • sip:<sip uri> , for example, sip:identity@mysipserver.com
  • sip:username:password@mysipserver.com
  • sip:<number>@<sip-id>- to call a <number> using a SIP server that was added using ‘setsipserver’ API
VoicePHP voicephp:<script url>
Note:Depending on the extension of the script, it will be either downloaded once or every time.
For example:The Y co-ordinate where the flash widget should be aligned when it needs to ask for security settings. If null passed, the widget will appear in the top corner of the document.
  • a. voicephp:http://myserver.com/script.voicephp – In this case, script will be always downloaded before the execution of VoicePHP application.
  • b. voicephp:http://myserver.com/script.txt – In this case, the script will be downloaded only once.
Conference
  • conf:<conf-id>:flag
  • a. <conf-id> is returned by ‘createconference’ API.
  • b. Flag is combination of one or more of following:
  • 0 – Ask for PIN
  • 0x1 – Use User PIN
  • 0x10 – Listen Only
  • 0x20 – Quiet Mode
Gtalk gtalk: user@gmail.com
Voicemail voicemail
Mobile VoIP mobilevoip

If you are an enterprise and would like to know better how TringMe can help you reduce cost and at the same time benefit you,
please send a mail to bizdev@tringme.com