Closed GoogleCodeExporter closed 9 years ago
For reference, what was discussed in private mail after logs collection --
seems linked to TLS transport use
To activate it :
- Go in global settings, in Network section, Secured transport and enable TLS transport. (This will globaly enable TLS transport as available for the sip stack).
Next step is to configure the account to use TLS transport.
To do so :
Create your account with basic wizard. For now don't enter the :5061 port. Just
the server and your credential.
Save. -- it will probably not register at this point but not a problem --
Then long press the account row and select the option to change the wizard and
choose "Expert".
Edit the account. You'll see a lot of options.
In transport select "TLS" instead of UDP.
It should be normally enough. Optionally you can change all "sip:" uri (in
registrar and in proxy field) to "sips:" uris.
It's a little bit complicate for now as the feature is new ;). When sip
providers supports TLS, I usually create a dedicated wizard.
Original comment by r3gis...@gmail.com
on 28 Sep 2012 at 9:39
merged in issue 2001.
I still try to investigate the problem but the weird thing is that I do not
reproduce from my network.
Could be interesting to regularly update to latest nightly build as sometimes I
update changes from the sip stack that might help with this kind of issue.
Original comment by r3gis...@gmail.com
on 15 Nov 2012 at 11:30
Original issue reported on code.google.com by
hammad....@gmail.com
on 26 Sep 2012 at 9:14