SIP TLS and SRTP Certificate Rotation: Renewing Credentials Without an Outage
Certificate lifecycle problems do not announce themselves. The common pattern is a certificate issued through a portal by an engineer who has since left, or a device configured with a certificate that was valid on the day it was installed and has not been examined since. Nothing in day-to-day operation depends on certificate validity until the moment the peer refuses the handshake, and by then the failure looks like somebody else's fault.
Two Credential Families With Different Lifetimes
Call setup encryption and media encryption are negotiated separately and fail separately. The signalling certificate sits on the trunk or on the session border controller and is long-lived, typically issued with a validity period measured in months to a year. Media keys are usually negotiated per session, established at call setup through a key exchange rather than held on the device. A site can therefore run for years with healthy media keys while the credential that permits the setup negotiation has aged past its expiry.
Where DTLS-SRTP is used, the media side also carries a certificate with its own renewal behaviour. Deployments that use it for key exchange rather than for authentication still need to know which mode is in use, because the symptom and the fix differ. Write the mode down next to the expiry date. It is the most useful line in the file.
| Credential | Where it lives | How it fails |
|---|---|---|
| TLS signalling certificate | Trunk or session border controller | Handshake refused; transport error at call setup |
| DTLS-SRTP certificate | Endpoint or gateway media stack | Media negotiation fails or will not secure |
| Intermediate and root chain | Trust store on each device | Handshake fails despite a valid leaf certificate |
| Shared secret or token | Integration target or API client | Authentication rejected, deliveries stop silently |
| Renewal request | Issuer portal or requester mailbox | Never arrives; expiry approaches with no warning |
Renewal Fails Quietly When the Chain Is Not Complete
Automatic renewal helps only where the whole chain supports it. Where the issuer requires a manual approval, where the device keeps its private key in a form that cannot be replaced without a site visit, or where an intermediate certificate is required and was never uploaded, the automation does nothing and reports nothing. A monitoring job that only checks the device's own clock will never notice a certificate that was never renewed because nobody received the request.
There is a second quiet failure mode: the device keeps using the old certificate because the new one was uploaded to the wrong trust store, or the renewal was applied to the management interface rather than to the trunk profile. The platform reports healthy because the process is running. Only a handshake attempt finds out otherwise.
What an Expired Certificate Looks Like on the Wire
On the signalling side, a failed handshake during connection or renegotiation surfaces as a transport error. Depending on how carefully the stack logs it, the peer may report a certificate error, a generic handshake failure, or a timeout. These get misread as a firewall problem, a NAT timeout, or a carrier outage, and the investigation walks in the wrong direction for half a day. Check the expiry date first, because it costs a minute and explains a great many incidents.
On the media side the failure is narrower: calls set up and carry no audio, or the negotiation falls back to an unencrypted path that the policy forbids and the platform refuses to allow. Both present to the vendor as something they have never seen, because in their laboratory the certificates were valid.
- Record the expiry date of every credential in one inventory, not in several places
- Check whether renewal is genuinely automatic or depends on a human approval
- Confirm the full certificate chain is stored, including any intermediate
- Confirm the renewed certificate was applied to the trunk, not only to the web interface
- Test a handshake against the peer shortly after renewal, before the old one expires
- Monitor from outside the platform as well, so a silent renewal failure is visible
- Rotate on a schedule that leaves room for a second attempt before expiry
Rotating Without an Outage
The safe procedure has one rule: never remove the old credential before the new one is confirmed in use. Issue the replacement with an overlapping validity window. Install it on the device or upload the chain. Confirm that the device is actually presenting the new certificate by looking at the negotiated parameters on a live call. Then let the old one expire on its own.
Where a device can hold two trust anchors, use that and the change becomes uneventful. Where it cannot, the rotation is a coordinated swap with both ends prepared, and the risk of a handshake failure at an awkward moment is real enough to schedule. For DTLS-SRTP, the equivalent check is whether a fresh session picks up new material, since sessions established before the rotation keep the old keys until they end.
Redstone Approach
Redstone deployments treat the signalling certificate and the media key material as separate operational objects, so completing a renewal on one does not mark the other as done. Trunk profiles can be staged to accept the replacement credential before the outgoing side is switched, so the overlap is a configuration state rather than a hope. Health checks can be written against negotiation state, which reports on the traffic path instead of on whether a process happens to be running.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.

Current Location :

