Polycom 3725-70003-009F Manual De Usuario
![Polycom](https://files.manualsbrain.com/attachments/767eaf955c8cc2b9ce09b520a479458e9ecc719d/common/fit/150/50/d6cfa10805a345f10c5d76edb36fa9cec42388252dcc309ffa6582d04677/brand_logo.png)
ReadiVoice Administration & Maintenance Guide
272
Proprietary & Confidential
Password Included
—
One-Password Call Flow
ReadiVoice-IP has three possible IP tributaries for one-password call flows.
Clear Text Password
In this type of SIP INVITE, the TO header includes the access code and
password. It has the following format:
TO: sip:accessnumber@host;AC=accesscode;PCODE=password
When the header has this format, the caller enters the traditional ReadiVoice
call flow after the password prompt (rather than being prompted for an access
code and password). If the password within the header is invalid, the system
sends a 401 Unauthorized response to the INVITE.
PCODE="" is valid if the participant password field in the database is empty.
call flow after the password prompt (rather than being prompted for an access
code and password). If the password within the header is invalid, the system
sends a 401 Unauthorized response to the INVITE.
PCODE="" is 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 access code and
verification of authorization. It has the following format:
TO: sip:accessnumber@host;AC=accesscode;AUTH=TRUE
When the header has this format and the SIP protocol authorization is valid,
the caller enters the traditional ReadiVoice call flow after the password
prompt (rather than being prompted for an access code and password). If the
authorization within the header is invalid, the system sends a 401
the caller enters the traditional ReadiVoice call flow after the password
prompt (rather than being prompted for an access code and password). If the
authorization within the header is invalid, the system sends a 401
Unauthorized response to the INVITE.
Trusted Proxy
In this type of SIP INVITE, the TO header includes the access code and
participant type. It has one of the following formats:
TO: sip:accessnumber@host;AC=acccesscode;PTYPE=SUBSCRIBER
or
TO: sip:accessnumber@host;AC=acccesscode;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 an access code and
password). If the proxy is not a trusted proxy, the system sends a 401
trusted proxy, the caller enters the traditional ReadiVoice call flow after the
password prompt (rather than being prompted for an access code and
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.
system sends a 400 Bad Request response to the INVITE.
Password Included
—
Two-Password Call Flow
ReadiVoice-IP has three possible IP tributaries for two-password call flows.
Clear Text Password
In this type of SIP INVITE, the TO header includes the password, but the access
code is not included or is empty. It has one of the following formats:
TO: sip:accessnumber@host;AC="";PCODE=password