[cisco-voip] Meridian Call Routing

Ryan O'Connell Roconnell at unislumin.com
Mon Dec 4 16:15:10 EST 2006


Hi Gary,

 

What you are saying is correct, typically in the past Vacant Number
Routing was used to send to an attendant, give a fast busy or a RAN
recording. I do believe as of Succession 3 you should also be able to
point VNR to PRI as well.

 

Ryan

 

________________________________

From: Sullivan,Gary,GREENWICH,Information Services
[mailto:gary.sullivan at waters.nestle.com] 
Sent: Monday, December 04, 2006 12:35 PM
To: Ryan O'Connell; cisco voip
Subject: RE: [cisco-voip] Meridian Call Routing

 

With Vacant number routing on the Meridian you can't send out of the
system. You can send it to the attendant ,give it fast busy or a RAN
recording .

You need to use a feature called CDP. and send each DID or group of
DID's (as small as 10) to the CCM

	-----Original Message-----
	From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Ryan O'Connell
	Sent: Monday, December 04, 2006 1:56 PM
	To: cisco voip
	Subject: Re: [cisco-voip] Meridian Call Routing

	Another option that may simplify this is to use the "Vacant
Number Routing" feature if supported on the Meridian. In summary this
feature is similar to the "default gateway" in the routing world.
Essentially any local that is not found on the Meridian can be simply
shipped out the QSIG PRI to CCM. CCM can then match the digits sent to
DN's in its own database or if no match is found we can give a busy
signal or alternatively send it elsewhere, ie: Unity Call handler that
tells the user that the number dialed is invalid. This way it's simple
on both sides of the fence from a DialPlan standpoint.

	 

	Regards

	 

	Ryan O'Connell CCIE VOICE #13382
	Network Consultant
	UNIS LUMIN - Technology Based Business Solutions
	Phone: 888.475.0432 x290

	Mobile: 403.990.1275

	roconnell at unislumin.com <http://www.unislumin.com/> 

	http://www.unislumin.com <http://www.unislumin.com/> 

	
________________________________


	From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Fred Nielsen
	Sent: Monday, December 04, 2006 10:57 AM
	To: 'Vince Loschiavo'; 'Mike Lay (milay)'; 'Jonathan Charles';
'cisco voip'
	Subject: Re: [cisco-voip] Meridian Call Routing

	 

	This is correct, we've done this plenty, with installations up
to the 5000 handset range.  It eventually will get real ugly on the
Nortel end of things, but since that system is phasing out, not a huge
deal here I would think.

	 

	-- Fred Nielsen

	 

	
________________________________


	From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Vince Loschiavo
	Sent: Monday, December 04, 2006 9:05 AM
	To: Mike Lay (milay); Jonathan Charles; cisco voip
	Subject: Re: [cisco-voip] Meridian Call Routing

	I disagree.  You can just route the DIDs you want from the
Nortel to CCM over the QSIG.  You don't have to route the whole block.
As you migrate one user from the Nortel to CCM, you route his DID on the
Nortel.

	 

	
________________________________


	From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike Lay
(milay)
	Sent: Monday, December 04, 2006 11:33 AM
	To: Jonathan Charles; cisco voip
	Subject: Re: [cisco-voip] Meridian Call Routing

	It can be done but will be a very ugly Route plan in CCM! I
would recommend that you implement some type of prefix in the NT & the
CM until the migration is complete. After the migration is complete the
prefix will not be needed & you may return to a more simple dial plan.

	 

	Mike

	 

	
________________________________


	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 10: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

	
________________________________


	Privileged/Confidential Information may be contained in this
message.  Disclosure to any person other than the named recipient is
unauthorized.  If you are not the intended recipient, please delete all
copies of this information and kindly notify the sender by reply email.
Opinions, conclusions and other information in this message that do not
relate to the official business of UNIS LUMIN Inc. shall be understood
as neither given nor endorsed by it.  UNIS LUMIN Inc. and any of its
subsidiaries reserve the right to monitor all e-mail communications
through its networks.  Thank you. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061204/00753b1a/attachment-0001.html 


More information about the cisco-voip mailing list