<div dir="ltr"><div>You need RP for both # and without # for calls to route if your users dial # sign to complete a number and some users don't dial # to indicate end of dialing. It wont work without that because of CCM 's exact match digit analysis.</div>
<div> </div>
<div>Also you need to set the service parrametter # to indicate end of dialing to true for CCM to treat it as end of dialing.</div>
<div> </div>
<div> </div>
<div>Aman<br><br></div>
<div class="gmail_quote">On Mon, Sep 22, 2008 at 10:42 PM, Kumar, Narinder <span dir="ltr"><<a href="mailto:Narinder.Kumar@getronics.com">Narinder.Kumar@getronics.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">"#" in the route pattern tell the call manager that this is the end of<br>the DNIS and CCM will not wait for more digits and will route the call<br>
ASAP, if the "#" is not present still ur call will go through but after<br>the T302 ( inter digit timeout) timer expire.<br><br>In my views in CCM ver 4.x you can't force the users to dial # after the<br>DNIS ( Please double check I could be wrong)<br>
<br>Thanks<br>Narinder<br><br><br>-----Original Message-----<br>From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of<br>
<a href="mailto:cisco-voip-request@puck.nether.net">cisco-voip-request@puck.nether.net</a><br>Sent: Tuesday, 23 September 2008 2:52 PM<br>To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>Subject: cisco-voip Digest, Vol 59, Issue 187<br>
<br>Send cisco-voip mailing list submissions to<br> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
or, via email, send a message with subject or body 'help' to<br> <a href="mailto:cisco-voip-request@puck.nether.net">cisco-voip-request@puck.nether.net</a><br><br>You can reach the person managing the list at<br>
<a href="mailto:cisco-voip-owner@puck.nether.net">cisco-voip-owner@puck.nether.net</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of cisco-voip digest..."<br>
<br><br>Today's Topics:<br><br> 1. Re: Another SRST Question (James Buchanan)<br> 2. questionable OT: MCU (Scott Voll)<br> 3. Re: questionable OT: MCU (Matthew Saskin)<br> 4. Re: Route pattern question (Jason Burns)<br>
5. CUVA & UC520 (Daniel Hooper)<br> 6. Re: Cisco VPN for voice routers... (Syed Khalid Ali)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 22 Sep 2008 17:19:59 -0400<br>
From: "James Buchanan" <<a href="mailto:jbuchanan@ctiusa.com">jbuchanan@ctiusa.com</a>><br>Subject: Re: [cisco-voip] Another SRST Question<br>To: "Todd Franklin" <<a href="mailto:toddnh65@gmail.com">toddnh65@gmail.com</a>>, <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
Message-ID:<br> <<a href="mailto:84FD0A05752C5C408C811C5D07205B25060740C0@EXCHANGE.ctiusa.com">84FD0A05752C5C408C811C5D07205B25060740C0@EXCHANGE.ctiusa.com</a>><br>Content-Type: text/plain; charset="us-ascii"<br>
<br>The phones would keep their old IP until their lease is up. When their<br>lease is up, they'd go looking for a new IP.<br><br><br><br>From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Todd Franklin<br>Sent: Monday, September 22, 2008 4:09 PM<br>To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
Subject: [cisco-voip] Another SRST Question<br><br><br><br>I have a question in regards to SRST.<br><br>If the phones go down, how do they get an IP address? In my case, CCM<br>hands out the IPs for the phones, and it's in a different building<br>
connected by fiber. So if the link were to die, would the phones be<br>able to operate? Would the 2801 at this location hand out IPs or would<br>the phones somehow keep their old IP and keep working?<br><br>Just curious.<br>
<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL:<br><<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20080922/f8a889f1/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20080922/f8a88<br>
9f1/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 22 Sep 2008 15:52:43 -0700<br>From: "Scott Voll" <<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>><br>
Subject: [cisco-voip] questionable OT: MCU<br>To: "<a href="mailto:cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
Message-ID:<br> <<a href="mailto:f84a38d30809221552t7369b785r450f93f0aabbf203@mail.gmail.com">f84a38d30809221552t7369b785r450f93f0aabbf203@mail.gmail.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br>
<br>If we were not integrating our MCU choice into CM and using only for<br>H323<br>video conferencing (maybe H320 isdn), knowing you have a combination of<br>Vtel<br>(very little left), tandberg, polycom, sony, etc What vendor / model<br>
would<br>you go with for Video conferencing?<br><br>I'm leaning toward either Tandberg or Polycom.<br><br>all coments welcome. but I'm not looking for vendor coments ;-) only<br>real<br>world experience.<br><br>Thanks<br>
<br>Scott<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL:<br><<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20080922/f368cf94/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20080922/f368c<br>
f94/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 3<br>Date: Mon, 22 Sep 2008 19:28:49 -0400<br>From: Matthew Saskin <<a href="mailto:matt@saskin.net">matt@saskin.net</a>><br>Subject: Re: [cisco-voip] questionable OT: MCU<br>
To: Scott Voll <<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>><br>Cc: "<a href="mailto:cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
Message-ID: <<a href="mailto:48D82A31.1000608@saskin.net">48D82A31.1000608@saskin.net</a>><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br><br> From my own experience (and running through a lab testing process<br>
recently with all the gear) I'd go with Codian<br><br>-matt<br><br>Scott Voll wrote:<br>> If we were not integrating our MCU choice into CM and using only for<br>> H323 video conferencing (maybe H320 isdn), knowing you have a<br>
> combination of Vtel (very little left), tandberg, polycom, sony, etc<br>> What vendor / model would you go with for Video conferencing?<br>><br>> I'm leaning toward either Tandberg or Polycom.<br>><br>
> all coments welcome. but I'm not looking for vendor coments ;-) only<br>> real world experience.<br>><br>> Thanks<br>><br>> Scott<br>><br>------------------------------------------------------------------------<br>
><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br><br><br><br>------------------------------<br><br>Message: 4<br>Date: Mon, 22 Sep 2008 20:56:01 -0400<br>From: "Jason Burns" <<a href="mailto:burns.jason@gmail.com">burns.jason@gmail.com</a>><br>Subject: Re: [cisco-voip] Route pattern question<br>
To: "Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>><br>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>, "cisco.voip" <<a href="mailto:cisco.voip@verizon.net">cisco.voip@verizon.net</a>><br>
Message-ID:<br> <<a href="mailto:78d9bfc20809221756g58120c0bk74a7e374e69723b9@mail.gmail.com">78d9bfc20809221756g58120c0bk74a7e374e69723b9@mail.gmail.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br>
<br>Lelio,<br><br>That's right - when you explicitly add the # to the end of the<br>RoutePattern<br>you cannot match that by dialing without hitting the # key at the end.<br><br>You can see what pattern you're hitting by looking at the traces, or by<br>
running dialed number analyzer.<br><br>On Mon, Sep 22, 2008 at 11:30 AM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>><br>wrote:<br><br>><br>> It's probably matching another route pattern, specific or not.<br>
><br>> Do you have any wildcard patterns that allow for 7 digit dialing? Or<br>are<br>> you using the @ macro with a 7digit dialing filter?<br>><br>> As far as I know, if your route pattern has a # in it, it won't work<br>
> without it.<br>><br>> I'm sure the list will deny/confirm that assumption.<br>><br>> ---<br>> Lelio Fulgenzi, B.A.<br>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>> "Bad grammar makes me [sic]" - Tshirt<br>><br>><br>><br>> ----- Original Message -----<br>> From: "cisco.voip" <<a href="mailto:cisco.voip@verizon.net">cisco.voip@verizon.net</a>><br>
> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Sent: Monday, September 22, 2008 11:16:58 AM GMT -05:00 US/Canada<br>Eastern<br>> Subject: [cisco-voip] Route pattern question<br>
><br>> I have a route pattern that I need the user to press the # key to<br>place the<br>> call.<br>> The route pattern is 5551212#, however, when the user dial 5551212 and<br>> waits<br>> a couple of seconds the<br>
> call is dialed anyways. Is ther e a CCM setting to change I use<br>CCMv4.2.<br>><br>> Thanks<br>><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL:<br><<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20080922/d4f7d80f/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20080922/d4f7d<br>
80f/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 5<br>Date: Tue, 23 Sep 2008 11:07:52 +0800<br>From: "Daniel Hooper" <<a href="mailto:dhooper@emerge.net.au">dhooper@emerge.net.au</a>><br>
Subject: [cisco-voip] CUVA & UC520<br>To: <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Message-ID:<br> <<a href="mailto:AF85579EB84D4F45A0CBB63DC6747F0225D608@md.team.emerge.net.au">AF85579EB84D4F45A0CBB63DC6747F0225D608@md.team.emerge.net.au</a>><br>
Content-Type: text/plain; charset="us-ascii"<br><br>Hi All,<br><br>I've recently deployed 3 UC520's across 3 sites.<br><br>I have created SIP dial peers between the 3 sites to allow them to call<br>
each other over the VOIP network, what I'm looking to do now is deploy<br>CUVA end points to the users to create a video calling solution.<br><br>>From what I've learnt so far, CUVA isn't going to work with SIP, H323<br>
is<br>required to carry video calls across sites.<br><br>Can this be achieved with the UC520 platform?<br><br>If so, is it as simple as creating H323 trunks between the sites?<br><br>Thanks for any help, I'm relatively new to the cisco VOIP world, a kick<br>
in the right direction would be much appreciated.<br><br>Regards,<br><br>-Dan<br><br><br><br><br><br><br><br>------------------------------<br><br>Message: 6<br>Date: Tue, 23 Sep 2008 09:51:53 +0500<br>From: Syed Khalid Ali <<a href="mailto:khalid_khursheed@hotmail.com">khalid_khursheed@hotmail.com</a>><br>
Subject: Re: [cisco-voip] Cisco VPN for voice routers...<br>To: <<a href="mailto:cenders@homesbyavi.com">cenders@homesbyavi.com</a>><br>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
Message-ID: <BLU133-W387FC2AB1DA45D10CBE644E84A0@phx.gbl><br>Content-Type: text/plain; charset="utf-8"<br><br><br><br><br>We are running 3825 with 20+ spokes on 2801 routers. Agree with Hong, it<br>is easy to handle QoS with routers. One more thing we have one SP<br>
through out the sites, therefore QoS is not an issue.<br><br>Khalid<br><br>> Date: Mon, 22 Sep 2008 14:32:30 -0500<br>> From: <a href="mailto:smetsysocsic@gmail.com">smetsysocsic@gmail.com</a><br>> To: <a href="mailto:cenders@homesbyavi.com">cenders@homesbyavi.com</a><br>
> CC: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>; <a href="mailto:Hoon.Hong@mulvannyg2.com">Hoon.Hong@mulvannyg2.com</a><br>> Subject: Re: [cisco-voip] Cisco VPN for voice routers...<br>
><br>> I forgot to add... i'd recommend configuring the remote sites as g729<br>as well.<br>><br>> -Joe C.<br>><br>> On Mon, Sep 22, 2008 at 2:21 PM, Corbett Enders<br><<a href="mailto:cenders@homesbyavi.com">cenders@homesbyavi.com</a>> wrote:<br>
> > Regarding the QoS, there is little other traffic than voice on the<br>VPN.<br>> > Besides, how do you use QoS on the Internet anyway?<br>> ><br>> ><br>> ><br>> > From: Hoon Hong [mailto:<a href="mailto:Hoon.Hong@MulvannyG2.com">Hoon.Hong@MulvannyG2.com</a>]<br>
> > Sent: Monday, September 22, 2008 12:57 PM<br>> > To: Corbett Enders; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > Subject: RE: [cisco-voip] Cisco VPN for voice routers...<br>
> ><br>> ><br>> ><br>> > Cisco for sure. Router will be even better. So you can set QOS all<br>the way<br>> > thru.<br>> ><br>> ><br>> ><br>> > Hoon Hong (? ?) | Network Engineer (CCVP, SCP, CCSA)<br>
> ><br>> > MulvannyG2 Architecture<br>> > T: 425.463.1327 (IP Phone)<br>> > C: 425.241.2646<br>> ><br>> > Hoon<br>> ><br>> > The contents of this e-mail and any attachment(s) are confidential<br>
and the<br>> > property of MulvannyG2 Architecture.<br>> ><br>> ><br>> ><br>> > From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>> > [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Corbett<br>
Enders<br>> > Sent: Monday, September 22, 2008 10:02 AM<br>> > To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > Subject: Re: [cisco-voip] Cisco VPN for voice routers...<br>
> ><br>> ><br>> ><br>> > I should add that we're currently using a Watchguard Core firewall<br>but for<br>> > some reason after a while a few of the VPNs will drop and won't<br>recreate<br>
> > unless I reboot the Cisco router. This happens to only a couple of<br>the<br>> > remote sites, not all of them. Of course, the config across all of<br>the<br>> > remote sites and VPN settings on the Watchguard's are the same<br>
(other than<br>> > their respective unique pieces).<br>> ><br>> ><br>> ><br>> > From: Corbett Enders<br>> > Sent: Monday, September 22, 2008 9:49 AM<br>> > To: '<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>'<br>
> > Subject: Cisco VPN for voice routers...<br>> ><br>> ><br>> ><br>> > We have 25 remote sites with Cisco 2801 routers for Voice. Which is<br>the best<br>> > device I should use at my head office for establishing a VPN to each<br>
of<br>> > these sites?<br>> ><br>> ><br>> ><br>> > Cisco or non-Cisco, I have no preference but of course non-cisco<br>> > interoperability is a concern as no one seems to follow the IPSEC<br>
spec 100%.<br>> ><br>> ><br>> ><br>> > Corbett Enders<br>> ><br>> > Network Manager<br>> > Homes by Avi - 2007 Canadian Builder of the Year.<br>> > Tel: (403) 536-7170<br>> > Fax: (403) 536-7171<br>
> > <a href="http://www.homesbyavi.com/" target="_blank">www.homesbyavi.com</a><br>> ><br>> > ? Please consider the environment before printing this email.<br>> ><br>> ><br>> ><br>> > _______________________________________________<br>
> > cisco-voip mailing list<br>> > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> ><br>> ><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>_________________________________________________________________<br>News, entertainment and everything you care about at Live.com. Get it<br>now!<br><a href="http://www.live.com/getstarted.aspx" target="_blank">http://www.live.com/getstarted.aspx</a><br>
-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL:<br><<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20080923/3424263c/attachment.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20080923/34242<br>
63c/attachment.html</a>><br><br>------------------------------<br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br><br>End of cisco-voip Digest, Vol 59, Issue 187<br>*******************************************<br>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br></div>