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@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@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
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@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@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users