[cisco-voip] H323 to CM 6.1.2

[Justin Steinberg]

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.

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...



On Mon, Aug 25, 2008 at 3:31 PM, Scott Voll <svoll.voip at gmail.com> wrote:

> That was the command I was looking for.  Thanks
>
> but all the number are coming up with the right Dial peer.
>
> I think I might have had a CSS on CFA that was causing some of the
> issue..... we will see.
>
> Scott
>
> On Mon, Aug 25, 2008 at 12:19 PM, Joe Cisco <smetsysocsic at gmail.com>wrote:
>
>> Ok. My next obvious question, is this... does the calling search space
>> on the h323 gateway (in the GUI) have the ability to see all needed
>> extensions?
>>
>> If so, if you do a "show dialplan number XXXX" on the gateway (where
>> XXXX is an actual 4 digit extension) do you see it match the voip dial
>> peer? I'd try it several times for different extensions.
>>
>> -Joe C.
>>
>> On Mon, Aug 25, 2008 at 2:11 PM, Scott Voll <svoll.voip at gmail.com> wrote:
>> > yep
>> > destination-pattern ....
>> >
>> > it worked just fine with CM 4.1.  the cm 6.1 is a different IP so I just
>> > changed the session target address.
>> >
>> > Scott
>> >
>> > On Mon, Aug 25, 2008 at 12:03 PM, Joe Cisco <smetsysocsic at gmail.com>
>> wrote:
>> >>
>> >> Does the VoIP dial peer include all the extensions in question?
>> >>
>> >> Example, the following voip dial peer only covers 4 digit extensions
>> >> starting with the number "4"
>> >>
>> >> !
>> >> dial-peer voice 4000 voip
>> >>  description 4XXX extension to publisher
>> >>  preference 1
>> >>  destination-pattern 4...
>> >>  progress_ind setup enable 3
>> >>  progress_ind progress enable 8
>> >>  voice-class h323 1
>> >>  session target ipv4:172.16.1.10
>> >>  dtmf-relay h245-alphanumeric
>> >>  codec g711ulaw
>> >>  no vad
>> >> !
>> >>
>> >> -Joe C.
>> >>
>> >> On Mon, Aug 25, 2008 at 1:34 PM, Scott Voll <svoll.voip at gmail.com>
>> wrote:
>> >> > no.  did I need to reboot?
>> >> >
>> >> > Q931 looks normal.... but I'm not seeing the problem ones as I'm not
>> >> > sure
>> >> > when they are happening.  It's not consistant.
>> >> >
>> >> > Scott
>> >> >
>> >> >
>> >> > On Mon, Aug 25, 2008 at 11:28 AM, Ryan West <rwest at zyedge.com>
>> wrote:
>> >> >>
>> >> >> Debug isdn q931 to make sure that your system is generating the
>> >> >> message,
>> >> >> make sure it's actually hitting your gateway.  Did you reboot your
>> >> >> router
>> >> >> after making the change?
>> >> >>
>> >> >>
>> >> >>
>> >> >> -ryan
>> >> >>
>> >> >>
>> >> >>
>> >> >> From: cisco-voip-bounces at puck.nether.net
>> >> >> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Scott Voll
>> >> >> Sent: Monday, August 25, 2008 2:23 PM
>> >> >> To: cisco-voip at puck.nether.net
>> >> >> Subject: [cisco-voip] H323 to CM 6.1.2
>> >> >>
>> >> >>
>> >> >>
>> >> >> I have a VGW (CMM) with a couple PRI's connected to my new CM 6.1.2
>> >> >> cluster.
>> >> >>
>> >> >>
>> >> >>
>> >> >> I am having reports of calls not going through.(your call cannot be
>> >> >> completed as dialed).
>> >> >>
>> >> >>
>> >> >>
>> >> >> All I did on the dial peers was change the IPV4:(new server cluster
>> >> >> IP).
>> >> >> All looks good
>> >> >>
>> >> >>
>> >> >>
>> >> >> is it an IOS issue or a CM issue.
>> >> >>
>> >> >>
>> >> >>
>> >> >> I call a DID and get the message and call it again and it works.  I
>> >> >> thought it was my cell phone, but I'm getting more reports of it.
>> >> >>
>> >> >>
>> >> >>
>> >> >> if anyone can give me a starting spot, I would like to trouble shoot
>> >> >> this.
>> >> >>
>> >> >>
>> >> >>
>> >> >> TIA
>> >> >>
>> >> >>
>> >> >>
>> >> >> Scott
>> >> >
>> >> > _______________________________________________
>> >> > cisco-voip mailing list
>> >> > cisco-voip at puck.nether.net
>> >> > https://puck.nether.net/mailman/listinfo/cisco-voip
>> >> >
>> >> >
>> >
>> >
>>
>
>
> _______________________________________________
> 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/20080825/d7fd446f/attachment.html>