Discussion:
Lastest Patches and Alias
Todd Hodgen
2012-09-29 10:33:58 UTC
Permalink
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?
George Niculae
2012-09-29 10:42:34 UTC
Permalink
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
Tony Graziano
2012-09-29 10:53:12 UTC
Permalink
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: ***@voice.myitdepartment.net
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!
Post by George Niculae
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Todd Hodgen
2012-09-29 19:37:38 UTC
Permalink
Sorry I don't.

This is unfortunate, as it creates service issues for this site.

This brings up a concern with this patching process that is being used.
Yum update pulls in all of the patches, and has the potential of bringing in
patches that are not fully vetted and regression tested to working sites.

I wish there was a different method of ensuring you know exactly what
patches you are putting into a system, along with a method of removing them
should there be an issue.



-----Original Message-----
From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of George Niculae
Sent: Saturday, September 29, 2012 3:43 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Post by Todd Hodgen
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.
Post by Todd Hodgen
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
George Niculae
2012-09-29 19:49:15 UTC
Permalink
Todd,

you should yum update sipxregistry and sipxconfig from here for the
moment, they contain changes reverted:

http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/

George
Post by Todd Hodgen
Sorry I don't.
This is unfortunate, as it creates service issues for this site.
This brings up a concern with this patching process that is being used.
Yum update pulls in all of the patches, and has the potential of bringing in
patches that are not fully vetted and regression tested to working sites.
I wish there was a different method of ensuring you know exactly what
patches you are putting into a system, along with a method of removing them
should there be an issue.
-----Original Message-----
Sent: Saturday, September 29, 2012 3:43 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Post by Todd Hodgen
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.
Post by Todd Hodgen
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Todd Hodgen
2012-09-29 19:54:35 UTC
Permalink
Thanks George, I'll give it a try.

-----Original Message-----
From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of George Niculae
Sent: Saturday, September 29, 2012 12:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias

Todd,

you should yum update sipxregistry and sipxconfig from here for the moment,
they contain changes reverted:

http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/

George
Post by Todd Hodgen
Sorry I don't.
This is unfortunate, as it creates service issues for this site.
This brings up a concern with this patching process that is being used.
Yum update pulls in all of the patches, and has the potential of
bringing in patches that are not fully vetted and regression tested to
working sites.
Post by Todd Hodgen
I wish there was a different method of ensuring you know exactly what
patches you are putting into a system, along with a method of removing
them should there be an issue.
-----Original Message-----
Sent: Saturday, September 29, 2012 3:43 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Post by Todd Hodgen
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.
Post by Todd Hodgen
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Gerald Drouillard
2012-09-29 21:09:53 UTC
Permalink
Post by George Niculae
Todd,
you should yum update sipxregistry and sipxconfig from here for the
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/
George
We have an install with #19 and their ACD's are not going to overflow
for outside calls when there is at least one agent signed in and does
not answer. Inside calls work properly and also when there are no
agents signed in.

I also tried with the sipxregistry and sixconfig from the above link.
--
Regards
--------------------------------------
Gerald Drouillard
Technology Architect
Drouillard & Associates, Inc.
http://www.Drouillard.biz
George Niculae
2012-09-29 22:13:27 UTC
Permalink
Post by Gerald Drouillard
Post by George Niculae
Todd,
you should yum update sipxregistry and sipxconfig from here for the
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/
George
We have an install with #19 and their ACD's are not going to overflow
for outside calls when there is at least one agent signed in and does
not answer. Inside calls work properly and also when there are no
agents signed in.
I also tried with the sipxregistry and sixconfig from the above link.
I don't think it will help as the issue Todd mention was introduced in
patch18 and you might see something from an older update

George
Post by Gerald Drouillard
--
Regards
--------------------------------------
Gerald Drouillard
Technology Architect
Drouillard & Associates, Inc.
http://www.Drouillard.biz
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Todd Hodgen
2012-09-29 21:18:13 UTC
Permalink
This might be a problem, as I believe the site is a 32-bit installation.

-----Original Message-----
From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of George Niculae
Sent: Saturday, September 29, 2012 12:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias

Todd,

you should yum update sipxregistry and sipxconfig from here for the moment,
they contain changes reverted:

http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/

George
Post by Todd Hodgen
Sorry I don't.
This is unfortunate, as it creates service issues for this site.
This brings up a concern with this patching process that is being used.
Yum update pulls in all of the patches, and has the potential of
bringing in patches that are not fully vetted and regression tested to
working sites.
Post by Todd Hodgen
I wish there was a different method of ensuring you know exactly what
patches you are putting into a system, along with a method of removing
them should there be an issue.
-----Original Message-----
Sent: Saturday, September 29, 2012 3:43 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Post by Todd Hodgen
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.
Post by Todd Hodgen
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
George Niculae
2012-09-29 21:57:08 UTC
Permalink
Ah, you should try from here

http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/i386/

George
Post by Todd Hodgen
This might be a problem, as I believe the site is a 32-bit installation.
-----Original Message-----
Sent: Saturday, September 29, 2012 12:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Todd,
you should yum update sipxregistry and sipxconfig from here for the moment,
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/
George
Post by Todd Hodgen
Sorry I don't.
This is unfortunate, as it creates service issues for this site.
This brings up a concern with this patching process that is being used.
Yum update pulls in all of the patches, and has the potential of
bringing in patches that are not fully vetted and regression tested to
working sites.
Post by Todd Hodgen
I wish there was a different method of ensuring you know exactly what
patches you are putting into a system, along with a method of removing
them should there be an issue.
-----Original Message-----
Sent: Saturday, September 29, 2012 3:43 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Post by Todd Hodgen
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.
Post by Todd Hodgen
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
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/
Todd Hodgen
2012-09-29 22:03:36 UTC
Permalink
Thanks George.



so from this directory I would just do a yum update of those two files then?



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of George Niculae
Sent: Saturday, September 29, 2012 2:57 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias



Ah, you should try from here

http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/i386/

George
Post by Todd Hodgen
This might be a problem, as I believe the site is a 32-bit installation.
-----Original Message-----
Sent: Saturday, September 29, 2012 12:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Todd,
you should yum update sipxregistry and sipxconfig from here for the moment,
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/
George
Post by Todd Hodgen
Sorry I don't.
This is unfortunate, as it creates service issues for this site.
This brings up a concern with this patching process that is being used.
Yum update pulls in all of the patches, and has the potential of
bringing in patches that are not fully vetted and regression tested to
working sites.
Post by Todd Hodgen
I wish there was a different method of ensuring you know exactly what
patches you are putting into a system, along with a method of removing
them should there be an issue.
-----Original Message-----
Sent: Saturday, September 29, 2012 3:43 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Post by Todd Hodgen
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.
Post by Todd Hodgen
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
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/
George Niculae
2012-09-29 22:11:48 UTC
Permalink
Yes, just sipxregistry and sipxconfig rpms

George
Post by Todd Hodgen
Thanks George.
so from this directory I would just do a yum update of those two files then?
Sent: Saturday, September 29, 2012 2:57 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Ah, you should try from here
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/i386/
George
Post by Todd Hodgen
This might be a problem, as I believe the site is a 32-bit installation.
-----Original Message-----
Sent: Saturday, September 29, 2012 12:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Todd,
you should yum update sipxregistry and sipxconfig from here for the moment,
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/
George
Post by Todd Hodgen
Sorry I don't.
This is unfortunate, as it creates service issues for this site.
This brings up a concern with this patching process that is being used.
Yum update pulls in all of the patches, and has the potential of
bringing in patches that are not fully vetted and regression tested to
working sites.
Post by Todd Hodgen
I wish there was a different method of ensuring you know exactly what
patches you are putting into a system, along with a method of removing
them should there be an issue.
-----Original Message-----
Sent: Saturday, September 29, 2012 3:43 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Post by Todd Hodgen
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.
Post by Todd Hodgen
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
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/
Todd Hodgen
2012-10-02 00:46:48 UTC
Permalink
George, seeing an error - Config error: file contains no section headers

File: file://///etc/yum.repos.d/sipxecs.repo
<file:///\\etc\yum.repos.d\sipxecs.repo> , line: 1



Any ideas?

Did a yum clean all with not improvements.



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of George Niculae
Sent: Saturday, September 29, 2012 3:12 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias



Yes, just sipxregistry and sipxconfig rpms

George
Post by Todd Hodgen
Thanks George.
so from this directory I would just do a yum update of those two files then?
Sent: Saturday, September 29, 2012 2:57 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Ah, you should try from here
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/i386/
George
Post by Todd Hodgen
This might be a problem, as I believe the site is a 32-bit installation.
-----Original Message-----
Sent: Saturday, September 29, 2012 12:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Todd,
you should yum update sipxregistry and sipxconfig from here for the moment,
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/
George
Post by Todd Hodgen
Sorry I don't.
This is unfortunate, as it creates service issues for this site.
This brings up a concern with this patching process that is being used.
Yum update pulls in all of the patches, and has the potential of
bringing in patches that are not fully vetted and regression tested to
working sites.
Post by Todd Hodgen
I wish there was a different method of ensuring you know exactly what
patches you are putting into a system, along with a method of removing
them should there be an issue.
-----Original Message-----
Sent: Saturday, September 29, 2012 3:43 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Post by Todd Hodgen
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.
Post by Todd Hodgen
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
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/
Todd Hodgen
2012-10-02 00:59:17 UTC
Permalink
No expert here, but from what I see, the doctype is missing the \ just
before the quote. Guess it isn't the problem, when I add it, it returns
same error with \\ instead of none on the error.



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Todd Hodgen
Sent: Monday, October 01, 2012 5:47 PM
To: 'Discussion list for users of sipXecs software'
Subject: Re: [sipx-users] Lastest Patches and Alias



George, seeing an error - Config error: file contains no section headers

File: file://///etc/yum.repos.d/sipxecs.repo
<file:///\\etc\yum.repos.d\sipxecs.repo> , line: 1



Any ideas?

Did a yum clean all with not improvements.



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of George Niculae
Sent: Saturday, September 29, 2012 3:12 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias



Yes, just sipxregistry and sipxconfig rpms

George
Post by Todd Hodgen
Thanks George.
so from this directory I would just do a yum update of those two files then?
Sent: Saturday, September 29, 2012 2:57 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Ah, you should try from here
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/i386/
George
Post by Todd Hodgen
This might be a problem, as I believe the site is a 32-bit installation.
-----Original Message-----
Sent: Saturday, September 29, 2012 12:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Todd,
you should yum update sipxregistry and sipxconfig from here for the moment,
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/
George
Post by Todd Hodgen
Sorry I don't.
This is unfortunate, as it creates service issues for this site.
This brings up a concern with this patching process that is being used.
Yum update pulls in all of the patches, and has the potential of
bringing in patches that are not fully vetted and regression tested to
working sites.
Post by Todd Hodgen
I wish there was a different method of ensuring you know exactly what
patches you are putting into a system, along with a method of removing
them should there be an issue.
-----Original Message-----
Sent: Saturday, September 29, 2012 3:43 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Post by Todd Hodgen
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.
Post by Todd Hodgen
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
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/
t***@frontier.com
2012-10-02 03:40:18 UTC
Permalink
Okay, resolved this issue via modifying the sipxecs.repo file temporarily.  Updated sipxconfig and sipxregister and problem with DID calls resolved.
 
Thanks George for the fast resolution to this issue!


________________________________
From: Todd Hodgen <***@frontier.com>
To: 'Discussion list for users of sipXecs software' <sipx-***@list.sipfoundry.org>
Sent: Monday, October 1, 2012 5:59 PM
Subject: Re: [sipx-users] Lastest Patches and Alias


No expert here, but from what I see, the doctype is missing the \ just before the quote.  Guess it isn’t the problem, when I add it, it returns same error with \\ instead of none on the error.
 
From:sipx-users-***@list.sipfoundry.org [mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Todd Hodgen
Sent: Monday, October 01, 2012 5:47 PM
To: 'Discussion list for users of sipXecs software'
Subject: Re: [sipx-users] Lastest Patches and Alias
 
George,  seeing an error – Config error: file contains no section headers
File: file://///etc/yum.repos.d/sipxecs.repo, line: 1
 
Any ideas?
Did a yum clean all with not improvements.
 
From:sipx-users-***@list.sipfoundry.org [mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of George Niculae
Sent: Saturday, September 29, 2012 3:12 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
 
Yes, just sipxregistry and sipxconfig rpms
George
Thanks George. 
 
so from this directory I would just do a yum update of those two files then?
 
Sent: Saturday, September 29, 2012 2:57 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
 
Ah, you should try from here
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/i386/
George
Post by Todd Hodgen
This might be a problem, as I believe the site is a 32-bit installation.
-----Original Message-----
Sent: Saturday, September 29, 2012 12:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
Todd,
you should yum update sipxregistry and sipxconfig from here for the moment,
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/CentOS_5/x86_64/
George
Post by Todd Hodgen
Sorry I don't.
This is unfortunate, as it creates service issues for this site.
This brings up a concern with this patching process that is being used.
Yum update pulls in all of the patches, and has the potential of
bringing in patches that are not fully vetted and regression tested to
working sites.
Post by Todd Hodgen
I wish there was a different method of ensuring you know exactly what
patches you are putting into a system, along with a method of removing
them should there be an issue.
-----Original Message-----
Sent: Saturday, September 29, 2012 3:43 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Lastest Patches and Alias
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
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/
Loading...