BLF+Asterisk+NAT

List overview All Threads
Download

newer

older

Seeing Large Waits

John Bob

23 Apr 2018 23 Apr '18

6:45 p.m.

Phone sends Subscribe Kamailio Responds 202 OK Kamailio Responds with NOTIFY Via: SIP/2.0/TCP 66.66.66.66:5051;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66 <mailto:30041@66.66.66.66>>;tag=48ae253ab7 From: <sip:47701@66.66.66.66 <mailto:47701@66.66.66.66>>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp> Subscription-State: terminated;reason=timeout In that packet I see Subscription-state: terminated;reason=timeout Im not sure what I am missing or misconfigured. Any help would be great. I’ve attached my config. Thanks.

Attachments:

attachment.html (text/html — 4.1 KB)
kamailio.cfg (application/octet-stream — 27.5 KB)
attachment.html (text/html — 311 bytes)

Show replies by date

Charles Chance

24 Apr 24 Apr

8:06 a.m.

...

Phone sends Subscribe Kamailio Responds 202 OK Kamailio Responds with NOTIFY Via: SIP/2.0/TCP 66.66.66.66:5051;branch=z9hG4bKfe3e. e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66>;tag=48ae253ab7 From: <sip:47701@66.66.66.66>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp> Subscription-State: terminated;reason=timeout In that packet I see Subscription-state: terminated;reason=timeout Im not sure what I am missing or misconfigured. Any help would be great. I’ve attached my config. Thanks. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB.

John Bob

1:13 p.m.

...

On Apr 24, 2018, at 5:06 AM, Charles Chance <charles.chance(a)sipcentric.com> wrote: Hello, In order for someone to help, you'll need to provide a trace which also includes the SUBSCRIBE and OK - the NOTIFY alone is not enough to understand what is happening here. Cheers, Charles On 23 April 2018 at 23:45, John Bob <preger604(a)gmail.com <mailto:preger604@gmail.com>> wrote: Phone sends Subscribe Kamailio Responds 202 OK Kamailio Responds with NOTIFY Via: SIP/2.0/TCP 66.66.66.66:5051;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66 <mailto:30041@66.66.66.66>>;tag=48ae253ab7 From: <sip:47701@66.66.66.66 <mailto:47701@66.66.66.66>>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp <>> Subscription-State: terminated;reason=timeout In that packet I see Subscription-state: terminated;reason=timeout Im not sure what I am missing or misconfigured. Any help would be great. I’ve attached my config. Thanks. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>

Charles Chance

1:43 p.m.

How long after the OK is the NOTIFY sent? Cheers, Charles On Tue, 24 Apr 2018 at 18:15, John Bob <preger604(a)gmail.com> wrote:

...

;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2

Call-ID: 1493ef52c41b6c1a CSeq: 674537542 SUBSCRIBE Expires: 30 Contact: <sip:192.168.1.30;transport=udp> Server: kamailio (5.1.2 (x86_64/linux)) Content-Length: 0 Via: SIP/2.0/TCP 66.66.66.66:5051 ;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66>;tag=48ae253ab7 From: <sip:47701@66.66.66.66>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp> Subscription-State: terminated;reason=timeout Accept: application/dialog-info+xml, application/rlmi+xml, multipart/related Via: SIP/2.0/TCP 66.66.66.66:5051 ;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 From: <sip:47701@66.66.66.66

;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2

To: <sip:30041@66.66.66.66>;tag=48ae253ab7 Call-ID: 1493ef52c41b6c1a CSeq: 2 NOTIFY Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE Allow-Events: refer Server: Vtech Vesa VSP726 2.0.2.0-0 Supported: eventlist, join, replaces, sdp-anat Content-Length: 0 On Apr 24, 2018, at 5:06 AM, Charles Chance <charles.chance(a)sipcentric.com> wrote: Hello, In order for someone to help, you'll need to provide a trace which also includes the SUBSCRIBE and OK - the NOTIFY alone is not enough to understand what is happening here. Cheers, Charles On 23 April 2018 at 23:45, John Bob <preger604(a)gmail.com> wrote:

Phone sends Subscribe Kamailio Responds 202 OK Kamailio Responds with NOTIFY Via: SIP/2.0/TCP 66.66.66.66:5051 ;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66>;tag=48ae253ab7 From: <sip:47701@66.66.66.66>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp> Subscription-State: terminated;reason=timeout In that packet I see Subscription-state: terminated;reason=timeout Im not sure what I am missing or misconfigured. Any help would be great. I’ve attached my config. Thanks. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- *Charles Chance* Managing Director t. 0330 120 1200 m. 07932 063 891 -- Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB.

John Bob

2:19 p.m.

Hi, The NOTIFY is sent 40seconds after the OK. On Tue, Apr 24, 2018 at 10:44 AM Charles Chance < charles.chance(a)sipcentric.com> wrote:

...

How long after the OK is the NOTIFY sent? Cheers, Charles On Tue, 24 Apr 2018 at 18:15, John Bob <preger604(a)gmail.com> wrote:

;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2

To: <sip:30041@66.66.66.66>;tag=48ae253ab7 Call-ID: 1493ef52c41b6c1a CSeq: 2 NOTIFY Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE Allow-Events: refer Server: Vtech Vesa VSP726 2.0.2.0-0 Supported: eventlist, join, replaces, sdp-anat Content-Length: 0 On Apr 24, 2018, at 5:06 AM, Charles Chance < charles.chance(a)sipcentric.com> wrote: Hello, In order for someone to help, you'll need to provide a trace which also includes the SUBSCRIBE and OK - the NOTIFY alone is not enough to understand what is happening here. Cheers, Charles On 23 April 2018 at 23:45, John Bob <preger604(a)gmail.com> wrote:

Phone sends Subscribe Kamailio Responds 202 OK Kamailio Responds with NOTIFY Via: SIP/2.0/TCP 66.66.66.66:5051 ;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66>;tag=48ae253ab7 From: <sip:47701@66.66.66.66>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp> Subscription-State: terminated;reason=timeout In that packet I see Subscription-state: terminated;reason=timeout Im not sure what I am missing or misconfigured. Any help would be great. I’ve attached my config. Thanks. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- *Charles Chance* Managing Director t. 0330 120 1200 m. 07932 063 891 Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Charles Chance

5:02 p.m.

It that case, it is completely expected if the UA does not renew the subscription before expiry (which in your initial SUBSCRIBE is set to 30 seconds). I would suggest trying to establish why the handset is not re-subscribing within the expiry time - could be settings, could be router/NAT/firewall related. Either way, your Kamailio config appears to be OK. Cheers, Charles On Tue, 24 Apr 2018 at 19:21, John Bob <preger604(a)gmail.com> wrote:

...

Hi, The NOTIFY is sent 40seconds after the OK. On Tue, Apr 24, 2018 at 10:44 AM Charles Chance < charles.chance(a)sipcentric.com> wrote:

How long after the OK is the NOTIFY sent? Cheers, Charles On Tue, 24 Apr 2018 at 18:15, John Bob <preger604(a)gmail.com> wrote:

;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2

To: <sip:30041@66.66.66.66>;tag=48ae253ab7 Call-ID: 1493ef52c41b6c1a CSeq: 2 NOTIFY Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE Allow-Events: refer Server: Vtech Vesa VSP726 2.0.2.0-0 Supported: eventlist, join, replaces, sdp-anat Content-Length: 0 On Apr 24, 2018, at 5:06 AM, Charles Chance < charles.chance(a)sipcentric.com> wrote: Hello, In order for someone to help, you'll need to provide a trace which also includes the SUBSCRIBE and OK - the NOTIFY alone is not enough to understand what is happening here. Cheers, Charles On 23 April 2018 at 23:45, John Bob <preger604(a)gmail.com> wrote:

Phone sends Subscribe Kamailio Responds 202 OK Kamailio Responds with NOTIFY Via: SIP/2.0/TCP 66.66.66.66:5051 ;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66>;tag=48ae253ab7 From: <sip:47701@66.66.66.66>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp> Subscription-State: terminated;reason=timeout In that packet I see Subscription-state: terminated;reason=timeout Im not sure what I am missing or misconfigured. Any help would be great. I’ve attached my config. Thanks. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

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

John Bob

2 May 2 May

3:03 p.m.

Hi, I extended my the phone expiry time. When I check the packet capture there is no Message Body. I do see this in the logs: /usr/sbin/kamailio[17853]: {2 2 NOTIFY 6950e81414240934} ERROR: presence [subscribe.c:502]: delete_subs(): Failed to delete subscription from memory [slot: 360 ev: sip:47701@66.66.66. <mailto:47701@66.199.170.144>66 <mailto:47701@66.199.170.144>.66 <mailto:47701@66.199.170.144>.66 <mailto:47701@66.199.170.144> pu: dialog ci: 6950e81414240934 ft: 2426440def tt: 00c39aabf419ddeab4250cd65af8ef90-b25d]

...

On Apr 24, 2018, at 2:02 PM, Charles Chance <charles.chance(a)sipcentric.com> wrote: It that case, it is completely expected if the UA does not renew the subscription before expiry (which in your initial SUBSCRIBE is set to 30 seconds). I would suggest trying to establish why the handset is not re-subscribing within the expiry time - could be settings, could be router/NAT/firewall related. Either way, your Kamailio config appears to be OK. Cheers, Charles On Tue, 24 Apr 2018 at 19:21, John Bob <preger604(a)gmail.com <mailto:preger604@gmail.com>> wrote: Hi, The NOTIFY is sent 40seconds after the OK. On Tue, Apr 24, 2018 at 10:44 AM Charles Chance <charles.chance(a)sipcentric.com <mailto:charles.chance@sipcentric.com>> wrote: How long after the OK is the NOTIFY sent? Cheers, Charles On Tue, 24 Apr 2018 at 18:15, John Bob <preger604(a)gmail.com <mailto:preger604@gmail.com>> wrote: Hi Charles, My bad. Here is the the full trace Accept: application/dialog-info+xml, application/rlmi+xml, multipart/related Via: SIP/2.0/TCP 192.168.1.154;branch=z9hG4bKb4503c75368818dfc.639d98ef5fa771345;rport Route: <sip:66.66.66.66:5051;lr <>> Max-Forwards: 70 From: "3004" <sip:30041@66.66.66.66 <>>;tag=48ae253ab7 To: <sip:47701@66.66.66.66:5051 <>> SIP to address: sip:47701@66.66.66.66:5051 <> Call-ID: 1493ef52c41b6c1a CSeq: 674537542 SUBSCRIBE Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE Allow-Events: refer Contact: <sip:30041@192.168.1.154;transport=tcp <>> Event: dialog Expires: 30 Supported: eventlist, join, replaces, sdp-anat User-Agent: Vtech Vesa VSP726 2.0.2.0-0 Content-Length: 0 Via: SIP/2.0/TCP 192.168.1.154;branch=z9hG4bKb4503c75368818dfc.639d98ef5fa771345;rport=6177;received=209.205.212.102 From: "3004" <sip:30041@66.66.66.66 <>>;tag=48ae253ab7 To: <sip:47701@66.66.66.66:5051 <>>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 Call-ID: 1493ef52c41b6c1a CSeq: 674537542 SUBSCRIBE Expires: 30 Contact: <sip:192.168.1.30;transport=udp <>> Server: kamailio (5.1.2 (x86_64/linux)) Content-Length: 0 Via: SIP/2.0/TCP 66.66.66.66:5051;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66 <>>;tag=48ae253ab7 From: <sip:47701@66.66.66.66 <>>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp <>> Subscription-State: terminated;reason=timeout Accept: application/dialog-info+xml, application/rlmi+xml, multipart/related Via: SIP/2.0/TCP 66.66.66.66:5051;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 From: <sip:47701@66.66.66.66 <>>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 To: <sip:30041@66.66.66.66 <>>;tag=48ae253ab7 Call-ID: 1493ef52c41b6c1a CSeq: 2 NOTIFY Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE Allow-Events: refer Server: Vtech Vesa VSP726 2.0.2.0-0 Supported: eventlist, join, replaces, sdp-anat Content-Length: 0

On Apr 24, 2018, at 5:06 AM, Charles Chance <charles.chance(a)sipcentric.com <mailto:charles.chance@sipcentric.com>> wrote:

Hello, In order for someone to help, you'll need to provide a trace which also includes the SUBSCRIBE and OK - the NOTIFY alone is not enough to understand what is happening here. Cheers, Charles On 23 April 2018 at 23:45, John Bob <preger604(a)gmail.com <mailto:preger604@gmail.com>> wrote: Phone sends Subscribe Kamailio Responds 202 OK Kamailio Responds with NOTIFY Via: SIP/2.0/TCP 66.66.66.66:5051;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66 <mailto:30041@66.66.66.66>>;tag=48ae253ab7 From: <sip:47701@66.66.66.66 <mailto:47701@66.66.66.66>>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp <>> Subscription-State: terminated;reason=timeout In that packet I see Subscription-state: terminated;reason=timeout Im not sure what I am missing or misconfigured. Any help would be great. I’ve attached my config. Thanks. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>

Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB.

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

Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> -- Charles Chance Managing Director t. 0330 120 1200 m. 07932 063 891 Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> -- Charles Chance Managing Director t. 0330 120 1200 m. 07932 063 891 Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Charles Chance

3 May 3 May

1:37 a.m.

Hi, On Wed, 2 May 2018 at 20:06, John Bob <preger604(a)gmail.com> wrote:

...

Hi, I extended my the phone expiry time. When I check the packet capture there is no Message Body.

Where are you expecting to see a message body? In the scenario you have described I would not expect to see a message body either.

...

I do see this in the logs: /usr/sbin/kamailio[17853]: {2 2 NOTIFY 6950e81414240934} ERROR: presence [subscribe.c:502]: delete_subs(): Failed to delete subscription from memory [slot: 360 ev: sip:47701@66. <47701(a)66.199.170.144>66 <47701(a)66.199.170.144>.66 <47701(a)66.199.170.144>.66 <47701(a)66.199.170.144> pu: dialog ci: 6950e81414240934 ft: 2426440def tt: 00c39aabf419ddeab4250cd65af8ef90-b25d]

It may be semi-related but it is not the cause of the subscription timing out. Do you see the handset ever try to renew its subscription before the expiry time? If not, that is where you should be looking. If you’re able to send a full pcap (privately if necessary) then I’ll be happy to take a look for you. Cheers, Charles

...

Hi, The NOTIFY is sent 40seconds after the OK. On Tue, Apr 24, 2018 at 10:44 AM Charles Chance < charles.chance(a)sipcentric.com> wrote:

How long after the OK is the NOTIFY sent? Cheers, Charles On Tue, 24 Apr 2018 at 18:15, John Bob <preger604(a)gmail.com> wrote:

Hi Charles, My bad. Here is the the full trace Accept: application/dialog-info+xml, application/rlmi+xml, multipart/related Via: SIP/2.0/TCP 192.168.1.154;branch=z9hG4bKb4503c75368818dfc.639d98ef5fa771345;rport Route: <sip:66.66.66.66:5051;lr> Max-Forwards: 70 From: "3004" <sip:30041@66.66.66.66>;tag=48ae253ab7 To: <sip:47701@66.66.66.66:5051> SIP to address: sip:47701@66.66.66.66:5051 Call-ID: 1493ef52c41b6c1a CSeq: 674537542 SUBSCRIBE Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE Allow-Events: refer Contact: <sip:30041@192.168.1.154;transport=tcp> Event: dialog Expires: 30 Supported: eventlist, join, replaces, sdp-anat User-Agent: Vtech Vesa VSP726 2.0.2.0-0 Content-Length: 0 Via: SIP/2.0/TCP 192.168.1.154;branch=z9hG4bKb4503c75368818dfc.639d98ef5fa771345;rport=6177;received=209.205.212.102 From: "3004" <sip:30041@66.66.66.66>;tag=48ae253ab7 To: <sip:47701@66.66.66.66:5051 >;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 Call-ID: 1493ef52c41b6c1a CSeq: 674537542 SUBSCRIBE Expires: 30 Contact: <sip:192.168.1.30;transport=udp> Server: kamailio (5.1.2 (x86_64/linux)) Content-Length: 0 Via: SIP/2.0/TCP 66.66.66.66:5051 ;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 To: <sip:30041@66.66.66.66>;tag=48ae253ab7 From: <sip:47701@66.66.66.66>;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 CSeq: 2 NOTIFY Call-ID: 1493ef52c41b6c1a Content-Length: 0 User-Agent: kamailio (5.1.2 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:192.168.1.30;transport=udp> Subscription-State: terminated;reason=timeout Accept: application/dialog-info+xml, application/rlmi+xml, multipart/related Via: SIP/2.0/TCP 66.66.66.66:5051 ;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 From: <sip:47701@66.66.66.66 >;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 To: <sip:30041@66.66.66.66>;tag=48ae253ab7 Call-ID: 1493ef52c41b6c1a CSeq: 2 NOTIFY Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE Allow-Events: refer Server: Vtech Vesa VSP726 2.0.2.0-0 Supported: eventlist, join, replaces, sdp-anat Content-Length: 0 On Apr 24, 2018, at 5:06 AM, Charles Chance < charles.chance(a)sipcentric.com> wrote: Hello, In order for someone to help, you'll need to provide a trace which also includes the SUBSCRIBE and OK - the NOTIFY alone is not enough to understand what is happening here. Cheers, Charles On 23 April 2018 at 23:45, John Bob <preger604(a)gmail.com> wrote: > Phone sends Subscribe > Kamailio Responds 202 OK > Kamailio Responds with NOTIFY > > Via: SIP/2.0/TCP 66.66.66.66:5051 > ;branch=z9hG4bKfe3e.e4fedb84000000000000000000000000.0 > To: <sip:30041@66.66.66.66>;tag=48ae253ab7 > From: <sip:47701@66.66.66.66 > >;tag=00c39aabf419ddeab4250cd65af8ef90-6fb2 > CSeq: 2 NOTIFY > Call-ID: 1493ef52c41b6c1a > Content-Length: 0 > User-Agent: kamailio (5.1.2 (x86_64/linux)) > Max-Forwards: 70 > Event: dialog > Contact: <sip:192.168.1.30;transport=udp> > Subscription-State: terminated;reason=timeout > > In that packet I see Subscription-state: terminated;reason=timeout > > > Im not sure what I am missing or misconfigured. Any help would be > great. I’ve attached my config. > > Thanks. > > > > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users(a)lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

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

2481

days inactive

2491

days old

sr-users@lists.kamailio.org

Manage subscription

7 comments

2 participants

tags (0)

participants (2)

Charles Chance
John Bob