I do get connection error every once in a while. If I disconnect and reconnect, it becomes online again, no connection error.
Update:
I just realized that the voip encryption setup above only works halfway. Outgoing calls work, but not incoming calls. When I call my Jami sip, I hear from the callers end a voip.ms message that the number I called is unavailable. From the Jami sip point of view, the status is online. On my voip.ms portal, it said that my Jami sip is registered.
I can receive incoming calls only if I deactivate TLS Transport.
How should I configure the TLS Transport so I can receive incoming calls?
When creating the account, use the following hostname format:
subdomain.voip.ms:5061;transport=tls
I made only the following changes in the Account settings:
Enable âEncrypt media streams (SRTP)â
Enable âEnable SDES as key exchange protocolâ
Enable âUse TLS Transportâ
I can also see in the voip.ms interface that I the account is securely registered.
One odd item is that I have two voip.ms accounts logged into the same Jami app and both are configured identically. One of the accounts voip.ms shows as as not registered, but Jami says it is online I can make calls with it no problem.
I just sorted out an additional issue that I didnât see before.
After some time, both logged in accounts could not make an outbound call (did not test inbound). Logging an account out and back in seemed to fix this. I thought that not setting registration expiration time to 120 could be the cause, so I set that to 120.
However, the only way I fixed this was to delete the second account, because the issue occurred even when the second account was disabled for a period.
The clue was that the voip.ms interface showed only the second account logged in and the first account not logged in, even though each has a unique set of login credentials.
What I am now testing is adding the second account using a different subdomain. Immediately, the voip.ms interface shows both accounts logged in securely, which it was not doing before, and both can successfully call 4443.
Something else Iâve discovered is that I canât figure out how to get SMS text messages to work.
On the portal, it is registered, but no secure transport
I can receive incoming calls.
Echo test works.
If I add:
Activate: Use TLS Transport
Permutate between 5061 (voip.ms TLS port) and the default value for whatever port options available.
result:
On Jami, the account is online.
On the portal, it is registered with secure transport
I cannot receive incoming calls.
Echo test works.
It must be something related to TLS configuration in Jami.
There are many TLS options underneath âUse TLS Transportâ. I donât know how to set these options to make encrypted voip work properly.
Among the TLS options, there are 3 which have red exclamation marks:
Certification Authorities
Certificate File
Private Key File
Regarding SMS:
Messages sent from Jami SIP (encrypted) is not received on the voip.ms portal.
Messages sent to Jami SIP (encrypted) is not received.
Messages sent from Jami SIP (unencrypted) is received on the voip.ms portal.
Messages sent to Jami SIP (unencrypted) is not received.
Iâm so confused how youâre able to get to a dialer. Did something change in the Jami application to remove this? Thereâs nothing in the interface that would indicate this can dial phone numbers.
Coming back here to say that I figured it out. Not very intuitive, but I just typed the number in that search box and tapped on it and it opens a conversation view that allows messaging and calling.
In 427, I saw a