<div dir="ltr"><div dir="ltr">On Sat, Aug 14, 2021 at 10:36 AM Reuben Farrelly <<a href="mailto:reuben-asterisk-users@reub.net">reuben-asterisk-users@reub.net</a>> wrote:</div><div dir="ltr"><br></div><div><snip></div><div dir="ltr"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Logs show:<br>
<br>
Aug 14 22:54:41] ERROR[26606] res_pjsip.c: Could not create dialog with<br>
endpoint 1001. Invalid URI (PJSIP_EINVALIDURI)<br>
[Aug 14 22:54:41] WARNING[26606] res_pjsip_pubsub.c: Unable to create<br>
dialog for SIP subscription<br>
[Aug 14 22:54:41] WARNING[26606] res_pjsip_pubsub.c: Failed recreating<br>
'1001' subscription: Could not create subscription tree.<br>
[Aug 14 22:54:41] ERROR[26606] res_pjsip.c: Could not create dialog with<br>
endpoint 1002. Invalid URI (PJSIP_EINVALIDURI)<br>
[Aug 14 22:54:41] WARNING[26606] res_pjsip_pubsub.c: Unable to create<br>
dialog for SIP subscription<br>
[Aug 14 22:54:41] WARNING[26606] res_pjsip_pubsub.c: Failed recreating<br>
'1002' subscription: Could not create subscription tree.<br>
[Aug 14 22:54:41] ERROR[26606] res_pjsip.c: Could not create dialog with<br>
endpoint 1001. Invalid URI (PJSIP_EINVALIDURI)<br>
[Aug 14 22:54:41] WARNING[26606] res_pjsip_pubsub.c: Unable to create<br>
dialog for SIP subscription<br></blockquote><div><br></div><div>Did these occur at startup? If so, it's because generally you can't recreate the subscription to a TCP or TLS based device.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
Debugs show this:<br>
<br>
<--- Received SIP request (628 bytes) from<br>
TCP:[2403:5800:7700:6411::5]:5066 ---><br>
SUBSCRIBE <a>sip:1003@sip.reub.net</a> SIP/2.0<br>
Via: SIP/2.0/TCP [2403:5800:7700:6411::5]:5066;branch=z9hG4bK-8a5f8a6c<br>
From: "Reuben Farrelly's Phone" <<a>sip:1002@sip.reub.net</a>>;tag=96894202b140ddb<br>
To: <<a>sip:1003@sip.reub.net</a>><br>
Call-ID: 1eb5588-6f32a075@2403:5800:7700:6411::5<br>
CSeq: 26191 SUBSCRIBE<br>
Max-Forwards: 70<br>
Contact: "Reuben Farrelly's Phone"<br>
<sip:1002@[2403:5800:7700:6411::5]:5066;transport=tcp><br>
Accept: multipart/related<br>
Accept: application/rlmi+xml<br>
Accept: application/dialog-info+xml<br>
Expires: 1800<br>
Event: dialog<br>
User-Agent: Cisco-CP-8845-3PCC/11.3.4<br>
Content-Length: 0<br>
Supported: replaces, sec-agree, eventlist<br>
<br>
<br>
<--- Transmitting SIP response (538 bytes) to<br>
TCP:[2403:5800:7700:6411::5]:5066 ---><br>
SIP/2.0 401 Unauthorized<br>
Via: SIP/2.0/TCP<br>
[2403:5800:7700:6411::5]:5066;rport=5066;received=2403:5800:7700:6411::5;branch=z9hG4bK-8a5f8a6c<br>
Call-ID: 1eb5588-6f32a075@2403:5800:7700:6411::5<br>
From: "Reuben Farrelly's Phone" <<a>sip:1002@sip.reub.net</a>>;tag=96894202b140ddb<br>
To: <<a>sip:1003@sip.reub.net</a>>;tag=z9hG4bK-8a5f8a6c<br>
CSeq: 26191 SUBSCRIBE<br>
WWW-Authenticate: Digest<br>
realm="asterisk",nonce="x",opaque="54aa5d4217da2b11",algorithm=md5,qop="auth"<br>
Server: Asterisk PBX 18.6.0<br>
Content-Length:  0<br>
<br>
<br>
<--- Received SIP request (887 bytes) from<br>
TCP:[2403:5800:7700:6411::5]:5066 ---><br>
SUBSCRIBE <a>sip:1003@sip.reub.net</a> SIP/2.0<br>
Via: SIP/2.0/TCP [2403:5800:7700:6411::5]:5066;branch=z9hG4bK-e18fdc9c<br>
From: "Reuben Farrelly's Phone" <<a>sip:1002@sip.reub.net</a>>;tag=96894202b140ddb<br>
To: <<a>sip:1003@sip.reub.net</a>><br>
Call-ID: 1eb5588-6f32a075@2403:5800:7700:6411::5<br>
CSeq: 26192 SUBSCRIBE<br>
Max-Forwards: 70<br>
Authorization: Digest<br>
username="1002",realm="asterisk",nonce="x",uri="<a>sip:1003@sip.reub.net</a>",algorithm=MD5,response="x",opaque="54aa5d4217da2b11",qop=auth,nc=00000001,cnonce="80ff50e8"<br>
Contact: "Reuben Farrelly's Phone"<br>
<sip:1002@[2403:5800:7700:6411::5]:5066;transport=tcp><br>
Accept: multipart/related<br>
Accept: application/rlmi+xml<br>
Accept: application/dialog-info+xml<br>
Expires: 1800<br>
Event: dialog<br>
User-Agent: Cisco-CP-8845-3PCC/11.3.4<br>
Content-Length: 0<br>
Supported: replaces, sec-agree, eventlist<br>
<br>
<br>
<--- Transmitting SIP response (637 bytes) to<br>
TCP:[2403:5800:7700:6411::5]:5066 ---><br>
SIP/2.0 200 OK<br>
Via: SIP/2.0/TCP<br>
[2403:5800:7700:6411::5]:5066;rport=5066;received=2403:5800:7700:6411::5;branch=z9hG4bK-e18fdc9c<br>
Call-ID: 1eb5588-6f32a075@2403:5800:7700:6411::5<br>
From: "Reuben Farrelly's Phone" <<a>sip:1002@sip.reub.net</a>>;tag=96894202b140ddb<br>
To: <<a>sip:1003@sip.reub.net</a>>;tag=5e48d14e-efda-4f73-b1e1-7dcbbe12e7c4<br>
CSeq: 26192 SUBSCRIBE<br>
Expires: 1800<br>
Contact: <sip:[2403:5800:7700:6410::25]:5060;transport=TCP><br>
Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE,<br>
CANCEL, UPDATE, PRACK, MESSAGE, REFER<br>
Supported: 100rel, timer, replaces, norefersub<br>
Server: Asterisk PBX 18.6.0<br>
Content-Length:  0<br>
<br>
<br>
<--- Transmitting SIP request (949 bytes) to<br>
TCP:[2403:5800:7700:6411::5]:5066 ---><br>
NOTIFY sip:1002@[2403:5800:7700:6411::5]:5066;transport=tcp SIP/2.0<br>
Via: SIP/2.0/TCP<br>
[2403:5800:7700:6410::25]:5060;rport;branch=z9hG4bKPj21e9c122-5302-4c39-bee5-9ea0d97fd29c;alias<br>
From: <<a>sip:1003@sip.reub.net</a>>;tag=5e48d14e-efda-4f73-b1e1-7dcbbe12e7c4<br>
To: "Reuben Farrelly's Phone" <<a>sip:1002@sip.reub.net</a>>;tag=96894202b140ddb<br>
Contact: <sip:[2403:5800:7700:6410::25]:5060;transport=TCP><br>
Call-ID: 1eb5588-6f32a075@2403:5800:7700:6411::5<br>
CSeq: 8775 NOTIFY<br>
Event: dialog<br>
Subscription-State: active;expires=1799<br>
Allow-Events: message-summary, presence, dialog, refer<br>
Max-Forwards: 70<br>
User-Agent: Asterisk PBX 18.6.0<br>
Content-Type: application/dialog-info+xml<br>
Content-Length:   258<br>
<br>
<?xml version="1.0" encoding="UTF-8"?><br>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0"<br>
state="full" entity="sip:1003@[2403:5800:7700:6410::25]:5060;transport=TCP"><br>
 <dialog id="1003"><br>
  <state>terminated</state><br>
 </dialog><br>
</dialog-info><br>
<br>
<--- Received SIP response (396 bytes) from<br>
TCP:[2403:5800:7700:6411::5]:5066 ---><br>
SIP/2.0 200 OK<br>
To: "Reuben Farrelly's Phone" <<a>sip:1002@sip.reub.net</a>>;tag=96894202b140ddb<br>
From: <<a>sip:1003@sip.reub.net</a>>;tag=5e48d14e-efda-4f73-b1e1-7dcbbe12e7c4<br>
Call-ID: 1eb5588-6f32a075@2403:5800:7700:6411::5<br>
CSeq: 8775 NOTIFY<br>
Via: SIP/2.0/TCP<br>
[2403:5800:7700:6410::25]:5060;branch=z9hG4bKPj21e9c122-5302-4c39-bee5-9ea0d97fd29c;alias<br>
Server: Cisco-CP-8845-3PCC/11.3.4<br>
Content-Length: 0<br>
<br>
<br>
The <state>terminated><state> line stands out as something I would not<br>
expect.<br></blockquote><div><br></div><div>This appears to be a perfectly normal subscription. For the NOTIFY It means that the device is not in use. The dialog-info+xml type isn't exactly for presence, it's to show you calls with the device. We feed hint status information in and construct a packet, as best we can, to represent the hint status. You'd need to provide a full SIP trace showing not just the initial subscription, but also when it should have changed to in use.</div></div><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-family:tahoma,sans-serif"><font color="#073763">Joshua C. Colp</font></div><div style="font-family:tahoma,sans-serif"><font color="#073763">Asterisk Technical Lead</font></div><div style="font-family:tahoma,sans-serif"><font color="#073763">Sangoma Technologies</font></div><div style="font-family:tahoma,sans-serif"><font color="#073763">Check us out at <a href="http://www.sangoma.com" target="_blank">www.sangoma.com</a> and <a href="http://www.asterisk.org" target="_blank">www.asterisk.org</a></font><br></div></div></div></div></div></div></div></div></div></div></div>