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

Centralized VMS / VMI Conversion Number 1

Status
Not open for further replies.

CableMonkey

Technical User
Sep 26, 2002
92
US
Has anyone out there successfully setup a “Centralized VMS”?

I have two locations, each with a Merlin Magix. They are already tied together with a T1 and UDP.

Only the first location has a Merlin Messaging system. I would like to use the Merlin Messaging system for both locations.

I am having trouble setting up the “VMI conversion number”. When I go to the VMI calling group on the second system, and try to select a valid non-local number as the only member of the group, nothing happens. It won’t let me add the non-local extension to the calling group.

I have verified that the non-local number does exist in the dial plan, it has a route and all the other settings look good.

Any suggestions?
 
If you using calling group 770 in the main switch then you have to use the same no. in the second switch ,In the second switch in the calling group member you can add i.e 699 as a member (phantom no) .Under non local UDP range enter 699 ,under UDP routing assign a pattern 2 and route 1 ,using the same pool between the two location .Under absorb you enter 3 digits for (699) and under add digits you add 770 (the calling group no.)and make sure the FRL is zero.You can use the group coverge 30 and assign it to the calling group 770.I hope I didn't confuse you.

Good Luck.
 
Thanks for the suggestion. That is exactly how I have it setup. The only differance is my calling group is 7929. The system will only let me add the non-local number to the calling group when I change it to “auto login” or “auto logout”.

Question: The conversion number doesn’t actually need to exist in the system with the VMS, does it?

 
The answer is no.The calling group must be INT VMI,with one member i.e 699 and you will convert that in your routing table and delete the 3 digits and add 7929.It should work fine I do that all the time.

Good Luck.
 
I finally got it to work by following the same procedure, but using Standard SPM instead of SPM Quick Access. There must be a bug in my SPM. I am running version 7.0
 
That's the same version I use but I never use Quick access, for that kind of programming. Std spm is the way to go. Quick access is usually good for programming extensions.Anyway I'm glad that you got it to work. That's all that matters.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top