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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2 MICS units back to back using PRI 1

Status
Not open for further replies.

RedHawkFla1

Technical User
Jun 25, 2002
13
US
I thought that the following senario could be done but I may have been mistaken on one part. I do have an idea I'd like feedback on.

Senario: Two MICS(unit A and B) units using PRI are connected Point to Point. Unit (A) also has PSTN connection and a NAM voicemail while Unit (B) has a Flash voicemail.

Three Objectives:
1. Seamless dialing between the systems as if it's one system. No pool code when dialing.

2. Outside calls must be able to be transfered from A to B and B to A seamlessly.

3. MICS (A) NAM Auto Attendant routing calls to MICS (B) must be possible. No Flash AA routing.

Well, 1 and 2 are pretty easy. Using SL1 protocols, and making the dial plan unique to each system(ex:starting extensions 221 for A and 321 for B). Un-equiping any duplicate extensions in either system so you can use Route and Destination Codes with Absorb = none. So let's say (3 + any) for switch A desticodes for PRI A and (2 + any) for switch B desti codes for it's PRI A. So you can seamlessly call 321 from A to B and 221 from B to A. The Transfers also work fine.

Step 3 is a problem. Of course if you are in MICS (A) and in the AA of the NAM and want to dial 321 it fails because it is not a valid extension.

I wonder if this will work? The only way I can think of is by fooling the system using the CCR tree and recording dead air for menu recordings routing the call to MICS B. I'm also not sure about the timing issues when entering digits.

Idea example: MICS A CCR tree to call extension 321.
path 0 = menu (dead air recording short)
path 3 = menu (dead air recording short)
path 32 = menu (dead air recording short)
path 321 = external transfer point to 321 (MICS B)

This may be too funny to consider but I'm going to try it tomorrow morning, or come to my senses! If anyone has an idea besides me giving up I'd appreciate it.

I know that MICS 6.0, to be released in September(ha!) It will address the centralized voicemail, Auto Attendant, unique dial plan and 3rd T1 issues plus more but I can't wait.

Thanks for reading this saga.
 
OK, I tried it and of course it didn't work. :~/

Timing issues. I was hoping you could enter path numbers quickly but you can't. So this won't do it, too bad.
 
Redhawkfla,
Unfortunately you cannot have the transfers from voicemail/AA to another system at all, the voicemail and ICS are looking for extension transfers and cannot handel transfers out of the local ICS. the next version release is SUPPOSED to allow you to have a common voicemail on one of multiple norstar systems (ver 5.0 lets you have a common voicemail only if connected to an option 11(meridian).

I have connected up two ICS back to back and worked ok for other transfers and direct dialing, also calling name ID between systems, it is just the AA that will drive you willies trying to think of a way to spoof the system. JerryReeve
Communications Systems Int'l
com-sys.com
 
Right.... I was trying to find a way to fool it. You can use CCR to transfer though. Thanks, I appreciate your help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top