I've done some pretty extensive testing with 5.8 and 4.2 and I haven't seen any issues yet. I'm going to do a mock upgrade to 4.2 on some test servers and see if I have any issues with 5.8 before I actually do my update.
I'll let you know how it goes. Josh Patten Assistant Network Administrator Brazos County IT Dept. (979) 361-4676 On 5/14/2010 5:19 PM, Tony Graziano wrote: > I'm not making this stuff up though. > ============================ > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > ----- Original Message ----- > From: [email protected] > <[email protected]> > Cc: [email protected]<[email protected]> > Sent: Fri May 14 18:17:34 2010 > Subject: Re: [sipx-users] sipXecs 4.2 voicemail allows only 10 seconds of > recording before disconnecting > > I don't really see anything in the tracker blacklisting 5.8 > > I did search for 5.8 in JIRA and nothing really came up > > Josh Patten > Assistant Network Administrator > Brazos County IT Dept. > (979) 361-4676 > > > On 5/14/2010 5:13 PM, Tony Graziano wrote: > >> The polycom issue is different. If the remote phone is on a connection >> that >> is not connected to a fast enough network, it does that. >> >> I have a 512k bridge for a small satellite location. Just two phones on >> it, >> nothing else. As soon as I updated to 3.2.3 it had that problem. >> >> I never did anything to update those phones other than activate the >> upload. >> When I activated it, all phones rebooted. That sucked. >> ============================ >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> Fax: 434.984.8431 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> Fax: 434.984.8427 >> >> Helpdesk Contract Customers: >> http://www.myitdepartment.net/gethelp/ >> >> ----- Original Message ----- >> From: [email protected] >> <[email protected]> >> To: [email protected]<[email protected]> >> Sent: Fri May 14 18:09:37 2010 >> Subject: Re: [sipx-users] sipXecs 4.2 voicemail allows only 10 seconds of >> recording before disconnecting >> >> Also, I ran tests on the community opensuse-build-service CentOS 5 64 >> bit version and I didn't have any problem leaving voicemails 2 or 3 >> minutes long. I also didn't see the ring-once-then-goto-voicemail >> polycom issue others were experiencing either. >> >> Josh Patten >> Assistant Network Administrator >> Brazos County IT Dept. >> (979) 361-4676 >> >> >> On 5/14/2010 5:08 PM, Josh Patten wrote: >> >> >>> On 4.0.4 at least >>> >>> and not managed by sipX >>> >>> Josh Patten >>> Assistant Network Administrator >>> Brazos County IT Dept. >>> (979) 361-4676 >>> >>> >>> On 5/14/2010 5:07 PM, Josh Patten wrote: >>> >>> >>> >>>> I run 5.8 on my mediant 1000 with no problems. >>>> >>>> Josh Patten >>>> Assistant Network Administrator >>>> Brazos County IT Dept. >>>> (979) 361-4676 >>>> >>>> >>>> On 5/14/2010 5:07 PM, Tony Graziano wrote: >>>> >>>> >>>> >>>> >>>>> 5.6 good. 5.8 bad. >>>>> >>>>> I didn't know anyone ran 5.8 with sipx with huge success. Weren't there >>>>> tracker items on that? >>>>> ============================ >>>>> Tony Graziano, Manager >>>>> Telephone: 434.984.8430 >>>>> Fax: 434.984.8431 >>>>> >>>>> Email: [email protected] >>>>> >>>>> LAN/Telephony/Security and Control Systems Helpdesk: >>>>> Telephone: 434.984.8426 >>>>> Fax: 434.984.8427 >>>>> >>>>> Helpdesk Contract Customers: >>>>> http://www.myitdepartment.net/gethelp/ >>>>> >>>>> ----- Original Message ----- >>>>> From: [email protected] >>>>> <[email protected]> >>>>> To: Josh Patten<[email protected]> >>>>> Cc: [email protected]<[email protected]> >>>>> Sent: Fri May 14 17:46:00 2010 >>>>> Subject: Re: [sipx-users] sipXecs 4.2 voicemail allows only 10 seconds >>>>> of >>>>> recording before disconnecting >>>>> >>>>> On 10-05-14 9:25 AM, Josh Patten wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> Did you ever find a fix to this? I'm curious if so because I will be >>>>>> updating to 4.2 tonight (I use audiocodes gateways) >>>>>> and I was hoping I would be able to fix this before it was ever a >>>>>> problem. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> I now see the following errors. >>>>> After 10 seconds, the AudioCodes is reporting: >>>>> >>>>> FXO Release Line >>>>> Guard_Time_Timer_Expired_EV >>>>> >>>>> On my second test, I saw this: >>>>> >>>>> RELEASE_BECAUSE_IP_TIMER_EXPIRED_EV >>>>> >>>>> Since I didn't want to take the chance of upgrading the firmware on my >>>>> AudioCodes MP-118 FXO >>>>> from 5.2 to 5.6 without a fallback, I configured a gateway account for >>>>> VOIP.MS on Monday. >>>>> I couldn't get the account to register and haven't had a chance to >>>>> report the details yet. >>>>> >>>>> This morning we had a "power event" and one of my 2 6KVA UPS had bad >>>>> batteries >>>>> so half my servers shut down (all the ones with a single power supply >>>>> plugged into the bad UPS). >>>>> When the AudioCodes came back up, the boss placed an outbound call to >>>>> Houston for a conference >>>>> attendee who couldn't call in. They used this line for about 2 hours. >>>>> >>>>> When the conference ended, I power cycled the AudioCodes, and lost all >>>>> contact with it. >>>>> I took it to my supplier who recovered the device by installing the 5.8 >>>>> firmware. >>>>> My original configuration was intact. I realized why it stopped >>>>> functioning - >>>>> it was configured ith the IP addresses of my backup sipXecs server. I >>>>> hadn't burned the flash >>>>> after cutting over to my new sipXecs 4.2 server. >>>>> >>>>> So I have a PSTN connection again. >>>>> Voicemail still disconnects after 10 seconds. >>>>> I made the following 2 changes to look like the configuration defaults >>>>> in sipXecs for AudioCodes: >>>>> Subscription Mode and Authentication Mode - changed "per Endpoint" to >>>>> "per Gateway" >>>>> Alas, to no avail. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> _______________________________________________ >>>> 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/ >>> >>> >>> >> _______________________________________________ >> 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/ > _______________________________________________ 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/
