On Mon, 11 Jan 2010 22:14:14 -0800, Todd Hodgen wrote: > According to the Audio Codes documention, 0 & D both specify Extended > Superframe with CRC6. Are you sure that was your problem?
Yes, quite sure, but, in our case at least, because it would not even allow a burn. When I take out the D, I can then burn the config otherwise, it won't even allow me to set up the PRI. I found this on the 3com site which was not exactly our error but using the solution helped and things startted to work once more. Problem Description : After replacing a gateway CPU module and attempting to import an INI file into a gateway, the import may fail with the error "The parameters validation check has failed! The device will not perform a reset until the parameters are reconfigured. RECOV:PSTN Trunk Validation Check failed. Framing method 44 is not valid (Line type is E1) [Trunk: 0 Bchannel: -1 ConnID: -1] [Code: 23014] [Time: 18:1:1]" or something similar. Product Model # : 3CRVG71225-07 3CRVG60005-06 Software / Firmware version : 5.20AEB.003.004 Fact : Replaced gateway CPU module Recent Changes : Gateway CPU module was recently replaced Cause : A parameter in the INI file is invalid and doesn't match the current parameters in memory on the gateway. Fix : 1. Edit the INI file with a text editor such as WordPad. Search for the text FramingMethod=D and change it to FramingMethod=0 2. Save your changes and import the INI file into the gateway again. The gateway should accept the file and reset, using the values in the INI file. Mike > FramingMethod > (Trunk Settings>Framing > Method) > For T1 > 0 or D = Extended super frame with CRC6 (default) > 1 or B = Super frame D4, F12 (12-Frame multiframe) > A = F4 (4-Frame multiframe) > C = Extended super frame without CRC6 > F = J1 - Japan (ESF with CRC6 and JT) > Selects the framing method to be used for E1/T1 spans. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > [email protected] > Sent: Monday, January 11, 2010 9:51 PM > To: sipx-users > Subject: [sipx-users] sipx ini ERROR for mediant 2000 > > Just spent a week in hell trying to figure this one out so wanted to share > it. > > Weird problems started to arrise after I made a small config change in sipx, > then uploaded the new ini file to my mediant. Quite suddenly, outgoing calls > worked fine, incoming calls no longer worked. Later down the road, incoming > calls work fine but outgoing calls don't work at all. Part of the problem > was the following but with a mix of the other work I was doing. Since I > didn't know about this problem, it created a much bigger mess. > > The following is the Trunk section of the ini file which sipx generates. > There is an error in the generated file for option FramingMethod. > > [Trunk_0] > ProtocolType_0=10 > ClockMaster_0=0 > LineCode_0=0 > FramingMethod_0=0 > > Sipx creates this option as FramingMethod_0=D where 0 needs to be and this > breaks the trunk in some not so obvious ways. > I'm not 100% sure if this error comes from sipx itself or some default > config that it uses to generate the file so wanted to mention it so that > someone who is more aware can know about it. > > Mike > > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
