Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Mapping extensiosn&DID Communication manager
- Thread starter Najib.bk
- Start date
ZeroZeroOne
Vendor
Personally, I would leave the mapping in Session Manager if you already have SIP trunks but yes, you can use the incoming call handling tables.
This entry would take any 10-digit dial string starting with "781555" and remove the first 6 digits, leaving just a 4-digit extension. This is great if your DIDs match up directly with your extensions and is typical on PRI circuits.
On SIP trunks from Session Manager you may see the service type as "tie":
Again, a "generic" rule would convert 10-digit to 4-digit. If your DIDs don't match the extensions then you will have to manually match them, as in lines 2-4.
If the carrier is only sending 4-digits then you can match that, too.
Keep in mind that you will need dial patterns and routing policies in Session Manager to send everything to CM.
Code:
display inc-call-handling-trmt trunk-group 1 Page 1 of 30
INCOMING CALL HANDLING TREATMENT
Service/ Number Number Del Insert Per Call Night
Feature Len Digits CPN/BN Serv
public-ntwrk 10 781555 6This entry would take any 10-digit dial string starting with "781555" and remove the first 6 digits, leaving just a 4-digit extension. This is great if your DIDs match up directly with your extensions and is typical on PRI circuits.
On SIP trunks from Session Manager you may see the service type as "tie":
Code:
display inc-call-handling-trmt trunk-group 1 Page 1 of 30
INCOMING CALL HANDLING TREATMENT
Service/ Number Number Del Insert Per Call Night
Feature Len Digits CPN/BN Serv
tie 10 781555 6
tie 10 7815551234 6 7345
tie 10 7815551255 6 8302
tie 4 2111 4 8303Again, a "generic" rule would convert 10-digit to 4-digit. If your DIDs don't match the extensions then you will have to manually match them, as in lines 2-4.
If the carrier is only sending 4-digits then you can match that, too.
Keep in mind that you will need dial patterns and routing policies in Session Manager to send everything to CM.
- Thread starter
- #3
HI mate
Thank you
Sorry I forgot to mention that I have an E1-R2 line so the call flow will be as follow SM>CM>MG430>Far-end Service provider.
Because I have an E1-R2 line, I am unable to configure the adaptation on session manager as well as the incoming call handling tables.
Thank you
Sorry I forgot to mention that I have an E1-R2 line so the call flow will be as follow SM>CM>MG430>Far-end Service provider.
Because I have an E1-R2 line, I am unable to configure the adaptation on session manager as well as the incoming call handling tables.
ZeroZeroOne
Vendor
Oh... E1 R2.... So incoming call handling isn't even an option, right?
You can try either the ARS digit conversion or AAR digit conversion tables.
Display Feature Access Codes, and look on the first page for these entries:
Either will work but you must pick one: AAR or ARS. I'll demonstrate ARS but the steps are pretty much the same.
First, How many digits is the carrier sending you? Let's assume 7 digits, and you want to match these to 4-digit extensions.
Second, Pick a dial string that doesn't interfere with anything else. We will use this to force the incoming dial string into the ARS Digit Conversion Table. I'll use "77".
This will make our new dial string 9-digits (2-digits for "77" plus the 7-digits from the carrier.
Third, Make entries in the ARS digit-conversion table, matching your new leading digits (77).
This should strip off our "77" plus 3 additional digits to leave us with a 4-digit extension. Now, I'm assuming your DID numbers match directly to your internal extension (345-1234 = ext. 1234) but you may have to use the Replacement String to make a manual match.
Fourth, on the Trunk Group form page 2 there should be an entry for Inserting Digits. You may need to specify the Digit Treatment, depending on how your trunk is set up.
For the inserted digits, enter the ARS Access Code and the new routing digits "77":
Now, what should happen is when the carrier sends you 7-digits, the trunk inserts "077". PBX sees "0" and starts processing the dial string as ARS. The ARS Digit Conversion strips 5 digits ("77" and the first 3 of the original dial string) to leave a 4-digit extension.
That's assuming I have everything right. No guarantees on that.
You can try either the ARS digit conversion or AAR digit conversion tables.
Display Feature Access Codes, and look on the first page for these entries:
Code:
Auto Alternate Routing (AAR) Access Code: [COLOR=#EF2929]*099[/color]
Auto Route Selection (ARS) - Access Code 1: [COLOR=#EF2929]0[/color] Access Code 2:Either will work but you must pick one: AAR or ARS. I'll demonstrate ARS but the steps are pretty much the same.
First, How many digits is the carrier sending you? Let's assume 7 digits, and you want to match these to 4-digit extensions.
Second, Pick a dial string that doesn't interfere with anything else. We will use this to force the incoming dial string into the ARS Digit Conversion Table. I'll use "77".
This will make our new dial string 9-digits (2-digits for "77" plus the 7-digits from the carrier.
Third, Make entries in the ARS digit-conversion table, matching your new leading digits (77).
Code:
change ars digit-conversion 0 Page 1 of 2
ARS DIGIT CONVERSION TABLE
Location: all Percent Full: 3
Matching Pattern Min Max Del Replacement String Net Conv ANI Req
[COLOR=#EF2929]77 9 9 5 ext[/color] n nThis should strip off our "77" plus 3 additional digits to leave us with a 4-digit extension. Now, I'm assuming your DID numbers match directly to your internal extension (345-1234 = ext. 1234) but you may have to use the Replacement String to make a manual match.
Fourth, on the Trunk Group form page 2 there should be an entry for Inserting Digits. You may need to specify the Digit Treatment, depending on how your trunk is set up.
For the inserted digits, enter the ARS Access Code and the new routing digits "77":
Code:
TRUNK PARAMETERS
Outgoing Dial Type: tone Incoming Dial Type: tone
Trunk Termination: rc
[COLOR=#EF2929]Digit Treatment: insertion Digits: 077[/color]
Expected Digits: Sig Bit Inversion: noneNow, what should happen is when the carrier sends you 7-digits, the trunk inserts "077". PBX sees "0" and starts processing the dial string as ARS. The ARS Digit Conversion strips 5 digits ("77" and the first 3 of the original dial string) to leave a 4-digit extension.
That's assuming I have everything right. No guarantees on that.
- Thread starter
- #5
Thank you very much, ZeroZeroOne, for this suggestion and the detailed explanations on how to route the incoming call to the appropriate destinations.
I'll share the trick that I found to do this stuff with you .
For incoming calls, I set the "DIGIT TREATMENT" to APSOTBTION in the trunk configuration, with "digits" set to 3 and I use the rest as virtual extensions (VDN or Hunt group), and then redirect to the appropriate internal extension
For outgoing calls, I created a plan of extensions that began with the last five digits of the SDAs I had and ended with a four-digit prefix on the class of restriction "MF ANI PREFIX" ,resulting in the entire correct sda on the "SEND ANI".
I'll share the trick that I found to do this stuff with you .
For incoming calls, I set the "DIGIT TREATMENT" to APSOTBTION in the trunk configuration, with "digits" set to 3 and I use the rest as virtual extensions (VDN or Hunt group), and then redirect to the appropriate internal extension
For outgoing calls, I created a plan of extensions that began with the last five digits of the SDAs I had and ended with a four-digit prefix on the class of restriction "MF ANI PREFIX" ,resulting in the entire correct sda on the "SEND ANI".
- Status
Similar threads
- Question