In this example, you send the curl request to the background, & , in effect ‘forking’ , so not ‘blocking’ , whether you proceed in the dialplan ‘correctly’ is doubtful.
Methods of properly calling external processes is discussed here
https://wiki.asterisk.org/wiki/pages/viewpage.action?pageId=29395573
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
Try the case insensitive (-i)
grep -i reachable
Turns out this was my ISP (ATT) is blocking SIP traffic while adamant they aren’t. Moved the connection to my prImary (Comcast) and it started working again.
So I’m having a problem with my webphone. When it register, this is the message on CLI:
== WebSocket connection from 'myip:55886' for protocol 'sip' accepted using version '13'
-- Added contact 'sip:s609edb2@myip:55886;transport=ws' to AOR '101' with expiration of 600 seconds
== Contact 101/sip:s609edb2@myip:55886;transport=ws has been created
-- Removed contact 'sip:qja79msi@myip:53980;transport=ws' from AOR '101' due to remove_existing
== Contact 101/sip:qja79msi@myip:53980;transport=ws has been deleted
-- Contact 101/sip:s609edb2@myip:55886;transport=ws is now Reachable. RTT: 69.304 msec
But when I try to make a call, just right after I allow the permissions on browser, the call finish. What I thought: “transport = ws” should be “transport = wss”. Am I right? And how could I change that?
Hello,
Is there a way to have the headset ring instead of beep when an incoming call comes in? User says the ringing on the S700 is not loud enough for them with the ringer volume up all the way. If they’re away from the front desk, they can’t hear the beep in the headset to announce an incoming call.
Is there a way I can make this louder, or to ring instead of just beep?
Thank you,
‘wss’ needs valid ssl certificates installed, ‘ws’ doesn’t , BUT very few modern browsers allow ‘ws’ anymore
Hello Community,
i have a FreePBX Warm Spare Setup running on 2 Different Locations. Each one has it’s own Public IP.
The Failover Scenario is an A Record Hostname with TTL 60s.
Also all phones do a re-register every 60 seconds.
So if i change the A record to the Failover PBX all phones and trunks are up within 1 Minute and eherything works except BLF Lights.
The BLF lights on all phones do not show anything anymore and stuck.
After a reboot of all phones the BLFs begin to work on the Failover PBX.
I have no idea how i can automate this Failover sceanrio with working Hints.
I already tried to dynamically generate hints but this did not solve the problem.
We are using Chan_SIP.
Does anyone have an idea how to get this working or maybe another Free Failover Solution which works on 2 different locations with 2 different IPs.
@dicko, thanks for the reply. I do have a valid ssl certificate, it should’be passing through wss?
Also, should I turn SIP NAT on?
Going to use ghostscript for this.
http://pages.cs.wisc.edu/~ghost/doc/AFPL/8.00/Devices.htm#TIFF
What phones are you using. Not all phones support this. I use Yealink now, used to use Grandstream gxp2160, and I know that both of these BLFs work in the scenario u had described.
You might be better served using prioritized SRV records in place of manipulating A records.
Blockquote
I use Yealink T46S, T56A, T58V and all do not work with this scenario…that means, everything works perfectly except BLF until i reboot all phones.
I cannot do this because i need it strict handlet which pbx should be used. A Script is changing the A Record, disabling my trunks on primary and activate them on the failover machine when the Primary is down or when i do some maintanance.
Also the most phones do not work out of the box with SRV records. Most phones have A Record as default setting
I must be missing something then, if you prioritize then everything is handled by the ip of the highest prioritised IP if it is there, only when that IP disappears when “The server is down” or "You do some maintainance and let DNS know you are " that the “Backup Serrver” will ever see traffic.
Which one worked? Upgrading RPMs or moving to HTTP
For me i prefer the A Record Failover. Srv records do not work with all phones and also needs to be special configured for every phone.
If i can solve the BLF problem im already really happy 
Your headset controls the beep level. We have no control over that.
Thanks for the insight and I agree with your sentiments. Unfortunately with a few hundred $ in credit across my GV accounts and a family who just want the phone to work I need to provide a solution. I read the comment from the Obitalk member who described people using GV in this way as ‘freeloaders’ which I thought was indicative of a weak character. Ultimately if there is an asterisk solution within a month I will just return the Obihai, a silly situation which benefits nobody in the end.
Well, good luck then.
Just as a point of record Yealinks T46S, T56A, T58V are very happy with SRV records, you could even say prefer it, just change your transport type to DNS-NAPTR (one line in your provisioning setup) and you should be good to go.