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

[Lelio Fulgenzi]

there is a forward on unregistered in later versions of ccm. i think v6 was the first. 

as a workaround, you could forward all phones that are not registered using the appropriate CSS and route pattern. 

--- 
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: "Kelemen Zoltan" <keli at carocomp.ro> 
To: "cisco-voip mailinglist" <cisco-voip at puck.nether.net> 
Sent: Thursday, October 30, 2008 11:18:44 AM GMT -05:00 US/Canada Eastern 
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 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081030/2284036d/attachment.html>