[cisco-voip] Route but don't Route!
Lelio Fulgenzi
lelio at uoguelph.ca
Mon Apr 9 13:33:28 EDT 2007
The secret to this is partitions and calling search spaces. Basically, you have to seperate into different partitions the translation patterns you only want your PRI to access and then you have to configure the calling search space that you will assign the translation so that it doesn't have access to the route patterns your users see.
It's the two together that you have to make sure to attend to.
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...there's no such thing as a bad timbit...
----- Original Message -----
From: Todd Franklin
To: cisco-voip at puck.nether.net
Sent: Monday, April 09, 2007 1:23 PM
Subject: [cisco-voip] Route but don't Route!
Hi everyone.
So we have this line 555-8657 that I pointed to the PRI. So I tell CCM that when it sees 8657 come down the line, to route it to
extension 1302. Only problem is that one of our buildings, we use an 8 for an outside line. (Don't ask why, it's convoluted!) Anyways,
yep, someone needs to call 657-1212, well they press 8 for the outbound line, then 657 and then they are automatically transferred
to X1302. How do I stop that?? Can I stop it just for that building?? All their extensions begin with 14.
Thanks.
------------------------------------------------------------------------------
_______________________________________________
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/20070409/81dcb05e/attachment.html
More information about the cisco-voip
mailing list