Thanks for prompt reply.
Yes port 5070.
Have done the usual :test with fresh extension, restart app & restart 'phone.
Later today will:
check that an Android 8 'phone which registered was in fact using TLS,
test with an Android 12 device & any other device to hand.
Sipdroid (latest version) on Android 14 'phone will not register to pbxes.org by TLS protocol. It will register by TCP or UDP. It was registering by TLS earlier this week.
Thanks.
I now have Sipdroid Callthru working.
Previously within Sipdroid I had 'Call Options'/'Preferred Call Type' set to 'Always ask' now with it set to 'Sipdroid only' as you suggest the calls progress as you describe - the only difference being that I am dialing from the Android dialer.
Within Sipdroid 'SIP Account'
1- untick 'Use WLAN'
2- untick 'Use 3G'
3- untick 'Use EDGE'
( if you want outgoing calls to trigger callback regardless of available networks )
Again thanks
'SIP Ringtone' selections:
'Default ringtone' rings only once,
but 3 other ringtones that I have tested continue to ring until call is answered.
Thanks for your swift reply.
I have tested & yes on an incoming call from public network audio does not pass through until Sipdroid is made to answer.
WIth Sipdroid ringing for such a short time it makes it easy to miss incoming calls & even answer them by without realising especially iwhen mobile 'phone is in a pocket!
This behaviour is new to me but since I usually use Sipdroid to 'PSTN number' for incoming calls & 'Trigger Callback' for outgoing
calls I might not have noticed it until this year.
Would it be possible to choose to make Sipdroid ring longer in a future update?
Using Sipdroid 6.1 beta with 2 different Android 8.1.0 mobile phones and Sipdroid registered to pbxes extension outgoing calls are fine but on incoming call to Sipdroid:
1 -Sipdroid rings briefly & then receives audio from caller
2 -caller continues to hear ringing tone with no warning of being heard
3 -after Sipdroid is made to answer (by flicking mobile phone screen upwards) the call is answered normally with 2 way audio
Unfortunately I did not make a note of when this problem started but think it was probably February 2022. Apologies for not reporting this earlier.
Thanks. Have tested several times & nothing has changed. Webcall URL still does not work.
I have pressed Submit in Personal Data which think re-starts the account.
Webcall URL stopped working a few days ago. I go to https://www1.pbxes.com/<acccountname>-<**********>
(as set in extension) in browser & the text that I set in the extension appears (proving that the URL set in the extension is recognised). I then enter a number & press call button it says "Dialling" but nothing happens. The extension is not called & nothing appears in System Log or Call Monitor.
Sipdroid Trigger Callback has also stopped working as it relies upon the Webcall URL above. I have the latest Sipdroid version (5.9 beta).
Webcall URL had been working since June when you fixed it - thanks again for this - but the problem has re-appeared.
Thanks for fixing Webcall so quickly & info on Sipdroid Trigger Callthru. I will experiment with Sipdroid Callthru as you suggest & let you know of any success.
All now seems to be working including Sipdroid Trigger Callback & I will test fully & reply further if necessary.
To avoid confusion for anyone reading this I made an error in the 1st post - https; when I meant https:
Webcall URL stopped working about 2 weeks ago. I go to
https;//www1.pbxes.com/<acccountname>-<**********>
(as set in extension) in browser & the text that I set in the extension appears (proving that the URL set in the extension is recognised). I then enter a number & press call button it says "Dialling" but nothing happens. The extension is not called & nothing appears in System Log or Call Monitor.
Sipdroid Trigger Callback has also stopped working as it relies upon the Webcall URL above. I have the latest Sipdroid version (5.7 beta).
Sipdroid Trigger Callthru does not work. It ignores the Prefix & simply dials number entered using 'phone. I have included this info in case it helps with the above & realise that it might need a seperate thread.
Thread: 
Thread: