[cisco-voip] Avoiding bounces with overlapping ranges

Lelio Fulgenzi lelio at uoguelph.ca
Thu Sep 2 14:36:46 EDT 2010


Yes, that took me a while to understand when first explained to me, but you hit the nail on the head. 

If you are sending calls to anything off the system (I refer to this as off-box vs off-net) that should be in a separate partition than anything that resides on the system. This could be a PBX, another cluster, etc. 

Add this partition to the CSS of all devices except the inbound trunk that those calls are sent to. 

We had dead air for years when an invalid number was called until we resolved this because our PBX defaulted to send everything else to the CallManager. 



--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 



From: "Bob Zanett (US)" <bob.zanett at us.didata.com> 
To: "Jonathan Madziarczyk" <JMad at cityofevanston.org>, cisco-voip at puck.nether.net 
Sent: Thursday, September 2, 2010 2:30:16 PM 
Subject: Re: [cisco-voip] Avoiding bounces with overlapping ranges 




Do not let your PBX trunks on CUCM see themselves. That is do not let the CSS on the trunks see the route patterns that send calls back to the PBX. 




Bob 





From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Madziarczyk, Jonathan 
Sent: Thursday, September 02, 2010 1:12 PM 
To: cisco-voip at puck.nether.net 
Subject: [cisco-voip] Avoiding bounces with overlapping ranges 



So as we’re migrating off of our antique PBX we have a problem with bouncing calls. 



PSTN -> CUCM -> Gateway(MGCP/QSIG) -> PBX 



Call comes in for extension 8011, its not on the CUCM, there’s a rule for unknown extensions in the 80xx range to go to the PBX. The PBX gets the call, doesn’t show it on it’s list of ports, then sends it up the chain (back to the CUCM)…then the cycle begins. It eventually fills up the ports on our Gateway and they finally get a busy signal (3-10 sec later) and the ports clear again. 



I’m not about to mess with PBX any more than I have to, so without “fixing” the PBX, how can I adapt the CUCM to be smarter with specific number overlaps? 










Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. 
_______________________________________________ 
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/20100902/f3880b9a/attachment.html>


More information about the cisco-voip mailing list