G.2. Authentication response

G.2. Authentication response
	Appendix G. Supported RADIUS Attribute/Value Pairs for VoIP operation

G.2.1. Challenge authentication

Table G.2. Access-Challenge

A challenge response allows the authentication details to be specified. By default this is not required as the FB2500 will generate a challenge.

AVP	No.	Usage
Digest-Realm	104	Digest Realm
Digest-Nonce	105	Digest Nonce
Digest-QOP	110	Digest QOP
Digest-Algorithm	111	Digest Algorithm
Digest-Opaque	116	Digest Opaque

G.2.2. Accepted authentication (registration)

Table G.3. Access-Accept

AVP	No.	Usage
Calling-Station-Id	31	Calling number to be set up for tel:number routing to this registration

G.2.3. Accepted authentication (invite)

Note that this section is not yet complete

Table G.4. Access-Accept

AVP	No.	Usage
Chargeable-User-Identity	89	Identity to be used on accounting records
Calling-Station-Id	31	Overrides CLI to use on this call
Called-Station-Id	30	URI for destination, may appear multiple times

The Called-Station-Id is used to say where to send the call. If none are specified then a default call routing logic is used. Multiple entries can be sent, and all are called. There are a number of formats which can be used:-

tel:number - send to registered addresses for the number.
sip:uri - send to SIP destination.
@carriername - send to named carrier.
number@carriername - send to named carrier using specific target number.

The above formats can be prefixed with digits and a plus to indicate a delay of a number of seconds before the destination is to be called. This allows a cascade ring pattern.

G.2.4. Rejected authentication

Table G.5. Access-Reject

AVP	No.	Usage
Reply-Message	18	Reply message sent in SIP response

The reply message is included in a Warning heading.


Appendix G. Supported RADIUS Attribute/Value Pairs for VoIP operation		G.3. Accounting Start