He would need to have access to the registrar rpm which is not made available anymore via the download site.
This would not be a certificate issue. If it was a certificate issue the only noticeable problem would be people cannot leave voicemail. -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! On Sep 29, 2012 6:42 AM, "George Niculae" <[email protected]> wrote: > On Sat, Sep 29, 2012 at 1:33 PM, Todd Hodgen <[email protected]> wrote: > > I haven’t dug into it yet, but will in morning. Last night I did a Yum > > Update to a site that was running on 4.4, with a Patton Gateway to PRI. > > Everything was running well, but the certificate was about to expire. > > > > > > > > Here are the steps I took – > > > > Stopped sipxecs > > > > Yum Update to get the latest patches > > > > Started sipxecs > > > > Logged in and Sent profiles for the server > > > > > > > > Did backup of system > > > > > > > > Stopped sipxecs > > > > Followed instruction from Wiki for creating a new Certificate – as this > one > > was going to run out 10/8/2012. > > > > Started sipxecs > > > > Logged in and sent profiles for the server. > > > > > > > > I tried to restart all of the phones, but only some did a restart. > > > > > > > > Otherwise, everything okay. > > > > > > > > Today, I discovered calls to the auto-attendant are processing fine. > > However, calls to DID numbers – which are all aliases on this system are > > not. Thought maybe related to certificates, so I factory reset two of > the > > phones with this issue, no joy. > > > > > > > > Have I missed an issue with the latest patches for 4.4, or is anyone else > > seeing a similar issue on 4.4 with latest patches. > > > > > > > > Yes, I know, hard to tell without a trace – I’ll get it in the morning, > but > > curious if anyone else has discovered an issue like this – possibly a new > > configuration items I am not aware of? > > > > Todd, > > there could be a problem with latest update19 - we noticed same > problem last night. Until we figure it out, do you have any mean to > downgrade sipregistrar /config to patch 18? > > George > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
