Table 19.1 (continued)
URI IDENTITY EXAMPLE SCHEME 1
EXAMPLE SCHEME 2
EXAMPLE SCHEME 3
Retrieve - SIP authentication sip:[email protected]
sip:[email protected]
sip:[email protected];mode=inpin
Retrieve - prompt for PIN sip:sub-rjs-retrieve-inpin.vm.mci.com
in-band sip:6 7741 [email protected]
sip:[email protected];mode=inpin
Deposit - identitfy target sip:[email protected]
mailbox by To: sip:[email protected]
sip:[email protected]
Retrieve - identify target sip:[email protected]
mailbox by SIP authentication sip:[email protected]
sip:[email protected]
Deposit - prompt for target sip:[email protected]
mailbox inband sip:[email protected]
sip:[email protected];mode=inband
Retrieve - prompt for target sip:[email protected]
mailbox and PIN in-band sip:[email protected]
sip:[email protected];mode=inbandUsing this design approach, very complex component service systems can
be designed by just designing the SIP URI schema in the system.
Another URI parameter of interest is the causefor redirecting the call [7].
The causeparameters are shown in Table 19.2.
Table 19.2 Cause Values for Redirecting the Call
REDIRECTING REASON VALUE
Unknown/Unavailable 404
User Busy 486
No Reply 408
Unconditional 302
Deflection during Alerting 487
Deflection immediate response 480
Mobile subscriber not reachable 503SIP Component Services 327