User's Manual
214
Document #: LTRT-89729
Mediant 3000
•
LDAP query is successful but call fails (due to, for example, busy line) to all the
relevant attribute destinations (private, Lync, PBX, and mobile), and a relevant
Tel-to-IP Release Reason (see Alternative Routing for Tel-to-IP Calls on page
) or SBC Alternative Routing Reason (see Configuring Alternative Routing
Reasons on page
) has been configured.
Once the device receives the original incoming call, the first rule that it uses is Rule 6,
which queries the AD server. When the AD replies, the device searches the table, from the
first rule down, for the matching destination phone prefix (i.e., "PRIVATE:, "PBX:", "OCS:",
"MOBILE:", and "LDAP_ERR:"), and then sends the call to the appropriate destination.
14.1.3.3 Querying the AD for Calling Name
The device can be configured to retrieve the calling name (display name) from Microsoft
Active Directory (AD) for Tel-to-IP calls that are received without a calling name. The
device queries the AD, based on the Calling Number search key and searches for the
calling name attribute configured by the parameter, MSLDAPDisplayNameAttrName (e.g.,
“displayName”). The device uses the resultant calling name as the display name in the SIP
From header of the sent INVITE message.
To configure this feature, the following keywords are used in the Calling Name
Manipulation Table for Tel -> IP Calls table for the 'Prefix/Suffix to Add' fields, which can be
combined with other characters:
"$LDAP-PBX": starts LDAP query using the MSLDAPPBXAttrName parameter as the
search key
"$LDAP-MOBILE": starts LDAP query using MSLDAPMobileAttrName parameter as
the search key
If the source (calling) number of the Tel-to-IP call matches the PBX / MOBILE (e.g.,
"telephoneNumber" and "mobile") number in the AD server, the device uses the resultant
Display Name instead of the keyword(s).
For example, assume the following configuration in the Calling Name Manipulation Table
for Tel -> IP Calls:
'Source Prefix' field is set to "4".
'Prefix to Add' field is set to "$LDAP-PBX Office".
If the calling number is 4046 and the resultant LDAP query display name is "John Doe", the
device sends the INVITE message with the following From header:
From: John Doe <sip:[email protected]>\
Notes:
•
The Calling Name Manipulation Table for Tel -> IP Calls table uses the
numbers before manipulation, as inputs.
•
The LDAP query uses the calling number after source number
manipulation, as the search key value.
Summary of Contents for Mediant 3000
Page 2: ......
Page 26: ...User s Manual 26 Document LTRT 89729 Mediant 3000 Reader s Note...
Page 27: ...Part I Getting Started with Initial Connectivity...
Page 28: ......
Page 40: ...User s Manual 40 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 41: ...Part II Management Tools...
Page 42: ......
Page 44: ...User s Manual 44 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 80: ...User s Manual 80 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 98: ...User s Manual 98 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 103: ...Part III General System Settings...
Page 104: ......
Page 113: ...Part IV General VoIP Configuration...
Page 114: ......
Page 144: ...User s Manual 144 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 164: ...User s Manual 164 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 222: ...User s Manual 222 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 224: ...User s Manual 224 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 275: ...Part V Gateway and IP to IP Application...
Page 276: ......
Page 278: ...User s Manual 278 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 399: ...Part VI Session Border Controller Application...
Page 400: ......
Page 402: ...User s Manual 402 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 464: ...User s Manual 464 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 465: ...Part VII Stand Alone Survivability Application...
Page 466: ......
Page 474: ...User s Manual 474 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 494: ...User s Manual 494 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 497: ...Part VIII IP Media Capabilities...
Page 498: ......
Page 501: ...Part IX High Availability System...
Page 502: ......
Page 515: ...Part X Maintenance...
Page 516: ......
Page 522: ...User s Manual 522 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 524: ...User s Manual 524 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 552: ...User s Manual 552 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 562: ...User s Manual 562 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 565: ...Part XI Status Performance Monitoring and Reporting...
Page 566: ......
Page 578: ...User s Manual 578 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 609: ...Part XII Diagnostics...
Page 610: ......
Page 624: ...User s Manual 624 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 626: ...User s Manual 626 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 638: ...User s Manual 638 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 639: ...Part XIII Appendix...
Page 640: ......
Page 864: ...User s Manual 864 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 871: ...Version 6 6 871 Mediant 3000 User s Manual 55 Selected Technical Specifications Reader s Notes...