CM 8.0 routing question
2

Question

CM 8.0 routing question

bignose21 (Programmer)

(OP)

22 Nov 18 11:23

Hi,
New to the CM and just deployed a Version 8.0, we are planning to use this to host Survivable sites globally and as such are thinking about the issues to come in the dialplan. We already know that we have sites the have extensions starting 1-9 and use 0 for outside line and to take the worst clash sites that use 9 for outside line and extensions starting with 0. As you seem to need to declare everything in the Dialplan in CM how do you take care of this?

so far figure on 3 digit prefixes for locations so that takes away any extension clash but how do you get around defining 0 as an ARS code for one site whereas needing to 4 digit dial extensions starting with 0 on another.

If this was CS1K we would use numberzones which basically prefixes everything with the location prefix so 9 is 2009 and 0 is 2000 for example if location prefix is 200. Because of that it is quite easy to pick out dialed digits as they are all unique to each site. Is the same thing possible with CM and if so a bit of a guide how to do it bearing in mind I am a noob on CM.

kyle555 (TechnicalUser) · Answer 1 · 2018-11-22 14:26:07

You can do location prefixes within the location table.
You can use location location-based calltype analysis - change calltype analysis location 1 or 2 or 3

Something like this would take anyone in location 1 dialing 0123 and make it go to the extension table as 50123.

You can also have 2 ARS access codes - like 9 and 0. Not sure without cracking open docs if calltype analysis pre-empts the feature invocation - like, does 0123 hit calltype first or pick ARS as an access code. i'd think the former otherwise it wouldn't be terribly useful

CODE -->

change calltype analysis location 1                             Page   1 of   4
                         CALL TYPE DIGIT ANALYSIS TABLE
                                  Location: 1

     Dialed String         Delete Insert       Type     Delete Insert       Type
Match: 0                1: 0      5            ext   2:
 Length: Min 4  Max 4   3:                           4:

bignose21 (Programmer) · Answer 2 · 2018-11-23 20:41:04

Thanks I will give it a go next time I get back to the system, install is done waiting for the cutover date

bignose21 (Programmer) · Answer 3 · 2019-03-01 09:42:27

been a while but only just got around to looking at this again, and couldn't get it going an example would be say all sites will have 3 digit location prefix and a DN length of 4

Location 1
prefix 200
dials 0 for ARS
Extensions 9xxx

Location 2
Prefix 201
dials 9 for ARS
Extensions 0xxx

So if you put 0 & 9 in as FAC for ARS in the Dialplan and try in CALLTYPE to say recognize 9, insert 200 and change it to type EXT the call still followed ARS.

So thought i would try it the other way around and declare 9 as a 4 digit extension in dialplan, then in Location 2 Calltype recognise 9 and change it to ARS, in part this works and goes to ARS but only passes first 4 digits.

If you dont declare 9 in the dialplan and just add it to calltype it doesn't work.

the problem we have is trying to replace a Avaya CS1K with CM the CS1K can do this easily its Zone based routing takes care of this seamlessly but to stay in support going forward we are moving over to Red.

bignose21 (Programmer) · Answer 4 · 2019-03-01 09:55:54

guessing instead if i link 9 with AAR then in AAR for Location 1 add the 200 and change to type EXT. For Location 2 send everything across to ARS from AAR. Only downside I guess is Location 1 would get dial tone between first and second digit of extensions.

jimbojimbo (Vendor) · Answer 5 · 2019-03-01 16:55:05

For global customers I typically recommend multiple CM cores (NAR/LATAM, EMEA, APAC). While it is possible to support a global footprint on one CM, latency often becomes an issue. Also simplifies dial plan. Use E.164 at the SM and you route 1,5 to NAR/LATAM, 2,3,4 to EMEA, 6,7,8 to APAC. 9 can go either to EMEA or APAC depending on where you want to put India and the Middle Eastern countries.

bignose21 (Programmer) · Answer 6 · 2019-03-01 17:07:47

We are planning to put a core in America and one in Asia but my issue at the moment is sites in say NL use 0 for outside dialling and have 9xxx extensions, sites in UK dial 9 for off net and have extensions starting 0xxx

bignose21 (Programmer) · Answer 7 · 2019-03-09 20:43:00

Not sure its ideal but certainly works if you add 0 & 9 in Dialplan Analysis as FAC then assign 0 to ARS and 9 to AAR:

Location 1
prefix 200
dials 0 for ARS (just works)
Extensions 9xxx (change AAR digit-conversion Location 1 0 - add 10 entries 0 to 9 length 3 and insert 2009 type ext)

You would

Location 2
Prefix 201
dials 9 for ARS (change AAR digit-connversion location 2 0 - add entries 0 to 9 type ARS (or could break this out in the same way as ARS if you want more specific lengths)
Extensions 0xxx (change ARS digit-conversion location 2 0 - add 10 entries 0 to 9 and insert 2010 type ext)

bignose21 (Programmer) · Answer 8 · 2019-06-20 20:00:37

After a bit more playing I have found the best way to achieve this is in the Dialplan Analysis to assign 0 & 9 as AAR and not FAC

Then in Loc 1 (prefix 200) that wants 0 for dialing external and 9 as extension, in the AAR Digit Conversion for Location 1 put
Dial 0 - Max 18 (or longer if required) - Delete 1 - net ARS - conv y
Dial 9 - min/max 4 - delete 0 - insert Location 200 - net EXT

Location 2 (prefix 201) that wants 9 for dialing external and 0 as extension, in the AAR Digit Conversion for Location 2 put
Dial 0 - min/max 4 - delete 0 - insert 201 - net EXT
Dial 9 - Max 18 (or longer if required) - Delete 1 - net ARS - conv y

This seems to work quite well so thought I would share.

ZeroZeroOne (Vendor) · Answer 9 · 2019-06-20 22:34:32

Good Job answering your own question! And thanks for sharing!

Come Join Us!

Posting Guidelines

CM 8.0 routing question
2