I have this setup exactly the same on my freepbx 13 system and it works perfect using yealink phones. If you call from the outside and hit a ring group, it should hit the alert info and play Ring2.wav. Instead it is playing the default ring tone which is defined in the basefile as account.1.ringtone.ring_type.
I am trying to make the ring tone different between internal and external calls. Basefile is set as follows:
Why is it bypassing the ringgroup alert ?
LOL. I was banging my head on the wall! Hope to see this resolved Monday then.
I have applied the edge fix and still is not working for me on 3 different systems
I think the fix was for FreePBX 14. I am also having the same issue with FreePBX 13 and Yealink.
I have the same issue. I also have yealink. So this is not resolved.
The fix was for 14 only as the title of this thread says āafter 14 Upgradesā
There are comments on the ticket that this relates to stating otherwise.
You can provide logs from the Asterisk Full log
Example:
Dialed test DID
Hit ring group which rings extension 1000 and 10
Both used default ring tone.
Called from extension 10 to 1000, same ring tone.
Alert info is set to a different ring tone than the default.
Full log:
FullLog
AGI Script Executing Application: (SIPAddHeader) Options: (Alert-Info:http://127.0.0.1/Vin/Ring1.wav:info=outside)
You havenāt upgraded. This function is no longer in the code at all. Did you confirm in Core that you actually upgraded?
fwconsole ma list | grep core
If your version is correct there then you have a custom dialparties.agi because we arenāt shipping a dialparties.agi that calls that Application anymore (https://github.com/FreePBX/core/commit/236df6a15cdd593da061b98a83d2b229e64276d3#diff-bcbf8063f22af25bcc8ce0317532eeefL83)
Thatās odd. I setup Edge and ran all the updates.
This is what your command provides:
[root@pbx~]# fwconsole ma list | grep core
| core | 14.0.18.46 | Enabled | GPLv3+
Since it did upgrade, was is the process of fixing this? I have over 50 clients with this issue.
Iām pretty confused why sangoma would take away something that was there before. Would would this function no longer be in the code? Was dialparties.agi changed recently? if so , why?
What are you talking about. The code that is referenced in your log is removed but the functionality still works. The fact that your log file still has that old line in it only proves that you havenāt updated. Your dialparties is running sipaddheader function. We no longer run that function in that file at that location. So I can instantly tell by looking and seeing that line that you are using the old dialparties because in new dialparties it doesnāt execute that function. You see. Headers are set outside of that file now. The fact that you still see that function call and the fact that you have pjsip extensions is a red flag. It wonāt work for you until you upgrade. That is what I am trying to explain.
I posted the results of the command. Isnāt that the upgrade? What am I missing?
Andrew, I am not sure if I should create a new topic since the system I am talking about is a little different.
I upgraded core (on a FreePBX 14 Asterisk 15) from 14.0.18.18 to 14.0.18.46 on Tue, Jan 15.
Internal calls alert-info is set to ring 2. It was working fine till I updated to .46.
Yesterday we got a complain that it stopped working.
Hereās a log from 1/14 where alert-info is working. https://pastebin.freepbx.org/view/a3b36401
Hereās a log from yesterday 1/16 where itās not working. https://pastebin.freepbx.org/view/1cd59d08
Hereās what I see different in the logs.
Working one 1/14:
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] app_stack.c: SIP/169-000256f2 Internal Gosub(func-apply-sipheaders,s,1) start
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:1] NoOp("SIP/169-000256f2", "Applying SIP Headers to channel") in new stack
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:2] Set("SIP/169-000256f2", "SIPHEADERKEYS=Alert-Info") in new stack
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:3] ExecIf("SIP/169-000256f2", "0?Set(Rheader=1)") in new stack
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:4] While("SIP/169-000256f2", "1") in new stack
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:5] Set("SIP/169-000256f2", "sipheader=ring2") in new stack
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:6] SIPAddHeader("SIP/169-000256f2", "Alert-Info: ring2") in new stack
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:7] Set("SIP/169-000256f2", "PJSIP_HEADER(add,Alert-Info)=ring2") in new stack
[2019-01-14 09:29:25] ERROR[39945][C-00012dbc] res_pjsip_header_funcs.c: This function requires a PJSIP channel.
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:8] EndWhile("SIP/169-000256f2", "") in new stack
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:4] While("SIP/169-000256f2", "0") in new stack
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:9] ExecIf("SIP/169-000256f2", "0?SIPRemoveHeader(Alert-Info:)") in new stack
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:10] ExecIf("SIP/169-000256f2", "0?Set(PJSIP_HEADER(remove,Alert-Info)=)") in new stack
[2019-01-14 09:29:25] VERBOSE[39945][C-00012dbc] pbx.c: Executing [s@func-apply-sipheaders:11] Return("SIP/169-000256f2", "") in new stack
Not working 1/16:
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] app_stack.c: SIP/160-00002135 Internal Gosub(func-apply-sipheaders,s,1) start
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:1] NoOp("SIP/160-00002135", "Applying SIP Headers to channel SIP/160-00002135") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:2] Set("SIP/160-00002135", "TECH=SIP") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:3] Set("SIP/160-00002135", "SIPHEADERKEYS=Alert-Info") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:4] ExecIf("SIP/160-00002135", "0?Set(Rheader=1)") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:5] While("SIP/160-00002135", "1") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:6] Set("SIP/160-00002135", "sipheader=ring2") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:7] ExecIf("SIP/160-00002135", "1?Set(sipheader=<uri>;info=ring2)") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:8] ExecIf("SIP/160-00002135", "1?SIPAddHeader(Alert-Info,<uri>;info=ring2)") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:9] EndWhile("SIP/160-00002135", "") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:5] While("SIP/160-00002135", "0") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:10] ExecIf("SIP/160-00002135", "0?SIPRemoveHeader(Alert-Info:)") in new stack
[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [s@func-apply-sipheaders:11] Return("SIP/160-00002135", "") in new stack
Finally, I went and downgraded to core 14.0.18.18 and it started working again
@PitzKey on line 209 of the log you say isnāt working sipaddheader is executed for your Chan sip extension. This is working correctly.
I donāt know what to tell you. It wasnāt working, the (Sangoma) phone did not ring with ring2.
Is there any additional log(s) I can provide? Something is clearly broken with .46 that it doesnāt work in that version, because when you downgrade it does work. And we both see that something changed in the way alert-info is being sent, in the quoted logs above.
I really appreciate your time looking at this.
Look at line 209. Looks right to me. It now has < uri > which if you look at the RFC for alert info for sip you will see it requires this. Thereās nothing more to look at.
I donāt really understand whatās going on here. But in the 1/14 log you see:
Executing [s@func-apply-sipheaders:6] SIPAddHeader("SIP/169-000256f2", "Alert-Info: ring2")
My understanding is: it adds the SIP Header to the ringing phone (In this case 160 called 169)
But in the 1/16 log. I donāt see the SIP Header being added to SIP/119-00002134
(in this case 160 called 119)
I might be totally off hereā¦
I upgraded again today to .48 and the ring tones are still not passed. I pasted the command showing you its upgraded. What do we need to do to resolve this?