You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to set up FreeSWITCH using TLS.
SIP-Trace shows the device registering through TLS.
When receiving a call FreeSWITCH receives an INVITE through TLS. FreeSWITCH replies through TLS, however the header "Contact" does not contain "transport=tls". Because of this, the other system tries to reply on port 5060/UDP, which leads to a timeout.
Is this just due to poor configuration or is there a bug in FreeSWITCH? Are there any additional configurations that have to be set for this to work?
If additional information are needed please let me know.
Description:
I'm trying to set up FreeSWITCH using TLS.
SIP-Trace shows the device registering through TLS.
When receiving a call FreeSWITCH receives an INVITE through TLS. FreeSWITCH replies through TLS, however the header "Contact" does not contain "transport=tls". Because of this, the other system tries to reply on port 5060/UDP, which leads to a timeout.
Is this just due to poor configuration or is there a bug in FreeSWITCH? Are there any additional configurations that have to be set for this to work?
If additional information are needed please let me know.
Relevant configuration:
SIP
The following SIP message is received by the other system, "Contact" does not contain any transport parameter:
The text was updated successfully, but these errors were encountered: