AT&T BCM50 manual Appendix a Configuring Destination Code with Wildcard

Page 36

AT&T IP Flexible Reach Service

Nortel BCM50 Release 3.0 SIP Configuration Guide

6APPENDIX A: Configuring Destination Code with Wildcard

In an inbound call scenario, the leading digit sent to the BCM50 may be the same as the digit used in the destination code. Without configuring for a wildcard; the BCM50 will interpret the call as a tandem call, and will fail to terminate the call on the BCM50. To remedy this, it is recommended to configure destination code with wildcard.

If the IP Flexible Reach sends a site prefix that is the same as the digit being used for the destination code; please use the following configuration example.

In this example, the number sent to the BCM50 is the following: “961170”. To configure the BCM50 for this call, use the following wildcard configuration.

Under Configuration Æ Telephony Æ Dialing Plan Æ Routing, under the Destination Codes tab, add the destination code “9A” to use Normal Route “001.” Configure the absorbed length to 1 so that the BCM50 will absorb the ‘9’ only in an outbound call scenario. Uncheck the digit following the ‘9’ in the incoming digits to the BCM50 (in this example, the ‘6’ in “961170”).

Figure 30: Configuring Destination Code with Wildcard

© 2007 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks contained herein are the property of their respective owners.

Issue 0.7

Page 36 of 37

Image 36
Contents AT&T Voip Table of Contents Table of Figures Introduction Customer QuestionsTrouble Reporting Document Feedback Document Change HistoryIssue Emergency 911/E911 Services Limitations Special NotesCalling Number Restricted / Private not supported BCM Soft Phones not currently supportedOverview PSTIssue Pstn Configuration Guide Nortel BCM50 Version and Feature RequirementsBCM50 Lists of Applied Patches IP Trunks Available VoIP Trunks Assigning Line Pool to IP Trunks Issue Configuring General DN Length Configuring Private Received Number Length Assigning a Route for IP Trunks Assign Code to Access IP Trunk Routes SIP Proxy Parameters Failover to Secondary AT&T IP Border Element IpbeOutbound Proxy Table for failover to secondary AT&T IPBEs Media Parameters Payload SizeConfiguring analog DNs for fax Port Ranges Media Gateway Port RangesConfiguring Outgoing Calls from BCM50 to AT&T IP Flex Reach ConfigurationÆ TelephonyÆ Sets Æ All DNsConfiguring Incoming Calls from AT&T IP Flex Reach to BCM50 Configuring did for Incoming CallsConfigurationÆ TelephonyÆ Lines Æ Target Lines Assign Line Pool to IP Sets Troubleshooting System Monitoring with BCM MonitorIP Device Listing RTP Session Information System Resources Real-time display of BCM50 Alarms AdministrationÆ General ÆAlarmsLog Management Log ManagementAppendix a Configuring Destination Code with Wildcard Configuring Destination Code with WildcardEnd of Document