OVHcloud Web Hosting Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
FS#6023 —SIP Proxy
Scheduled Maintenance
Report for Web Cloud
Completed
We will put in production our SIP Proxy on Tuesday, 8th of November 2011 during the morning (around 6h00).
The purpose of this proxy is to improve the security of our infrastructure.
It will be the best parade at the hands of the bad SIP behaviours which can
happen on the internet.
It will help provide new services:
- The secure of SIP accounts (restrictions by IP for example),
- a better compatibility of the MWI service (indication message on the answering machine),
- the SMS,
- and others
This proxy is on bêta since a few months. We were able to test it
in all ways.
The results are very good with a a few thousand people of subscribers. All the possible tests
were done. Now, there still a single test:
the behaviour of the proxy in the real world.
The accounts of our Belgium, German, English and Spanish subsidiaries already use this proxy from the very beginning.
The introduction of the proxy will be totally transparent. No manipulation is necessary from your side.
Update(s):
Date: 2012-03-01 01:27:56 UTC
The proxy has been deployed on the new domain: sip.ovh.fr
Current lines can be migrated via manager.
Date: 2011-11-29 11:42:04 UTC
The update of the proxy was done correctly.
We check the corrections done in order to put it in production in the next days.
Date: 2011-11-29 11:40:17 UTC
Our constructor did provide us the last corrective patches.
We are installing them on the proxy.
Date: 2011-11-16 23:25:20 UTC
The proxy implementation hasn't been performed correctly. A serie of crash prevented making it work.
Our manufacturer will check this issue in order to identify the problem.
Meanwhile, a temporary solution to bypass the proxy has been set up.
This solution has enabled phones work again. For an unknown reason by now, only theservers\" asterisk\" failed to register.
So we are back to the original configuration.
The service got back to normal for all.
Date: 2011-11-16 06:29:18 UTC
We started the intervention.
Date: 2011-11-10 03:39:43 UTC
Activation failed, we returned to the original configuration.
The operation is postponed later.
Date: 2011-11-10 03:36:15 UTC
We started the operation.
Date: 2011-11-07 20:44:08 UTC
The operation was postponed to Wednesday November 9th at 5 a.m .
The purpose of this proxy is to improve the security of our infrastructure.
It will be the best parade at the hands of the bad SIP behaviours which can
happen on the internet.
It will help provide new services:
- The secure of SIP accounts (restrictions by IP for example),
- a better compatibility of the MWI service (indication message on the answering machine),
- the SMS,
- and others
This proxy is on bêta since a few months. We were able to test it
in all ways.
The results are very good with a a few thousand people of subscribers. All the possible tests
were done. Now, there still a single test:
the behaviour of the proxy in the real world.
The accounts of our Belgium, German, English and Spanish subsidiaries already use this proxy from the very beginning.
The introduction of the proxy will be totally transparent. No manipulation is necessary from your side.
Update(s):
Date: 2012-03-01 01:27:56 UTC
The proxy has been deployed on the new domain: sip.ovh.fr
Current lines can be migrated via manager.
Date: 2011-11-29 11:42:04 UTC
The update of the proxy was done correctly.
We check the corrections done in order to put it in production in the next days.
Date: 2011-11-29 11:40:17 UTC
Our constructor did provide us the last corrective patches.
We are installing them on the proxy.
Date: 2011-11-16 23:25:20 UTC
The proxy implementation hasn't been performed correctly. A serie of crash prevented making it work.
Our manufacturer will check this issue in order to identify the problem.
Meanwhile, a temporary solution to bypass the proxy has been set up.
This solution has enabled phones work again. For an unknown reason by now, only theservers\" asterisk\" failed to register.
So we are back to the original configuration.
The service got back to normal for all.
Date: 2011-11-16 06:29:18 UTC
We started the intervention.
Date: 2011-11-10 03:39:43 UTC
Activation failed, we returned to the original configuration.
The operation is postponed later.
Date: 2011-11-10 03:36:15 UTC
We started the operation.
Date: 2011-11-07 20:44:08 UTC
The operation was postponed to Wednesday November 9th at 5 a.m .