Alert-Info header format changed from
this way it’s no more compatible with some phones.
Temporary solved by editing
Requiring a final solution.
I would appreciate very much if, after many years working in a not strictly RFC compliant way, but indeed phone compliant, the FreePBX GUI could give me the opportunity (maybe just a flag in the GUI?) to choose if I want to continue to use the old Alert-Info format or if I prefer the new, strictly RFC compliant one.
Note: Using such a flag/option, one could just pass RFC compliant headers by typing
in the GUI text field Connectivity - Inbound Routes - General - Alert info resulting in the header:
Since last Friday, when I upgraded FeePBX to 188.8.131.52 (now core is at version 184.108.40.206) and Asterisk to 13.22.0, distinctive ringtone on my Cisco SPA 303 phones did not work any more.
After last upgrade the phones rung the same (default) tone independently on the source of the call, while, before upgrading, they rung differently when the call came from inside or outside.
After some analysis I found that the problem is the new format of the Alert-Info header in the sip INVITE.
Let’s say that I set Connectivity - Inbound Routes - General - Alert info to
the new version sends to the phones an INVITE packet with the following Alert-Info header
while, in the previous version it was simply
While the new format is compliant to RFC7462, my phones are not able to parse the new Alert-Info format so they ignore the header at all, not paying the different ringtone.
Now, my phones are old, but work perfectly, as I suppose, many other similar phones all over the world do. We cannot expect Cisco (or other manufacturer) to release new firmwares for them.
By now I’ve temporary solved the issue by manually editing the file
exten => xxxxxxxxxz,n,Set(__ALERT_INFO=foo)
exten => xxxxxxxxxx,n,SIPAddHeader(Alert-Info: foo)
like previous FreePBX versions.
But, this way, I will need to re-edit the file it every time FreePBX will have applied some changes.
- Does anybody know if there is a way to keep the change to persist to Freepbx reload?
- Or any way to re-enable in FreePBX the old Alert-Info format?
- Someone with the same issue?
- Should post the request elsewhere?