markj39k

Hey Merlin Heavy Hitters,

I have mucho big problem. I must network together, with centralized
VM, 2 Merlin 7.0's, with one Merlin having a PRI to the outside world.
I have very good skills/ comfort level with the Merlin, EXCEPT for ARS.
These 2 systems are sitting on my test bench, with accompanying CSUs,
ready to rock.
The good news: Just by setting up the "PRI" correctly and putting
the opposing extension ranges in the UDP under SYS RENUM, I can ICOM
call between the systems.
The bad news: I cannot transfer an outside call between the systems,
and the time has come for me to do the ARS programming associated with
the one system having the only connection for outgoing ( a PRI) and
the fact that DIDs are incoming. I have read (over and over) the Merlin
Manuals on "routing" but as you might agree, nowhere is the relationship,
the mojo, between ARS, UDP, tables, stats, blah, blah, blah explained.
An example: I have more experience on the N* and I woud give a
brief explanation on n* routing thusly; Lines (Digital or not) go into
pools with there own kind. Destination codes are digits or digit patterns
that the user dials, when the destination code is matched, it points to a
Route (digits can be stripped here). Routes point to pools (digits can
be added here) and there goes the phone call. Merlin routing seems
way waY WAY more complicated.
At any rate: Could someone give me a similar primer on Merlin
routing, I can look up individual terms, I just have no idea how it all
fits together.
Since you stayed this long: one more quickie, From the Merlin
Networking Manual, page 2-17. This VMI Conversion number is mentioned
alot, but what is never explaned is, is this a number that I just pick out of
the sky arbitrarily ? Or is it somehow related to the extension range or the
VM Calling group or uh..... what ?

Thanks in advance for your time ! No foolin' !