We are trying to automate a bunch of new VG202s using auto-install provided by TFTP servers. The VGs get their configuration properly but you aren't able to telnet to them until you manually enter no for the initial configuration dialog prompt. Does anyone know how that can be automated or ignored so that the VGs can register and be accessed? Would hate to have to console into each one and type in no manually to get it to come up. Thank you!! ... View more

Hello all, I'm implementing a new dial plan for our international sites that currently aren't on +E.164 format. For China, dialing mobile numbers that are in the area don't require a zero, however if they aren't in the area they do require you to prefix a 0. They are used to having to adjust what they dial for this scenario. The carrier sends the mobile numbers calling party without a zero regardless of where they are calling from. My dilemma is in regards to redialing a missed call from a mobile number. All missed calls will now be in E.164 format without a leading zero (+861[3458]!). I am localizing the call on it's way out to the gateway via CdPTP but if for some reason that redial actually required a zero, I don't want to have them edit dial and put in a 0 after the country code (+8601[3458]). I was trying to think of way using dialpeers - to send the call to the gateway without the leading zero every time and perhaps try it not using a zero first (preference 1), and if that fails, try another dial peer that includes the zero (preference 2). The problem is that even if they prefix a 0 when they shouldn't, the call still connects but they get a message from the carrier, so as far as the router is concerned, it would most likely treat it as a successful call. It is ISDN and was wondering if you know a way using dialpeers to accomplish what I need? Is there somehow a cause code or something that if that if using that dialpeer failed, or in my scenario played a message, to try the next dialpeer and prefix a 0? Any advice is greatly appreciated! ... View more

I wanted to give everyone a heads who might be running into the issue with trying to install a subscriber fresh running 10.5(2). Only work around is to call TAC and the developers still don't have a fix for this issue. The install will get about 90% done and then throw a critical error.   Subscriber fresh installation fails with CUCM Version 10.5(2) CSCus35964   Description Symptom: Subscriber fresh installation fails with CUCM Version 10.5(2) Conditions: We will run into this case only when Pub is fresh installed and restored from old upgraded PUB CUCM. Workaround: Contact TAC Requires remote account support. Detailed steps of workaround mentioned in the enclosure Workaround.txt. ... View more