No Alert Info passing through after 14 Upgrades

FreePBX
41

I don’t see anything to resolve. Sorry. In the last logs you added dialparties.agi was still calling the old function. It wouldn’t say:

AGI Script Executing Application: (SIPAddHeader) Options: (Alert-Info:http://127.0.0.1/Vin/Ring1.wav:info=outside)

At all.

42

On line 209. Which I already told you about. It puts it on 160. Please look.

[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

43

If your using Sangoma phones please open a support ticket on this and someone can dig into it as there seems to be a disconnect somewhere here and we are just going in circles.

44

I’m not here to just make you work or keep on going in circles.

I believe you when you say that the logs shows it’s being sent correctly. But I’m just trying to help here and provide the necessary logs to find the cause in version .46.

To clarify.
In both cases, 160 was the one who placed the call.
From the 1/14 log I understood that the SIP Header was added to 169 and in the 1/16 log its being added to 160.

As Tony suggested, I’ll open a ticket for the Sangoma Phones.

45

Because you are dialing 160 from 119. Line 3-4. You say “160 was the one who placed the call”. But that is not true from the logs.

[2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx.c: Executing [160@from-internal:1] GotoIf("SIP/119-00002134", "1?ext-local,160,1:followme-check,160,1") in new stack [2019-01-16 13:21:54] VERBOSE[5182][C-00001110] pbx_builtins.c: Goto (ext-local,160,1)

In these two lines of dialplan the channel is 119 (the dialer). It is dialing 160. Then on line 209 the header is added to the channel for 160

[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

46

I apologize, I guess I grabbed a wrong log file. I’ll get the correct one soon.

47

I ran all updates though, I’m confused why it was working before the update and now it’s not. Besides the core which is current at .48 what else needed upgraded?

48

That is it. Post your logs again and let’s see if dialparties.agi has the offending line or not

49

Logs attached. Tested from outside. Says it’s hitting ring1.wav but it’s actually using the default ring3.wav from the outside. Called from extension 10 to 1000 and still played ring4.wav

basefile edit settings on template:
Capture

Full Log

50

I apologize again for the confusion.
Here’s two logs where 105 called 136

1/14 https://pastebin.freepbx.org/view/9861923b
1/16 https://pastebin.freepbx.org/view/de8060a3

I see again on line 209 the same differences.
1/14

Executing [s@func-apply-sipheaders:6] SIPAddHeader("SIP/136-00026343", "Alert-Info: ring2")

1/16

Executing [s@func-apply-sipheaders:8] ExecIf("SIP/136-000018d8", "1?SIPAddHeader(Alert-Info,<uri>;info=ring2)")
51

In both instances Alert-Info is set.

52

Now you are upgraded correctly and I see the issue. The way you did your Alert-Info is not to the RFC

You did:

http://127.0.0.1/Vin/Ring1.wav:info=outside

I believe it should be

<http://127.0.0.1/Vin/Ring1.wav>;info=outside

In some RFCs I have looked over the colon ‘:’ is only valid within the URN

Alert-Info: <urn:alert:service:normal>;appearance=1

Here’s a few examples:

Of note @PitzKey this applies to you as well.

53

Meaning, I have to set this manually, or this needs to be fixed in EPM?

54

Nothing needs to be fixed. The Alert info sent to your device is valid as per the RFC. EPM does not control Alert-Infos.

Format is:

<uri>;info=ring2
55

I am not sure I follow here.

When we configured the PBX we set in advanced settings the following:

image
image928×160 11.6 KB

It worked perfectly on all the Sangoma phones we have there, until I upgraded core to .46. (When I downgrade it works again)

What changed that it stopped working in .46, and what do I need to change to make it work again?

56

that made no difference. See new log:

Full Log

57

You’ll need to bring this up with support because for your exact setup with a Sangoma phone our QA team confirmed it works.

58

You didn’t do what I said. Now your alert-info is still

info=http://127.0.0.1/Vin/Ring1.wav:info=outside

But you have so many calls in this log file that it’s hard for me to actually read it.

There is no reference to <http://127.0.0.1

59

I will. Thank you for your time!

60

I’m not sure how to filter it but I did make the changes. On line 59697 is clearly shows http://127.0.0.1/Vin/Ring1.wav;info=outside