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.