4.6.0

[Bryan Anderson]

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

[Tony Graziano]

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.

Post by Bryan Anderson
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.
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.
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
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Bryan Anderson]

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

Post by Tony Graziano
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.

Post by Bryan Anderson
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.
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.
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
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Tony Graziano]

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.

Post by Bryan Anderson
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
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 <

Post by Tony Graziano
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.

Post by Bryan Anderson
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.
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.
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
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Tony Graziano]

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.

Post by Tony Graziano
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.

Post by Bryan Anderson
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
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 <

Post by Tony Graziano
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.

Post by Bryan Anderson
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.
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.
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
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Bryan Anderson]

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

Post by Tony Graziano
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.

Post by Tony Graziano
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.

Post by Bryan Anderson
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
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 <

Post by Tony Graziano
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.

Post by Bryan Anderson
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.
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.
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
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Douglas Hubler]

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.

Post by Bryan Anderson
I'll re-install and start from fresh, and compare. I did notice in the
<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 <

Post by Tony Graziano
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.

Post by Tony Graziano
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.

Post by Bryan Anderson
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
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 <

Post by Tony Graziano
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.

Post by Bryan Anderson
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.
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.
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
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Bryan Anderson]

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

-Bryan Anderson

Post by Douglas Hubler
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.

Post by Bryan Anderson
I'll re-install and start from fresh, and compare. I did notice in the
<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 <

Post by Tony Graziano
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.

Post by Tony Graziano
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.

Post by Bryan Anderson
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
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 <

Post by Tony Graziano
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.

Post by Bryan Anderson
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.
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.
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
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Douglas Hubler]

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

If sipxecs-setup is successful, it removes itself from /root/.bashrc which
is called upon login. The code to remove itself is also in ~/.bashrc.

cat >> /root/.bashrc <<EOF

/usr/bin/sipxecs-setup
# restore /root/.bashrc and /etc/issue to original states upon successful
# setup.
if [ $? == 0 ]; then
sed -i '/^\/usr\/bin\/sipxecs-setup$/,//d' /root/.bashrc
sed -i '/^====/,//d' /etc/issue
fi
EOF


It's always worked for me, but it always works for the developer. If you
see anything that would make this not work on you machine, maybe we can fix
this.

[Bryan Anderson]

I guess third time's the charm??? I setup a new vm and setup from the same
image. This time it only asked once.

-Bryan Anderson

Post by Douglas Hubler

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

If sipxecs-setup is successful, it removes itself from /root/.bashrc which
is called upon login. The code to remove itself is also in ~/.bashrc.
cat >> /root/.bashrc <<EOF
/usr/bin/sipxecs-setup
# restore /root/.bashrc and /etc/issue to original states upon successful
# setup.
if [ $? == 0 ]; then
sed -i '/^\/usr\/bin\/sipxecs-setup$/,//d' /root/.bashrc
sed -i '/^====/,//d' /etc/issue
fi
EOF
It's always worked for me, but it always works for the developer. If you
see anything that would make this not work on you machine, maybe we can fix
this.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Douglas Hubler]

Let's keep an eye on it. It is harmless to run multiple times. Btw I have
a fix for the import and polycom issue, just testing it.I'll respond later

Post by Bryan Anderson
I guess third time's the charm??? I setup a new vm and setup from the
same image. This time it only asked once.
-Bryan Anderson

Post by Douglas Hubler

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

If sipxecs-setup is successful, it removes itself from /root/.bashrc
which is called upon login. The code to remove itself is also in
~/.bashrc.
cat >> /root/.bashrc <<EOF
/usr/bin/sipxecs-setup
# restore /root/.bashrc and /etc/issue to original states upon successful
# setup.
if [ $? == 0 ]; then
sed -i '/^\/usr\/bin\/sipxecs-setup$/,//d' /root/.bashrc
sed -i '/^====/,//d' /etc/issue
fi
EOF
It's always worked for me, but it always works for the developer. If you
see anything that would make this not work on you machine, maybe we can fix
this.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Bryan Anderson]

Ok, Thanks for the update on the Polycom, now I have something regarding
updating DNS records/configuration.

I had changed the "Domain Name" under system > domain. It updated
/etc/named.conf with the new name including the name of the zone file (I
went from domain.net, to sipx.domain.net), but did not actually rename the
zone file.


-Bryan Anderson

Post by Douglas Hubler
Let's keep an eye on it. It is harmless to run multiple times. Btw I have
a fix for the import and polycom issue, just testing it.I'll respond later

Post by Bryan Anderson
I guess third time's the charm??? I setup a new vm and setup from the
same image. This time it only asked once.
-Bryan Anderson

Post by Douglas Hubler

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

If sipxecs-setup is successful, it removes itself from /root/.bashrc
which is called upon login. The code to remove itself is also in
~/.bashrc.
cat >> /root/.bashrc <<EOF
/usr/bin/sipxecs-setup
# restore /root/.bashrc and /etc/issue to original states upon successful
# setup.
if [ $? == 0 ]; then
sed -i '/^\/usr\/bin\/sipxecs-setup$/,//d' /root/.bashrc
sed -i '/^====/,//d' /etc/issue
fi
EOF
It's always worked for me, but it always works for the developer. If
you see anything that would make this not work on you machine, maybe we can
fix this.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Michael Picher]

The file name itself doesn't matter... The config statements inside the
zone file and the named.conf file matter.

It may of course confuse some.

Post by Bryan Anderson
Ok, Thanks for the update on the Polycom, now I have something regarding
updating DNS records/configuration.
I had changed the "Domain Name" under system > domain. It updated
/etc/named.conf with the new name including the name of the zone file (I
went from domain.net, to sipx.domain.net), but did not actually rename
the zone file.
-Bryan Anderson

Post by Douglas Hubler
Let's keep an eye on it. It is harmless to run multiple times. Btw I
have a fix for the import and polycom issue, just testing it.I'll respond
later

Post by Bryan Anderson
I guess third time's the charm??? I setup a new vm and setup from the
same image. This time it only asked once.
-Bryan Anderson

Post by Douglas Hubler

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

If sipxecs-setup is successful, it removes itself from /root/.bashrc
which is called upon login. The code to remove itself is also in
~/.bashrc.
cat >> /root/.bashrc <<EOF
/usr/bin/sipxecs-setup
# restore /root/.bashrc and /etc/issue to original states upon successful
# setup.
if [ $? == 0 ]; then
sed -i '/^\/usr\/bin\/sipxecs-setup$/,//d' /root/.bashrc
sed -i '/^====/,//d' /etc/issue
fi
EOF
It's always worked for me, but it always works for the developer. If
you see anything that would make this not work on you machine, maybe we can
fix this.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Tony Graziano]

Since I am confused, let's ask this:

Since one would assume the zone file name should equal the domain name and
it does not, the truer test would be if dig commands (or nslookup) from
another device on the network using the sipx server as the dns server
return the proper records for the "new" domain name.

It also begs to ask the question about DNS management, which would be "why
doesn't the dns zone name change to reflect the correct domain name". These
are two separate questions.

Can you do a dig or nslookup and specify your sipx server and see if it
resolves srv records for the new domain properly and post back? If so,
that's good, and it leaves us with a wiki type of entry or a jira to
correct the zone file name in the event of a domain rename.

Post by Michael Picher
The file name itself doesn't matter... The config statements inside the
zone file and the named.conf file matter.
It may of course confuse some.

Post by Bryan Anderson
Ok, Thanks for the update on the Polycom, now I have something regarding
updating DNS records/configuration.
I had changed the "Domain Name" under system > domain. It updated
/etc/named.conf with the new name including the name of the zone file (I
went from domain.net, to sipx.domain.net), but did not actually rename
the zone file.
-Bryan Anderson

Post by Douglas Hubler
Let's keep an eye on it. It is harmless to run multiple times. Btw I
have a fix for the import and polycom issue, just testing it.I'll respond
later

Post by Bryan Anderson
I guess third time's the charm??? I setup a new vm and setup from the
same image. This time it only asked once.
-Bryan Anderson

Post by Douglas Hubler

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

If sipxecs-setup is successful, it removes itself from /root/.bashrc
which is called upon login. The code to remove itself is also in
~/.bashrc.
cat >> /root/.bashrc <<EOF
/usr/bin/sipxecs-setup
# restore /root/.bashrc and /etc/issue to original states upon successful
# setup.
if [ $? == 0 ]; then
sed -i '/^\/usr\/bin\/sipxecs-setup$/,//d' /root/.bashrc
sed -i '/^====/,//d' /etc/issue
fi
EOF
It's always worked for me, but it always works for the developer. If
you see anything that would make this not work on you machine, maybe we can
fix this.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
sip: ***@voice.myitdepartment.net
Fax: [phone]
~~~~~~~~~~~~~~~~~~
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!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>

[Douglas Hubler]

Post by Bryan Anderson
Ok, Thanks for the update on the Polycom, now I have something regarding
updating DNS records/configuration.
I had changed the "Domain Name" under system > domain. It updated
/etc/named.conf with the new name including the name of the zone file (I
went from domain.net, to sipx.domain.net), but did not actually rename the
zone file.

I'm glad you brought this up. After working on and testing domain
name change from sipxecs-setup script, my new recommendation for this
is we remove the ability to change the domain name, primary host IP
address and primary host FQDN from the UI and require users to change
those values by rerunning sipxecs-setup. All of those values, the
sipxconfig ui simply cannot work w/o restarting sipxconfig or even
restarting the network.

[Tony Graziano]

I think that makes it all fixed!

Post by Douglas Hubler

Post by Bryan Anderson
Ok, Thanks for the update on the Polycom, now I have something regarding
updating DNS records/configuration.
I had changed the "Domain Name" under system > domain. It updated
/etc/named.conf with the new name including the name of the zone file (I
went from domain.net, to sipx.domain.net), but did not actually rename

the

Post by Bryan Anderson
zone file.

I'm glad you brought this up. After working on and testing domain
name change from sipxecs-setup script, my new recommendation for this
is we remove the ability to change the domain name, primary host IP
address and primary host FQDN from the UI and require users to change
those values by rerunning sipxecs-setup. All of those values, the
sipxconfig ui simply cannot work w/o restarting sipxconfig or even
restarting the network.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Michael Picher]

i would probably be good to make it not quite so easy to just change the
domain name.

Kind of like why upgrade is not in the gui anymore...

Post by Tony Graziano
I think that makes it all fixed!

Post by Douglas Hubler

Post by Bryan Anderson
Ok, Thanks for the update on the Polycom, now I have something regarding
updating DNS records/configuration.
I had changed the "Domain Name" under system > domain. It updated
/etc/named.conf with the new name including the name of the zone file (I
went from domain.net, to sipx.domain.net), but did not actually rename

the

Post by Bryan Anderson
zone file.

I'm glad you brought this up. After working on and testing domain
name change from sipxecs-setup script, my new recommendation for this
is we remove the ability to change the domain name, primary host IP
address and primary host FQDN from the UI and require users to change
those values by rerunning sipxecs-setup. All of those values, the
sipxconfig ui simply cannot work w/o restarting sipxconfig or even
restarting the network.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

--
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
www.ezuce.com

------------------------------------------------------------------------------------------------------------
There are 10 kinds of people in the world, those who understand binary and
those who don't.

[Douglas Hubler]

Post by Michael Picher
i would probably be good to make it not quite so easy to just change the
domain name.

y, another good reason.

here's the issue
http://track.sipfoundry.org/browse/XX-10327

[Bryan Anderson]

@Michael - The file name doesn't matter but it updated the config file and
so the file named looked for didn't exist.
@Tony - Digging didn't work. That's when I discovered named didn't load
the file and why.

@All - yes I like the idea of removing those from the UI (I am embarrassed
to admit that I had never thought of rerunning the setup script in the
past. That may help with something else I am working on in 4.4)


Thank you,

-Bryan Anderson

Post by Douglas Hubler

Post by Michael Picher
i would probably be good to make it not quite so easy to just change the
domain name.

y, another good reason.
here's the issue
http://track.sipfoundry.org/browse/XX-10327
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Douglas Hubler]

Post by Bryan Anderson
@All - yes I like the idea of removing those from the UI (I am embarrassed
to admit that I had never thought of rerunning the setup script in the past.
That may help with something else I am working on in 4.4)

re: 4.4 - be warned changing domain name, ip address or host name in
4.4 has very limited success and most would say not to attempt it.

[Bryan Anderson]

Ok, I had noticed that with the GUI but hoped the setup script would fix
that. Thanks.

Any update with the polycom? The phone works without the restore. Haven't
tried the restore again yet. (Right now I am moving an office between
floors.)

-Bryan Anderson

Post by Bryan Anderson

Post by Bryan Anderson
@All - yes I like the idea of removing those from the UI (I am

embarrassed

Post by Bryan Anderson
to admit that I had never thought of rerunning the setup script in the

past.

Post by Bryan Anderson
That may help with something else I am working on in 4.4)

re: 4.4 - be warned changing domain name, ip address or host name in
4.4 has very limited success and most would say not to attempt it.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Douglas Hubler]

Post by Bryan Anderson
Ok, I had noticed that with the GUI but hoped the setup script would fix
that. Thanks.

I got caught-up w/something but you can fix the system with

psql -U postgres SIPXCONFIG -c 'delete from timezone where timezone_id > 1'

[Bryan Anderson]

Not a problem. I'll run it after the move here is done.

Thanks,
-Bryan Anderson

Post by Douglas Hubler

Post by Bryan Anderson
Ok, I had noticed that with the GUI but hoped the setup script would fix
that. Thanks.

I got caught-up w/something but you can fix the system with
psql -U postgres SIPXCONFIG -c 'delete from timezone where timezone_id > 1'
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Bryan Anderson]

Worked like a charm. As always.

-Bryan Anderson

Post by Bryan Anderson
Not a problem. I'll run it after the move here is done.
Thanks,
-Bryan Anderson

Post by Douglas Hubler

Post by Bryan Anderson
Ok, I had noticed that with the GUI but hoped the setup script would fix
that. Thanks.

I got caught-up w/something but you can fix the system with
psql -U postgres SIPXCONFIG -c 'delete from timezone where timezone_id

Post by Bryan Anderson
1'

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/