<div dir="ltr">cfwdall, cfwdna, cfwdbusy CSS operate differently in CM6 than the did in CM4. In cm4, if the CSS for any of the CFWD options was set to <none> than the CM concantaned the device and line css to determine how to route the call forward. <br>
<br>however, in cm6 if you have <none> for your css you (by default) will get reorder. you will need to bulk update your CSS to properly route the forwards. there is a service param for the cfwdall that you can look into that changes the default for cfwdall - but you'd still need to bat update the cfwdbusy/cfwdna...<br>
<br><br><br><div class="gmail_quote">On Mon, Aug 25, 2008 at 3:31 PM, Scott Voll <span dir="ltr"><<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"><div>That was the command I was looking for. Thanks</div>
<div> </div>
<div>but all the number are coming up with the right Dial peer.</div>
<div> </div>
<div>I think I might have had a CSS on CFA that was causing some of the issue..... we will see.</div>
<div> </div><font color="#888888">
<div>Scott<br><br></div></font><div><div></div><div class="Wj3C7c">
<div class="gmail_quote">On Mon, Aug 25, 2008 at 12:19 PM, Joe Cisco <span dir="ltr"><<a href="mailto:smetsysocsic@gmail.com" target="_blank">smetsysocsic@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">Ok. My next obvious question, is this... does the calling search space<br>on the h323 gateway (in the GUI) have the ability to see all needed<br>
extensions?<br><br>If so, if you do a "show dialplan number XXXX" on the gateway (where<br>XXXX is an actual 4 digit extension) do you see it match the voip dial<br>peer? I'd try it several times for different extensions.<br>
<br>-Joe C.<br>
<div>
<div></div>
<div><br>On Mon, Aug 25, 2008 at 2:11 PM, Scott Voll <<a href="mailto:svoll.voip@gmail.com" target="_blank">svoll.voip@gmail.com</a>> wrote:<br>> yep<br>> destination-pattern ....<br>><br>> it worked just fine with CM 4.1. the cm 6.1 is a different IP so I just<br>
> changed the session target address.<br>><br>> Scott<br>><br>> On Mon, Aug 25, 2008 at 12:03 PM, Joe Cisco <<a href="mailto:smetsysocsic@gmail.com" target="_blank">smetsysocsic@gmail.com</a>> wrote:<br>
>><br>>> Does the VoIP dial peer include all the extensions in question?<br>
>><br>>> Example, the following voip dial peer only covers 4 digit extensions<br>>> starting with the number "4"<br>>><br>>> !<br>>> dial-peer voice 4000 voip<br>>> description 4XXX extension to publisher<br>
>> preference 1<br>>> destination-pattern 4...<br>>> progress_ind setup enable 3<br>>> progress_ind progress enable 8<br>>> voice-class h323 1<br>>> session target ipv4:<a href="http://172.16.1.10/" target="_blank">172.16.1.10</a><br>
>> dtmf-relay h245-alphanumeric<br>>> codec g711ulaw<br>>> no vad<br>>> !<br>>><br>>> -Joe C.<br>>><br>>> On Mon, Aug 25, 2008 at 1:34 PM, Scott Voll <<a href="mailto:svoll.voip@gmail.com" target="_blank">svoll.voip@gmail.com</a>> wrote:<br>
>> > no. did I need to reboot?<br>>> ><br>>> > Q931 looks normal.... but I'm not seeing the problem ones as I'm not<br>>> > sure<br>>> > when they are happening. It's not consistant.<br>
>> ><br>>> > Scott<br>>> ><br>>> ><br>>> > On Mon, Aug 25, 2008 at 11:28 AM, Ryan West <<a href="mailto:rwest@zyedge.com" target="_blank">rwest@zyedge.com</a>> wrote:<br>
>> >><br>
>> >> Debug isdn q931 to make sure that your system is generating the<br>>> >> message,<br>>> >> make sure it's actually hitting your gateway. Did you reboot your<br>>> >> router<br>
>> >> after making the change?<br>>> >><br>>> >><br>>> >><br>>> >> -ryan<br>>> >><br>>> >><br>>> >><br>>> >> From: <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a><br>
>> >> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Scott Voll<br>>> >> Sent: Monday, August 25, 2008 2:23 PM<br>
>> >> To: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
>> >> Subject: [cisco-voip] H323 to CM 6.1.2<br>>> >><br>>> >><br>>> >><br>>> >> I have a VGW (CMM) with a couple PRI's connected to my new CM 6.1.2<br>>> >> cluster.<br>
>> >><br>>> >><br>>> >><br>>> >> I am having reports of calls not going through.(your call cannot be<br>>> >> completed as dialed).<br>>> >><br>>> >><br>
>> >><br>>> >> All I did on the dial peers was change the IPV4:(new server cluster<br>>> >> IP).<br>>> >> All looks good<br>>> >><br>>> >><br>>> >><br>
>> >> is it an IOS issue or a CM issue.<br>>> >><br>>> >><br>>> >><br>>> >> I call a DID and get the message and call it again and it works. I<br>>> >> thought it was my cell phone, but I'm getting more reports of it.<br>
>> >><br>>> >><br>>> >><br>>> >> if anyone can give me a starting spot, I would like to trouble shoot<br>>> >> this.<br>>> >><br>>> >><br>
>> >><br>>> >> TIA<br>>> >><br>>> >><br>>> >><br>>> >> Scott<br>>> ><br>>> > _______________________________________________<br>>> > cisco-voip mailing list<br>
>> > <a href="mailto:cisco-voip@puck.nether.net" target="_blank">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></div></div></blockquote></div><br></div></div></div>
<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></blockquote></div><br></div>