Can I set up a CDP to an internal DN? 2

[krby_34]

PC, Server, Network guy that has done VOIP phone system on the side and has done some Meridian support and maintenance but never developed a call manager outside of asterisk.

Meridian system. I have two DN (5555 and 5211) that our staff is used to calling for particular needs. We are starting to migrate to a VOIP system however this call manager is multi-site controlled where my meridian was single site management. Our extensions will be changing as our 5xxx group was given to another site. Our new numbers are 2xxx group.

The new contact numbers will be 2555 and 2211 on the VOIP system. We want all phones on the site to be able to dial the same number for contacting these phones. There will be a VOIP phone at the location that will be configures for the VOIP DN (vDN) 2555 and vDN 2211. The old Meridian phone will remain at this location as well and will still be Meridian DN (mDN) 5555 and 5211. I want people on the Meridian phones to be able to dial 2555 and have it direct the call to mDN 5555 and dial 2211 and have it direct the call to mDN 5211.

Suggestions please.

Thank you,
Kevin

 

[Wanebo]

Create a couple of phantom 500's and DCFW them to the old numbers.

 

[KCFLHRC]

You can also build a Dummy ACD Que also and NCFW them, however, your scenario is quite confusing and I think I'm still missing something about your request. Seems like a round about way to accomplish something very easy. You cant have numbering conflicts in any way, the number either resides in the M1 or it is a CDP Entry sending it across the TIE Lines.

 

[KCFLHRC]

Maybe I read this again and understand now

5555 will remain on the M1 but you want to dial 2555 to reach this number, correct?
5211 will remain on the M1 but you want to dial 2211 to reach this number, correct?

Keep in mind, 2555 and 2211 have to be vacant numbers in the M1, if so then do this

Go into LD 23 and do this

REQ new
TYPE acd
CUST 0
ACDN 2555
MWC
DSAC
MAXP 1
SDNB
BSCW
ISAP
RGAI
ACAA
FRRT
SRRT
NRRT
FROA
CALP
ICDD
NCFW 5555
FNCF
FORC
RTQT
SPCP
OBTN
RAO
CWTH

Then do the same thing for 2211

 

[krby_34]

Okay a new wrinkle. Don't know why I didn't see this coming sooner...

2* is already a CDP for making outbound calls.

How do CDP lists get processes?

Is it possible to develop the CDP in such a way like a nested IF-THEN-ELSE?

IF dialed digits = 2555 (no other digits)

THEN go to lsc 5555​

ELSE IF dialed digits = 2211 (no other digits)​

THEN go to lsc 5211​

ELSE IF dialed digits = 2 (any other digits)​

THEN go to dsc (all digits after 2)​

END​

END​

END

If this is possible they would dial:
1) 2555 and my 5555 phone would ring.
2) 2211 and my 5211 phone would ring.
3) 25551237654 and outbound trunk would be used to dial 555-123-7654.

Anyone see a way around this for me?

Thanks,
Kevin

 

[KCFLHRC]

You will have to break out the CDP entries instead of having just "2" as the entry, it will be a lot of work.

So instead of the entry 2 you will have to have entries like

21
23
24
26
27
28
29

Then it gets fun for the rest of the entries

220
2210
2212
2213
2214
2215
2216
2217
2218
2219
Noticed I skipped a CDP entry for 2211, because it will stay local

See what I mean, lots of work

 

[krby_34]

KCFLHRC,

Thank you so much.

Yes you are correct on your rereading of it. I want to dial and stay local so the ACD would likely work also. However I do need the unique numbers in the M1 to be unused. As they are currently "used" in the CDP for "starts with 2" I would need to modify the CDP list as you have shown above. This could get very messy....

Thank you.

Kevin

 

[krby_34]

UPDATE: I think I found it. I believe the ACOD for my Routes on the COT Trunks are set to 2 so that is what is taking anything I dial that starts with a 2. Is this correct?

Okay this may show my inexperience in setting up systems even more...

I pulled up my CDP list. I have a bunch of DSC in the list but not any that start with 2. Where else could this be located be found?

All items in my CDP are for steering to one of two PRI routes I have two remote buildings that have their own M1 at them that this M1 is the primary system for. So a long list of extension (5513, 5527, 5833, 5969, etc) go to Route 7 on PRI to building 2. A single CDP with DSC 6 goes to Route 6 on PRI to building 3 (all of their phone extensions are 6xxx).

Currently if any building phone dials a number that starts with 2 it evaluates the string and if a valid area code it sends it to an outgoing trunk in Building 1 and dials all digits after the 2. If not valid area code you get a fast busy signal. So in my case as soon as I type 233 I get a fast busy signal because there are not any valid area codes that start with 33 in my 10 digit calling area. I would have to dial 2133x7778888 to make it work.

Cannot find where this resides in the M1 configuration.

Thank you,
Kevin

 

[KCFLHRC]

Sounds like you have your work cut out for you researching your numbering plan. You would have to print out a DNB in LD 22 to see what each digit is doing. Typically you would dial a 9 prior to any other digit for an outbound call. It's all a mystery until you have that DNB in your hand and you see what 2 is actually doing.

 

[bignose21]

If you are on later release like 7.6 you can use number zones and example would be

LSC 2555 delete 4 insert 5555 type cdp (or use a phantom for the same)

ZFDP entry 2 send it where ever you want.

Down side to this is you need to add a numberzone prefix which means altering all DNs and adding the prefix and numzone to all sets.

I use it mainly where say we have a PABX connected to Sonus SBC as an entry into Lync/SFB all e164 so say all 4 digit DNs start with 2 and the NPA is 213 and NXX 444 you could just add a ZFDP

new zfdp xxx 2 npa 2134442 (xxx=numzone)

That way allows 4 digit dialing to full e164 if it doesn't find a match in DN Tree, if an entry exists on the PABX then it has priority over ZFDP.

Probably a bit much to take on but certainly can achieve what you are looking for.