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 |
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 |
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, Anonymous will flag as withheld CLI |
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. The order of entries matters - the previous Chargeable-User-Identity and Calling-Station-Id are used on Called-Station-Id routes, so you can interleave them if they need to be differnt for each route. Typically they will not, and you set CLI and CUI once at the start of the packet.
There are a number of formats for call routing (Called-Station-Id) which can be used:-
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.