BLF 'NOTIFY' not working

List overview All Threads
Download

newer

older

Unresolvable destination for new...

Call limit through shared database

Petarr Jones

30 Sep 2019 30 Sep '19

1:16 p.m.

I am using Kamailio 5.2 with the following PRESENCE modules and parameters:

loadmodule "presence.so" loadmodule "presence_xml.so" loadmodule "presence_dialoginfo.so" loadmodule "presence_reginfo.so"

modparam("presence", "db_url", DBURL) modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) modparam("presence_xml", "disable_bla", 0) modparam("presence_xml", "integrated_xcap_server", 1)

I have a Yealink T28P phone which has two lines/extensions successfully registered with Kamailio 5.2. When I setup the BLF light to monitor one of the extensions, I get the correct SUBSCRIBE record but the NOTIFY record is sent over and over again until it fails.

----------------------------------------------------------------------------------------------------------- NOTIFY sip:101@192.168.1.123:5062 SIP/2.0 Via: SIP/2.0/UDP 45.45.45.45;branch=z9hG4bKd16c.03b5bc97000000000000000000000000.0 To: sip:101@45.45.45.45;tag=1366853594 From: sip:104@45.45.45.45;tag=a6a1c5f60faecf035a1ae5b6e96e979a-e6c3 CSeq: 2 NOTIFY Call-ID: 594386350@192.168.1.123 Content-Length: 0 User-Agent: kamailio (5.2.4 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: sip:45.45.45.45:5060;transport=udp -----------------------------------------------------------------------------------------------------------

When I register the phone with Freeswitch instead and run the same test, the NOTIFY works and I get a much longer NOTIFY message

----------------------------------------------------------------------------------------------------------- NOTIFY sip:100@192.168.1.123:5064 SIP/2.0 Via: SIP/2.0/UDP 66.66.66.66;rport;branch=z9hG4bK1mXej9r2605UB Route: sip:55.55.55.55:5064;transport=udp Max-Forwards: 70 From: sip:102@66.66.66.66;tag=xUoVghM5syHc To: "100" sip:100@66.66.66.66;tag=1720892352 Call-ID: 2583553127@192.168.1.123 CSeq: 1178415701 NOTIFY Contact: sip:102@66.66.66.66:5060 User-Agent: FreeSWITCH-mod_sofia/1.10.1-release-12-f9990221e6~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Event: dialog Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Subscription-State: active;expires=1800 Content-Type: application/dialog-info+xml Content-Length: 149

xml version="1.0"?> dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:102@66.66.66.66"> dialog-info> -----------------------------------------------------------------------------------------------------------

Should the message coming from Kamailio contain more data or is that not the issue. Should I be including other modules also?

All guidance would be appreciated.

Attachments:

attachment.html (text/html — 7.3 KB)

Show replies by date

Daniel-Constantin Mierla

1 Oct 1 Oct

7:16 a.m.

Hello,

there can be NOTIFY requests with no body, as the one below has Content-Length 0 -- a matter of what is the call state, it can be a valid one.

Regarding the fact that the NOTIFY is not delivered, have you done nat traversal for SUBSCRIBE? I see private address in the R-URI, so the problem can be in that part. You should do set_contact_alias() for SUBSCRIBE.

Cheers, Daniel

On 30.09.19 15:16, Petarr Jones wrote:

...

Hi

I am using Kamailio 5.2 with the following PRESENCE modules and parameters:

loadmodule "presence.so" loadmodule "presence_xml.so" loadmodule "presence_dialoginfo.so" loadmodule "presence_reginfo.so"

modparam("presence", "db_url", DBURL) modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) modparam("presence_xml", "disable_bla", 0) modparam("presence_xml", "integrated_xcap_server", 1) I have a Yealink T28P phone which has two lines/extensions successfully registered with Kamailio 5.2. When I setup the BLF light to monitor one of the extensions, I get the correct SUBSCRIBE record but the NOTIFY record is sent over and over again until it fails.

NOTIFY sip:101@192.168.1.123:5062 SIP/2.0 Via: SIP/2.0/UDP 45.45.45.45;branch=z9hG4bKd16c.03b5bc97000000000000000000000000.0 To: sip:101@45.45.45.45;tag=1366853594 From: sip:104@45.45.45.45;tag=a6a1c5f60faecf035a1ae5b6e96e979a-e6c3 CSeq: 2 NOTIFY Call-ID: 594386350@192.168.1.123 Content-Length: 0 User-Agent: kamailio (5.2.4 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: sip:45.45.45.45:5060;transport=udp

When I register the phone with Freeswitch instead and run the same test, the NOTIFY works and I get a much longer NOTIFY message

NOTIFY sip:100@192.168.1.123:5064 SIP/2.0 Via: SIP/2.0/UDP 66.66.66.66;rport;branch=z9hG4bK1mXej9r2605UB Route: sip:55.55.55.55:5064;transport=udp Max-Forwards: 70 From: sip:102@66.66.66.66;tag=xUoVghM5syHc To: "100" sip:100@66.66.66.66;tag=1720892352 Call-ID: 2583553127@192.168.1.123 CSeq: 1178415701 NOTIFY Contact: sip:102@66.66.66.66:5060 User-Agent: FreeSWITCH-mod_sofia/1.10.1-release-12-f9990221e6~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Event: dialog Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Subscription-State: active;expires=1800 Content-Type: application/dialog-info+xml Content-Length: 149

xml version="1.0"?> dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:102@66.66.66.66"> dialog-info>

Should the message coming from Kamailio contain more data or is that not the issue. Should I be including other modules also?

All guidance would be appreciated.

Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

Petarr Jones

9:57 a.m.

Thanks for your response Daniel.

Kamailio is installed on a cloud server (not AWS) and therefore has an internet facing IP address. The phone is in my office so there is NAT happening at that end. I would have thought the NAT traversal would only apply if the server/Kamailio was behind a firewall/router doing some kind of NAT?

Regards Petarr ________________________________ From: Daniel-Constantin Mierla miconda@gmail.com Sent: 01 October 2019 00:16 To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org; Petarr Jones petarrjones@outlook.com Subject: Re: [SR-Users] BLF 'NOTIFY' not working

Hello,

there can be NOTIFY requests with no body, as the one below has Content-Length 0 -- a matter of what is the call state, it can be a valid one.

Cheers, Daniel

On 30.09.19 15:16, Petarr Jones wrote: Hi

I am using Kamailio 5.2 with the following PRESENCE modules and parameters:

loadmodule "presence.so" loadmodule "presence_xml.so" loadmodule "presence_dialoginfo.so" loadmodule "presence_reginfo.so"

----------------------------------------------------------------------------------------------------------- NOTIFY sip:101@192.168.1.123:5062 SIP/2.0 Via: SIP/2.0/UDP 45.45.45.45;branch=z9hG4bKd16c.03b5bc97000000000000000000000000.0 To: sip:101@45.45.45.45 sip:101@45.45.45.45;tag=1366853594 From: sip:104@45.45.45.45 sip:104@45.45.45.45;tag=a6a1c5f60faecf035a1ae5b6e96e979a-e6c3 CSeq: 2 NOTIFY Call-ID: 594386350@192.168.1.123mailto:594386350@192.168.1.123 Content-Length: 0 User-Agent: kamailio (5.2.4 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: sip:45.45.45.45:5060;transport=udp sip:45.45.45.45:5060;transport=udp -----------------------------------------------------------------------------------------------------------

When I register the phone with Freeswitch instead and run the same test, the NOTIFY works and I get a much longer NOTIFY message

----------------------------------------------------------------------------------------------------------- NOTIFY sip:100@192.168.1.123:5064 SIP/2.0 Via: SIP/2.0/UDP 66.66.66.66;rport;branch=z9hG4bK1mXej9r2605UB Route: sip:55.55.55.55:5064 sip:55.55.55.55:5064;transport=udp Max-Forwards: 70 From: sip:102@66.66.66.66 sip:102@66.66.66.66;tag=xUoVghM5syHc To: "100" sip:100@66.66.66.66 sip:100@66.66.66.66;tag=1720892352 Call-ID: 2583553127@192.168.1.123mailto:2583553127@192.168.1.123 CSeq: 1178415701 NOTIFY Contact: sip:102@66.66.66.66:5060 sip:102@66.66.66.66:5060 User-Agent: FreeSWITCH-mod_sofia/1.10.1-release-12-f9990221e6~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Event: dialog Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Subscription-State: active;expires=1800 Content-Type: application/dialog-info+xml Content-Length: 149

xml version="1.0"?> dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:102@66.66.66.66"sip:102@66.66.66.66> dialog-info> -----------------------------------------------------------------------------------------------------------

Should the message coming from Kamailio contain more data or is that not the issue. Should I be including other modules also?

All guidance would be appreciated.

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.orgmailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Daniel-Constantin Mierla -- www.asipto.comhttp://www.asipto.com www.twitter.com/micondahttp://www.twitter.com/miconda -- www.linkedin.com/in/micondahttp://www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

Petarr Jones

1:29 p.m.

Daniel

Adding in the set_contact_alias() for SUBSCRIBE meant that the NOTIFY now gets a "200 OK", but the light on the phone does not light up even though the extension being monitored is registered.

I notice that after the SUBSCRIBE request, the return message is a "202 OK" instead of a "202 ACCEPTED". Is that correct?

I am also now getting this message in the log

nathelper [nathelper.c:700]: set_contact_alias(): you can't update contact twice, check your config! ________________________________ From: sr-users sr-users-bounces@lists.kamailio.org on behalf of Petarr Jones petarrjones@outlook.com Sent: 01 October 2019 02:57 To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org; miconda@gmail.com miconda@gmail.com Subject: Re: [SR-Users] BLF 'NOTIFY' not working

Thanks for your response Daniel.

Hello,

there can be NOTIFY requests with no body, as the one below has Content-Length 0 -- a matter of what is the call state, it can be a valid one.

Cheers, Daniel

On 30.09.19 15:16, Petarr Jones wrote: Hi

I am using Kamailio 5.2 with the following PRESENCE modules and parameters:

loadmodule "presence.so" loadmodule "presence_xml.so" loadmodule "presence_dialoginfo.so" loadmodule "presence_reginfo.so"

----------------------------------------------------------------------------------------------------------- NOTIFY sip:101@192.168.1.123:5062 SIP/2.0 Via: SIP/2.0/UDP 45.45.45.45;branch=z9hG4bKd16c.03b5bc97000000000000000000000000.0 To: sip:101@45.45.45.45 sip:101@45.45.45.45;tag=1366853594 From: sip:104@45.45.45.45 sip:104@45.45.45.45;tag=a6a1c5f60faecf035a1ae5b6e96e979a-e6c3 CSeq: 2 NOTIFY Call-ID: 594386350@192.168.1.123mailto:594386350@192.168.1.123 Content-Length: 0 User-Agent: kamailio (5.2.4 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: sip:45.45.45.45:5060;transport=udp sip:45.45.45.45:5060;transport=udp -----------------------------------------------------------------------------------------------------------

When I register the phone with Freeswitch instead and run the same test, the NOTIFY works and I get a much longer NOTIFY message

----------------------------------------------------------------------------------------------------------- NOTIFY sip:100@192.168.1.123:5064 SIP/2.0 Via: SIP/2.0/UDP 66.66.66.66;rport;branch=z9hG4bK1mXej9r2605UB Route: sip:55.55.55.55:5064 sip:55.55.55.55:5064;transport=udp Max-Forwards: 70 From: sip:102@66.66.66.66 sip:102@66.66.66.66;tag=xUoVghM5syHc To: "100" sip:100@66.66.66.66 sip:100@66.66.66.66;tag=1720892352 Call-ID: 2583553127@192.168.1.123mailto:2583553127@192.168.1.123 CSeq: 1178415701 NOTIFY Contact: sip:102@66.66.66.66:5060 sip:102@66.66.66.66:5060 User-Agent: FreeSWITCH-mod_sofia/1.10.1-release-12-f9990221e6~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Event: dialog Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Subscription-State: active;expires=1800 Content-Type: application/dialog-info+xml Content-Length: 149

Should the message coming from Kamailio contain more data or is that not the issue. Should I be including other modules also?

All guidance would be appreciated.

Petarr Jones

2 Oct 2 Oct

noon

I decided to try a different setup and install Siremis and Kamailio 5.1 according to the following tutorial : https://www.powerpbx.org/content/kamailio-v5-siremis-v5-debian-v9-mariadb-ap...

All is working and because this setup uses WITH_NAT, I have not needed to add set_contact_alias() to the SUBSCRIBE section of kamailio.cfg.

Unfortunately, the BLF lights on the phone do not light up. I can see dialog entries in the "Active Watchers List" in Siremis and no errors in the log. The other list ("Watcher List", "Presentity List" and "PUA List") are empty.

I have tested the phone directly with Freeswitch to make sure the lights are working.

Any ideas.

________________________________ From: sr-users sr-users-bounces@lists.kamailio.org on behalf of Petarr Jones petarrjones@outlook.com Sent: 01 October 2019 06:29 To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org; miconda@gmail.com miconda@gmail.com Subject: Re: [SR-Users] BLF 'NOTIFY' not working

Daniel

Adding in the set_contact_alias() for SUBSCRIBE meant that the NOTIFY now gets a "200 OK", but the light on the phone does not light up even though the extension being monitored is registered.

I notice that after the SUBSCRIBE request, the return message is a "202 OK" instead of a "202 ACCEPTED". Is that correct?

I am also now getting this message in the log

Thanks for your response Daniel.

Hello,

there can be NOTIFY requests with no body, as the one below has Content-Length 0 -- a matter of what is the call state, it can be a valid one.

Cheers, Daniel

On 30.09.19 15:16, Petarr Jones wrote: Hi

I am using Kamailio 5.2 with the following PRESENCE modules and parameters:

loadmodule "presence.so" loadmodule "presence_xml.so" loadmodule "presence_dialoginfo.so" loadmodule "presence_reginfo.so"

----------------------------------------------------------------------------------------------------------- NOTIFY sip:101@192.168.1.123:5062 SIP/2.0 Via: SIP/2.0/UDP 45.45.45.45;branch=z9hG4bKd16c.03b5bc97000000000000000000000000.0 To: sip:101@45.45.45.45 sip:101@45.45.45.45;tag=1366853594 From: sip:104@45.45.45.45 sip:104@45.45.45.45;tag=a6a1c5f60faecf035a1ae5b6e96e979a-e6c3 CSeq: 2 NOTIFY Call-ID: 594386350@192.168.1.123mailto:594386350@192.168.1.123 Content-Length: 0 User-Agent: kamailio (5.2.4 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: sip:45.45.45.45:5060;transport=udp sip:45.45.45.45:5060;transport=udp -----------------------------------------------------------------------------------------------------------

When I register the phone with Freeswitch instead and run the same test, the NOTIFY works and I get a much longer NOTIFY message

----------------------------------------------------------------------------------------------------------- NOTIFY sip:100@192.168.1.123:5064 SIP/2.0 Via: SIP/2.0/UDP 66.66.66.66;rport;branch=z9hG4bK1mXej9r2605UB Route: sip:55.55.55.55:5064 sip:55.55.55.55:5064;transport=udp Max-Forwards: 70 From: sip:102@66.66.66.66 sip:102@66.66.66.66;tag=xUoVghM5syHc To: "100" sip:100@66.66.66.66 sip:100@66.66.66.66;tag=1720892352 Call-ID: 2583553127@192.168.1.123mailto:2583553127@192.168.1.123 CSeq: 1178415701 NOTIFY Contact: sip:102@66.66.66.66:5060 sip:102@66.66.66.66:5060 User-Agent: FreeSWITCH-mod_sofia/1.10.1-release-12-f9990221e6~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Event: dialog Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Subscription-State: active;expires=1800 Content-Type: application/dialog-info+xml Content-Length: 149

Should the message coming from Kamailio contain more data or is that not the issue. Should I be including other modules also?

All guidance would be appreciated.

1968

Age (days ago)

1970

Last active (days ago)

sr-users@lists.kamailio.org

4 comments

2 participants

tags (0)

participants (2)

Daniel-Constantin Mierla
Petarr Jones