Mics 7.0 networking with MCDN

[techman63]

ave 2 sites with Mics 7.0,networked together thru a PRI (SL1) with MCDN enabled on both systems ,the main system has a another PRI for out going and DID calls to both systems. They both share the call pilot rel 3 (centralized VM)
My problems is I can't direct the DID from the main location to the remote site and I can't dial out from the remote site. I got busy signal either way.
However I can dial each other on the network and I can dial out from the main location.
I have the system set as CDP (the main site starts with 2580 and the remote site starts with 3600, the DID range for the remote site is 1600-1699), and I have destination codes programmed. and remote package 01 programmed for the PRI pools and the access code is 9 in both systems and I programmed the Private act as (9) ,and I have a destination code as 9 using the route with the PRI access, I also modified the public DN in the remote site and added 9 and increased the length by one. I know I’m missing something but my brain is shot right now, I have done it before with Mics and BCM.
If anyone can shed some lights I really appreciated.

 

[aragon]

On remote site you will have to configure you destination code to absorb 0 digits and increase public DN lengths by 1 digit.
At the main site the destination code 9 must absorb 1 digit only to absorb the 9.
Remote access package must be assigned to the trunks and PRI's access must be allowed in the remote access package.
If you are using 9ANY then press show and allow for each leading digit after the 9.

 

[techman63]

Aragon, Thanks for the response,
I had set all that and the calls was not going thru till I reboot both system last night and now the calls are going from the remote site over the public network just fine. (Reboot miracle I guess) However my problem now that I can't figure it out it how to route DID (range 1600-1699) calls over PRI from the main site to the remote site (extension range is 3600-3699) thru the PRI configured as SL1 with MCDN enabled on both systems, what kind of routing I should create. There is no option for target line redirect (like the BCM) so I’m kind of a lost, for now (temporary solutions) I had to do some remote forwarding from spare station on the main site to the remote site just to send the DID across know it has to be some kind of routing table but its not clear for me how. I appreciate any inputs

 

[hawks]

You can redirect Target Lines just like you would normal lines

 

[techman63]

That’s what I have done so far with no luck.
I tried to create a destination code with received digits i.e. 1600 and using a route i.e. 002 using the PRI pool with absorb digits all and dial digits the other remote extension i.e. ext 3600,and have the route as private and in the remote site I created a target line with received digits and assign it to the extension, didn’t work, The PRI pool has a remote package of 001.
I also tried to create a target line on the main site with received digits and tried to create a destination code but for sure I can't because its conflicting with received digits.
So I appreciate any inputs.

 

[aragon]

Here is what I would try:
On the main site delete any target line with the received digits you wish to forward to remote site.
Create destination code which equals this received number and use the route that is private to the P2P PRI. Set absorbed digits to 0 for this dest code.
At the remote site configure a target line with these received digits and assign this as a ring only line assignment to the set at the remote.
But it sounds like you have already tried this.
You could also assign the target line at the main site to a set and in capabilities allow redirect then you could feature4 (hard forward) to the remote site to an extension.
This does work but it requires you use a set or ATA permanently forwarded to the second location.

 

[hawks]

Try this
Example: Want # 555-1234 to go to extension 2345 at site B using both the Public & Private PRI from Site A.
If you call direct from site A you dial 2345 (desti 2any in my case) to get to that extension in site B.

1) Build Target Line for 555-1234 at site A.
2) Put that Target Line on a phone in site A
3) Use F84 Line Redirect to direct that line back out to the Private PRI to site B (2345).
4) Remove Target line from phone in site A (the line will stay redirected).

Keep good records in case you need to change any of the Redirected Lines in the future.

 

[techman63]

I have done what you mentioned but it didn't go thru, and I'm using the call forward right now as a temporary solution, however call forward or line redirect its not good solutions because if the system lost power it will has to be reprogrammed.
It seems I was on the right track but I’m not sure why it’s not working. I had the same solutions done before but was MICS rel 6.1 MR, I wondering if Rel 7 has an issue.
I appreciate any inputs.

 

[techman63]

Here is an update,
I replaced the s/w Mics 7.0 in the main site and the system starts to work and route the DID to the remote site like it suppose to be (looks like the s/w was corrupted), however I have a problem now with centralize VM, If I call from the remote site to any extension on the remote site or to the main site the calls goes to the correct mail box just fine, however if an outside calls comes in to the remote site thru DID to the extension it will goes to the general delivery mailbox instead of the correct mailbox. The other crazy problem when call made from the main site to the remote site extension it will ring the extension correctly and it will forward to the main site and you will see on the main site phone the message using line i.e. 250(the target line for the VM) and small pause and a message not in service and after that you will hear a busy signal.
Any ideas.....

 

[hawks]

Have you verified that the target line is set up for External Messaging allowed.

 

[techman63]

Yes I have all that done,The calls if its made from the remote site to any extension on the remote site ,the calls goes over the network to the VM to the correct mailbox.

 

[hawks]

Yes but calling internal at site B does not use a target line of site B. Call from site A, call comes in on Target line 170 of site B make sure that line 170 is set up.

 

[techman63]

I have that set as well, each set in the remote site has 2 target line, one for the extension number across the network and the other one for the DID (DID doesn't match the extension) and both lines are enabled for external V msg under teleco feature. As I mention earlier, when the calls comes in on the DID it goes the General MB, but if the calls comes internally across the network from site A (main site) to the remote site the calls forward back to the main site with a message on the display of the phone which imitated the call line not in service (i.e. 250 the target line for VMDN) and busy signal afterwards. I already replaced the main site s/w after having problem routing calls and that’s fixed the DID routing and I’m trying now to replace the remote site s/w but having problem with vendor. In realty I would like to replace the s/w to 6.1 instead of 7 but it’s not possible at this time. Thanks for your thoughts and I appreciate any inputs.