ReadiVoice-IP with IP Tributaries
Proprietary & Confidential 273
or
TO: sip:accessnumber@host;PCODE=password
When the header has one of these formats, the caller enters the traditional
ReadiVoice call flow after the password prompt (rather than being prompted
for a password). If the password within the header is invalid, the system sends
a
401 Unauthorized
response to the
INVITE
.
PCODE=""
is also valid if the participant password field in the database is
empty.
Per Call Authorization
In this type of SIP
INVITE
, the
TO
header includes the verification of
authorization, but the access code is not included or is empty. It has one of the
following formats:
TO: sip:accessnumber@host;AC
=""
;AUTH=TRUE
or
TO: sip:accessnumber@host;AUTH=TRUE
When the header has one of these formats, the caller enters the traditional
ReadiVoice call flow after the password prompt (rather than being prompted
for a password). If the authorization within the header is invalid, the system
sends a
401 Unauthorized
response to the
INVITE
.
Trus ted P roxy
In th is t ype of S IP I NVI TE, the TO hea der includes the participant type, but the
access code is not included or is empty. It has one of the following formats:
TO: sip:accessnumber@host;AC=
""
;PTYPE=SUBSCRIBER
or
TO: sip:accessnumber@host;AC=
""
;PTYPE=PARTICIPANT
or
TO: sip:accessnumber@host;PTYPE=SUBSCRIBER
or
TO: sip:accessnumber@host;PTYPE=PARTICIPANT
When the header has one of these formats and the INVITE comes from a
trusted proxy, the caller enters the traditional ReadiVoice call flow after the
password prompt (rather than being prompted for a password). If the proxy is
not a trusted proxy, the system sends a
401 Unauthorized
response to the
INVITE. If the
PTYPE
specified is not valid, the system sends a
400 Bad
Request
response to the INVITE.