[asterisk-bugs] [JIRA] (ASTERISK-27775) Includes for Events in pjsip_notify.conf lead to more Event headers

[AvayaXAsterisk (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242833#comment-242833 ] 

AvayaXAsterisk edited comment on ASTERISK-27775 at 3/26/18 5:23 PM:
--------------------------------------------------------------------

pjsip_notify.conf contains this:
#include sip_notify_custom.conf
#include sip_notify_additional.conf

sip_notify_additional.conf contains this (among other sections for different phones)
[reboot-yealink]
Event=>check-sync\;reboot=true

sip_notify_custom.conf contains this:
[reboot-yealink]
Event=>check-sync\

A sip notify will then contain both headers instead of one, leading to a conflict:
Event: check-sync\ 
Event: check-sync;reboot=true

Do you need any other configuration files as well?


was (Author: avayax):
pjsip_notify.conf contains this:
#include sip_notify_custom.conf
#include sip_notify_additional.conf

sip_notify_additional.conf contains this (among other sections for different phones)
[reboot-yealink]
Event=>check-sync\;reboot=true

sip_notify_custom.conf contains this:
[reboot-yealink]
Event=>check-sync\

A sip notify will then contain both headers instead of one, leading to a conflict:
"Event: check-sync\ 
 Event: check-sync;reboot=true "

Do you need any other configuration files as well?

> Includes for Events in pjsip_notify.conf lead to more Event headers
> -------------------------------------------------------------------
>
>                 Key: ASTERISK-27775
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27775
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_notify
>    Affects Versions: 13.18.3
>            Reporter: AvayaXAsterisk
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: pjsip
>
> This issue was discovered on FreePBX distro, but the developers asked me to report it here as a pjsip problem.
> When using Includes in pjsip_notify.conf, like FreePBX does with 
> #include sip_notify_custom.conf and #include sip_notify_additional.conf in it, and having different event headers in each file, the SIP notify will then contain both event headers, conflicting each other.
> This is not happening on chansip.
> There is no need for Asterisk to include two event headers in pjsip, the first one is sufficient.
> NOTIFY sip:5314 at 10.124.193.26:5160 SIP/2.0 
>  Via: SIP/2.0/UDP 10.1.1.176:5160;rport;branch=z9hG4bKPj962499e6-e385-4034-b112-f65804ebe63d 
>  From: <sip:5314 at 10.1.1.176>;tag=0d0a4a08-e929-401f-9d23-61d142d446b4 
>  To: <sip:5314 at 10.124.193.26> 
>  Contact: <sip:5314 at 10.1.1.176:5160> 
>  Call-ID: 44665192-e993-4979-81fe-02c17fa959ad 
>  CSeq: 25027 NOTIFY 
>  Subscription-State: terminated 
>  Event: check-sync\ 
>  Event: check-sync;reboot=true 
>  Max-Forwards: 70 
>  User-Agent: FPBX-13.0.194.2(13.18.3) 
>  Content-Length: 0



--
This message was sent by Atlassian JIRA
(v6.2#6252)