[cisco-voip] Attendant Console, SRST, hunt pilots

[Wes Sisk]

Same numbers in different partitions will work for park/retrieval  
depending on your CSS. There are some call flows with devices  
registered to different nodes in a cluster where you will encounter  
problems.  For CTI monitoring of park numbers (Attendant Console, IVR  
scripting, etc) same park number in different partitions definitely  
will not work.  CTI does not include partition support until CM5.x  
and even then I have not seen any CTI clients coded to handle the new  
support.

/Wes

On Oct 17, 2006, at 9:20 PM, Kris Seraphine wrote:

Strange, it sounds like you were trying to do exactly what I'm  
doing.  I'm not having any problems using the same park number range  
(in different partititions)  at each of 40 + sites.

On 10/15/06, Robert Kulagowski <bob at smalltime.com> wrote:
For anyone that's still interested, it appears that the root cause was
that we had configured 16[0-4] on the primary and 16[5-9] on the
secondary call manager for each one of our sites (but in different
partitions), thinking that we could make our documentation / training
simpler.  So every site had a "160" as their first call park number.

That doesn't work.  When I changed our test site to 15[0-4], it started
working, so that gave me the clue on where to look further.  Now I have
to go back and re-look at how to allocate our park numbers.

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



-- 
kris seraphine
_______________________________________________
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/20061017/44d774a1/attachment.html