Is the /usr/bin/sipxecs-setup supposed to run the first *two* times you log
into the system?

-Bryan Anderson



On Wed, Jul 25, 2012 at 5:18 PM, Douglas Hubler <dhub...@ezuce.com> wrote:

> Restore from 4.4 *should be* foolproof.  you can restore from (almost) any
> previous version, any domain, any ip address, any FQDN.  PINs that are
> longer than 6 numbers or alphanumeric we cannot restore, but you can reset
> them upon restore.
>
> We do not preserve all data, for example, as you said, no features are
> enabled even though you may have had all sorts of roles enabled in 4.4.  In
> all cases, the data should be easily recreated.
>
> As for your issue with your polycom, we changed how NTP addresses are
> managed in the system and it's causing issues somehow.  It would be easy to
> reproduce if I could get a copy your restore file, but barring that, I'm
> going to have to study the code and see how this might happen.
>
>
> On Wed, Jul 25, 2012 at 5:55 PM, Bryan Anderson <shadow...@gmail.com>wrote:
>
>> I'll re-install and start from fresh, and compare.   I did notice in the
>> config file the sntp section reads:
>>
>>     <SNTP
>>       tcpIpApp.sntp.resyncPeriod="86400"
>>       tcpIpApp.sntp.address="0.pool.ntp.org"
>>
>>
>>
>> this is at the end of <MAC>-sipx-sip.cfg nothing after no close out or
>> anything.
>>
>> Thanks,
>>
>> -Bryan Anderson
>>
>>
>>
>>
>> On Wed, Jul 25, 2012 at 2:53 PM, Tony Graziano <
>> tgrazi...@myitdepartment.net> wrote:
>>
>>> I also wonder if the poly com and NTP issues were a byproduct of the
>>> restore. I wouldn't put much effort into that if it does not happen on
>>> fresh non-restored system.
>>> On Jul 25, 2012 5:51 PM, "Tony Graziano" <tgrazi...@myitdepartment.net>
>>> wrote:
>>>
>>>> The restore was not compatible. I am not sure how they plan to overcome
>>>> that but this has not been something I would think is implicitly supported
>>>> get. You would be better off not doing that. Instead export the 4.4 system
>>>> and remove superadmin and randomize the passwords (remove the password with
>>>> the sip domain in the export file) and make new passwords and import.
>>>> That's what I would do and have ALWAYS done unless it is the same version
>>>> to same version and same everything else.
>>>>
>>>> Standby to see what is developed for the backup from 4.4 and restore to
>>>> 4.6, I just have the indication it is done or fully tested yet.
>>>> On Jul 25, 2012 5:40 PM, "Bryan Anderson" <shadow...@gmail.com> wrote:
>>>>
>>>>> The backup was from 4.4.
>>>>>
>>>>> I have the SNTP sever set to the default under System > Date and Time.
>>>>>
>>>>> I just went to devices > phones  and clicked on the phone then went to
>>>>> the "SNTP" Link.  The url was:
>>>>>
>>>>> https://sipx.domain.net/sipxconfig/phone/EditPhone,$phone$PhoneNavigation.$setting$SettingsNavigation.settingsLink.sdirect?sp=1&sp=StcpIpApp.sntp&state:phone/EditPhone=BrO0ABXcnAAAAAQEADiRjb21tb24kQm9yZGVyABBpbml0aWFsU2Vzc2lvbklkdAANNXE2OXJyOWg4ZHZudg%3D%3D
>>>>>
>>>>>
>>>>> I received an error "An internal error has occurred. Click here to
>>>>> continue." All red text nothing else on the screen.
>>>>>
>>>>>
>>>>> I will check the jira for a polycom issue.
>>>>>
>>>>> -Bryan Anderson
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Jul 25, 2012 at 2:29 PM, Tony Graziano <
>>>>> tgrazi...@myitdepartment.net> wrote:
>>>>>
>>>>>> No real services are enabled by default. That's "normal".
>>>>>>
>>>>>> When you restored from backup did you restart the server? If the
>>>>>> backup was from a prior version also it may not work due to the way
>>>>>> passwords were stored and encrypted with the domain.
>>>>>>
>>>>>> You might check the jira for the poly com issue and open a case for
>>>>>> that.
>>>>>>
>>>>>> If it isn't picking up NTP where is the NTP? Is it enabled?
>>>>>>
>>>>>> Homer is being worked on.
>>>>>> On Jul 25, 2012 5:21 PM, "Bryan Anderson" <shadow...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I installed SipXecs 4.6.0 yesterday and have updated it using yum.
>>>>>>> Currently I am running 4.6.0. 2012-07-25EDT11:07:42
>>>>>>> ip-10-72-43-110.ec2.internal.
>>>>>>>
>>>>>>> The wiki says to send the experiences so here are mine so far:
>>>>>>>
>>>>>>> When I first installed next to nothing was enabled for services.  I
>>>>>>> guess that is to be expected?
>>>>>>>
>>>>>>> When I restored from a backup I lost access to the superadmin
>>>>>>> account and had to clear the password in the database to get back in.
>>>>>>>
>>>>>>> I receive a failed job when generating phone profiles:
>>>>>>> Projection for: 0004f22a38de
>>>>>>> 7/25/12 2:04 PM 7/25/12 2:04 PM Failed  Invocation of method
>>>>>>> 'getValue' in class
>>>>>>> org.sipfoundry.sipxconfig.setting.ConditionalSettingImpl threw exception
>>>>>>> org.springframework.dao.IncorrectResultSizeDataAccessException: 
>>>>>>> Incorrect
>>>>>>> result size: expected 1, actual 2 @ 
>>>>>>> polycom/mac-address.d/sip.cfg.vm[413,56]
>>>>>>>
>>>>>>> My phone will boot and register with the system no problem, but
>>>>>>> isn't picking up the NTP server.  I can get to IVR and make and receive
>>>>>>> call no problem.
>>>>>>>
>>>>>>> I have seen that it's stated homer is having issues.  I can get to
>>>>>>> the web interface and login without fault.  The interface look easy to 
>>>>>>> use,
>>>>>>> but I am not capturing any data into the MySQL database.  I looked at my
>>>>>>> logs and have seen the same error over and over
>>>>>>>
>>>>>>> "2012-07-25T21:17:02.562422Z":18352:NET:NOTICE:sipx.domain.net:task-140671845394176:7ff0b75fe700:sipxhomer:"StateQueueClient::signin
>>>>>>> Type=watcher SIGNIN"
>>>>>>> "2012-07-25T21:17:02.563328Z":18353:NET:ERR:sipx.domain.net:task-140671845394176:7ff0b75fe700:sipxhomer:"StateQueueClient::eventLoop
>>>>>>> Is unable to SIGN IN to SQA service"
>>>>>>>
>>>>>>> I hope some of this may be helpful.
>>>>>>>
>>>>>>> Aside from that I am enjoying what I am seeing so far and look
>>>>>>> forward to the final release.
>>>>>>>
>>>>>>>
>>>>>>> -Bryan Anderson
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> sipx-users mailing list
>>>>>>> sipx-users@list.sipfoundry.org
>>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>>>>>
>>>>>>
>>>>>> LAN/Telephony/Security and Control Systems Helpdesk:
>>>>>> Telephone: 434.984.8426
>>>>>> sip: 
>>>>>> helpdesk@voice.myitdepartment.**net<helpd...@voice.myitdepartment.net>
>>>>>>
>>>>>> Helpdesk Customers: 
>>>>>> http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
>>>>>> Blog: http://blog.myitdepartment.net
>>>>>>
>>>>>> _______________________________________________
>>>>>> sipx-users mailing list
>>>>>> sipx-users@list.sipfoundry.org
>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> sipx-users mailing list
>>>>> sipx-users@list.sipfoundry.org
>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>>>
>>>>
>>> LAN/Telephony/Security and Control Systems Helpdesk:
>>> Telephone: 434.984.8426
>>> sip: helpdesk@voice.myitdepartment.**net<helpd...@voice.myitdepartment.net>
>>>
>>> Helpdesk Customers: 
>>> http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
>>> Blog: http://blog.myitdepartment.net
>>>
>>> _______________________________________________
>>> sipx-users mailing list
>>> sipx-users@list.sipfoundry.org
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>
>>
>>
>> _______________________________________________
>> sipx-users mailing list
>> sipx-users@list.sipfoundry.org
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
>
> _______________________________________________
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to