If this is happening when updating, it makes sense (to me) to grep your packages and compare that with the repo list to make sure everything:
1. Got installed (there are new packages that are installing and not updating) 2. Got updated If something didn't get installed or updated it should be noted. Then if this problem happens, a snapshot would be helpful with a JIRA issue. On Thu, Apr 22, 2010 at 2:04 PM, Todd Hodgen <thod...@verizon.net> wrote: > I can confirm that I had the same issue when I did my update to 4.2 > initially. However, I wasn't sure I had a clean system that I was > updating, > so I did not report it. > > Essentially, everything came up and was working except my trunks. I went > in > and added the branch setting - in all areas. I then noticed I didn't have > an SBC, and the drop down contained NONE if I recall correctly. It would > not allow me to add the sipxbridge, and it was not in the dropdown - only > None was in there. I confirmed that I had Sip Trunking enabled, etc. > Basically, I couldn't find a way to enable the Bridge. Out of frustration, > I reloaded from ISO, as I wasn't sure it was something I had done to the > base software of 4.0.4. > > > > -----Original Message----- > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Scott > Lawrence > Sent: Thursday, April 22, 2010 6:24 AM > To: Robert B > Cc: sipx-users@list.sipfoundry.org > Subject: Re: [sipx-users] ITSP Account setting missing in Gateway config > > On Thu, 2010-04-22 at 07:22 -0500, Robert B wrote: > > Tony, > > > > Okay -- so you're right, but here's the issue and apparently a bug... > > > > When I restored my configuration, it did not bring over the SBC Route. > > Nor, once a SIP trunk is created, can I change the SBC Route. That > > option does not appear. > > > > I have quite a few trunks configured, so re-adding them is going to be > > time consuming. It would be better to keep the route configuration when > > restored from backup. > > If you can carefully reconstruct what you did and file an issue with a > snapshot from after the upgrade and either a snapshot or a backup file > from before the upgrade, it would be helpful. > > A snapshot does not contain security-sensitive data (all the passwords > and ssl keys are removed), but the backup file does have that stuff, so > don't just post the backup - create the issue and we can arrange for > secure transfer of the 'before' data. > > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > 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 sipx-users@list.sipfoundry.org > 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/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
