CHAPTER20 SIP Definitions
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Description
'Request Key'
request-key
[CallSetupRules_
AttributesToQuery]
Defines the key to query.
â– For LDAP, the key string is queried on the LDAP server.
â– For Dial Plans, the key string is searched for in the specified Dial
Plan.
â– For ENUM, the key string is queried on the ENUM server.
â– For HTTP GET and HTTP POST queries, the key string is queried
on the HTTP server.
The valid value is a string of up to 100 characters. Combined strings
and values can be configured like in the Message Manipulations table,
using the '+' operator. Single quotes (') can be used for specifying a
constant string (e.g., '12345').
You can use the built-in syntax editor to help you configure the field.
Click the Editor button located alongside the field to open the Editor,
and then simply follow the on-screen instructions.
Examples:
â– To LDAP query the AD attribute "mobile" that has the value of the
destination user part of the incoming call:
'mobile=' + param.call.dst.user
â– To LDAP query the AD attribute "telephoneNumber" that has a
redirect number:
'telephoneNumber=' + param.call.redirect + '*'
â– To query a Dial Plan for the source number:
param.call.src.user
â– To query an ENUM server for the URI of the called (destination)
number:
param.call.dst.user
â– To send an HTTP POST to notify the HTTP server of call
connection status:
'connectionStatus'
Note: The parameter is applicable only if the 'Request Type' parameter
is configured to any value other than None.
'Attributes To Get'
attr-to-get
[CallSetupRules_
AttributesToGet]
Defines the Attributes of the queried LDAP record that the device must
handle (e.g., retrieve value).
The valid value is a string of up to 100 characters. Up to five attributes
can be defined, each separated by a comma (e.g., msRTCSIP-
PrivateLine,msRTCSIP-Line,mobile).
Note:
â– The parameter is applicable only if you configure the 'Request
Type' parameter to LDAP.
- 486 -