Dialogic 6.2 - Manual (Page 221)

Managing Calls Using IP Telephony
November 2009 221
The following are valid dial string examples for a SIP channel.
Comments are shown in italics.
sip:Joe Smith<[email protected]> SIP endpoint address.
sip:[email protected] Endpoint gateway specified.
sip:[email protected] Proxy explicitly specified.
Joe Smith<[email protected]> SIP endpoint address.
[email protected] Endpoint gateway specified.
[email protected] Proxy explicitly specified.
800-555-1212 Will use default proxy server.
+1 (800) 555-1212 Will use default proxy server.
192.168.1.45 Valid, but not recommended.
[email protected] Valid, but not recommended.
sip:somewhere.com User part (left side of ‘@') is implied.
sip:[email protected]:9876 An explicit port specification.
sip:[email protected];user=phone Specifies that user part is a phone number.
Using prefixed dial strings would have the same effect, as in:
fax –u 0 –s sip/t38://[email protected] foo.pkt
Using an alternative URI scheme:
fax -u 0 -s [email protected] foo.pkt
¾ initiates the following sequence of events:
1. Call Control processes the URI dial string, sends it to the SIP
protocol stack.
2. SIP stack places the SIP call to the Cisco XXXX Gateway.
3. The Cisco Gateway places the call on the PSTN, sending call
progress information to the SIP stack and then finally connecting
the call.
4. The fax is then sent and the call is torn down.
No SIP proxy or redirect server is required if not configured or
needed for point to point calls.
Again, using prefixed dial strings would have the same effect as in:
fax -u 0 -s sip://[email protected]
foo.pkt