[cisco-voip] how to allow alternate routes for unregistered phones

[Lelio Fulgenzi]

Yes, I keep forgetting to mention that....must make sure the PBX trunk CSS doesn't include patterns that route back to itself. 

Of course, I think there is a loop prevention parameter, but it will take up channel after channel..... 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Ryan Ratliff" <rratliff at cisco.com> 
To: "Nick Thompson" <Nick.Thompson at gocorptech.com>, "Kelemen Zoltan" <keli at carocomp.ro>, "cisco-voip mailinglist" <cisco-voip at puck.nether.net> 
Sent: Thursday, October 30, 2008 11:38:30 AM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] how to allow alternate routes for unregistered phones 

I'd do it the other way and set the 4XX route pattern in another partition, 
ie PBX. 

To eliminate call routing loops you disallow the PBX gateway to call itself 
(via CSS). 

For your phone 452, set the CFNA destination to 452, with a CSS set on the 
CFNA destination that allows it to reach the PBX partition. 

In all versions that don't have the specific value for forward unregistered 
the CFNA destination is used when the device is unregistered. 


-Ryan 
-----Original Message----- 
From: cisco-voip-bounces at puck.nether.net 
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nick Thompson 
Sent: Thursday, October 30, 2008 11:32 AM 
To: Kelemen Zoltan; cisco-voip mailinglist 
Subject: Re: [cisco-voip] how to allow alternate routes for unregistered 
phones 

Make sure that the route-pattern is inside the same partition as your DNs. 

Route Pattern 4XX in partition INTERNAL 
DN 4XX in partition INTERNAL. 

Nick Thompson 
Senior Network Engineer 
Corporate Technologies, LLC 
E-Mail: nick.thompson at gocorptech.com 
http://www.gocorptech.com/ 


-----Original Message----- 
From: cisco-voip-bounces at puck.nether.net 
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Kelemen Zoltan 
Sent: Thursday, October 30, 2008 10:19 AM 
To: cisco-voip mailinglist 
Subject: [cisco-voip] how to allow alternate routes for unregistered phones 

Hi! 

I'm trying to migrate some phones from a PBX to a CCM system. The CCM 
currently has a route pattern towards the PBX and the migrated phones will 
have extensions from the same range. 

Since there are a lot of phones and some administrative hurdles as well, I 
can't just move all the phones at once. What I wanted to do, was to register 
the IP phones in the CallManager, keep the route pattern, and deploy the 
phones as I can. 

I just supposed, that a phone, as long as it's not registered with the 
CallManager won't "take over" the call to it's line number and allow the 
call to go out on the route pattern. Only it isn't working like that. Is 
there any setting I can change to make it work like I expect it to? 

Ex: 

Route pattern to 4XX goes out to gateway. 
451 is registered to CCM, 452 is configured but in "not registered" 
state, 453 isn't added to CCM at all. 

What I expect to happen: 
Calling 451 rings out on IP phone, while calling 452 and 453 would go out to 
the PBX and ring there, if applicable. 

What happens instead: 
451 rings, 452 gives busy, 453 goes to PBX. 

Dialed Number Analyzer shows an alternate match for 452, but that's it. 

(I'm currently testing this on CCM4.2, with a IP Communicator, but I don't 
really think that's relevant) 

thanks, 
Zoltan 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 

_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081030/29352967/attachment-0001.html>