[cisco-voip] Meridian Call Routing

[Jonathan Charles]

Their initial intent is that the CCM be a pilot program (if it works, they
will agree to finish the implementation, they are still pretty convinced
that CCM is completely unreliable and unstable (thank you sales guys!).

To that end, they want the calls to hit the PBX first and the DIDs they are
moving to route on over to CCM. I asked them to do this with a contiguous
block of numbers, but they want to distribute the IP phones in each
department (they don't appear to want to discuss this matter, they made a
decision, they don't care how wrong it is, they just want it done their
way).




Jonathan

On 12/4/06, Voll, Scott <Scott.Voll at wesd.org> wrote:
>
>  I'm setup in the opposite direction……. CM is connected to the PSTN and
> the PBX is behind the CM.  Then I just setup a Route Pattern of xxxx to go
> to the PBX.  Anything CM doesn't know goes to the PBX.
>
>
>
> Will they let you get in front of the PBX?
>
>
>
> Scott
>
>
>  ------------------------------
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Jonathan Charles
> *Sent:* Monday, December 04, 2006 8:27 AM
> *To:* cisco voip
> *Subject:* [cisco-voip] Meridian Call Routing
>
>
>
> Customer is migrating (way too slowly) from Meridian to VoIP
> (CallManager).
>
> Customer has around 300 phones, they want to move 50 phones over to
> CallManager (already in place), but the phones are random (I cannot figure
> out how they were picked).
>
> These 100 phones are intermixed (DID-wise, so extensions 2940-2340 are on
> the PBX, 2341, will be moved, 2342 will stay on the PBX, etc...) all calls
> come in on six PRIs, which are connected to the Meridian... Selecting a
> contiguous range of DIDs is not an option.
>
> Can I route individual DIDs over a QSIG trunk to the CCM? (IOW, call comes
> into PBX for x2341, gets routed over QSIG to 2851 for CCM)? Or only blocks?
>
>
>
> Thanx...
>
>
>
> Jonathan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061204/88d0cafe/attachment.html