Chapter 3 CS 1000 considerations 41Survivable Remote Gateway 50 Configuration Guide5 Add a destination code.a Access the Dialing Plan - Routing panel (Configuration > Telephony > Dialing Plan >Routing) and select the Destination Codes tab.b Add a new destination code.Use the ALTPrefix as the destination code.c On the ALTPrefix Destination Code row, select the Normal Route field.d Enter the route for the Attendant telephone (997).e In the adjacent Absorbed Length field, select All from the pull-down menu.When the SRG receives the ALTPrefix+DN digits from the main office, it looks up the destinationcode table, finds a match for the ALTPrefix, dumps all the digits (ALTPrefix+DN), and dials themain office Attendant.To configure Alternative Call Routing on the SRG50; with DIDtrunks1 Complete the procedure: To configure the SRG50 for NBWM and ADBWM (“To configurethe SRG50 for NBWM and ADBWM” on page 39).2 Refer to “Call routing: configuring for outgoing calls” on page 86 and the BCM50 NetworkingConfiguration Guide (N0027156) for more information on the logic behind this procedure.3 Obtain the ALTPrefix for the SRG50 (configured at the main office).4 Define a route for the NPA-NXXX portion of the main office DID numbers.a Access the Dialing Plan - Routing panel (Configuration > Telephony > Dialing Plan >Routing) and select the Routes tab.b Add a new route (for example, 996).c Ensure that the DN Type is Public (Unknown).d In the External Number field, enter the NPA-NXXX of the DID trunks that serve themain office.e Assign the PSTN line pool to the route (select the line pool from the Use Pool pull-downmenu; default is A).Note: In order to support DID trunks, the MODN dialed by an SRG50caller must match the DID digits.Note: In the following procedure, it is assumed that the MODN matchesthe XXXX portion of the DID’s NPA-NXX-XXXX; and that theALTPrefix is 3 digits.
