Stripping PNI between clusters

[PureChimpie]

Hi All

I have an old MCD4 cluster with a PNI 499 and new MCD7 cluster without a PNI. All sets from the old cluster are being migrated to the new virtual cluster.

I have a slight issue with the voicemail on my new cluster. As all extensions are arriving with their PNI tag 499+Extension. I have to add an alternate extension in Nupoint so the digits match. I need to find a way around this as I have 6,000 users to migrate.

Eg calls comes from old cluster for ext 499 37981 which is then call fwd always to 89101 37981 (89101 routing digits from old cluster to new). Nupoint mailbox is 37981 with an alternate number of 499 37981. Nupoint is matching the digits of the incoming CLI 49937981.

I need to strip the PNI499 if possible? I have tried absorbing 3 digits on the incoming IP trunk att's but the call fails.

Any thoughts?

Thanks

 

[kwbMitel]

You should be able to modify the digits on the sending system

Can you remove the PNI in the old cluster altogether? No Conflicts?

**********************************************
What's most important is that you realise ... There is no spoon.

 

[PureChimpie]

Removing the PNI isn't an option unfortunately. I don't see how I can remove the 499 tag from the extension. I can modify the digits it sends across to the new cluster, but the originating CLI 49937981 looks unbreakable?

 

[jpruder]

Maybe absorbing 3 in trunk service for the link, or doing a loopback that removes them

 

[kwbMitel]

The CLI would not be modifiable.

I forgot we were talking about VM integration, sorry.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[PureChimpie]

I had to use the following script in NuPoint to add the alternate extensions and it works very well:

om=37981 ae1=49937981

This will add an alternate mailbox of 49937981 when the script is run. I created some much larger scripts and it works very well.

No way of stripping the PNI499 off.