Sip sms not working

asterisk
configuration
bug
Tags: #<Tag:0x00007f4f42fa40b8> #<Tag:0x00007f4f42fa6ef8> #<Tag:0x00007f4f42fa3f78>

(Rana hashem) #1

hi :smile:
in my local network i cannot send sip messages from line phone smartphone to line phone desktop :disappointed_relieved:

freepbx 15 bistro
asterisk 17
centos 7

sip.config
accept_outofcall_message = yes
outofcall_message_context = messages
auth_message_requests = no

extensions_custom.conf
[astsms]
;Deliver to local 3-digit extension
exten => _XXX,1,MessageSend(sip:${EXTEN},${MESSAGE(from)})
same => n,Hangup()

[root@freepbx ~]# tail -f /var/log/asterisk/full
[2021-06-18 13:39:12] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:101,sip:100@192.168.1.4”) in new stack
[2021-06-18 13:39:12] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-18 13:39:12] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 101, 2) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-18 13:39:22] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:100,sip:101@192.168.1.6”) in new stack
[2021-06-18 13:39:22] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-18 13:39:22] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 100, 2) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-18 13:39:26] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:100,sip:101@192.168.1.6”) in new stack
[2021-06-18 13:39:26] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-18 13:39:26] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 100, 2) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-18 13:39:37] VERBOSE[4697] asterisk.c: Remote UNIX connection disconnected
[2021-06-18 13:39:42] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:100,sip:101@192.168.1.6”) in new stack
[2021-06-18 13:39:42] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-18 13:39:42] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 100, 2) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-18 13:39:46] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:101,sip:100@192.168.1.4”) in new stack
[2021-06-18 13:39:46] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-18 13:39:46] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 101, 2) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-18 13:39:50] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:100,sip:101@192.168.1.6”) in new stack
[2021-06-18 13:39:50] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-18 13:39:50] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 100, 2) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-18 13:39:53] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:101,sip:100@192.168.1.4”) in new stack
[2021-06-18 13:39:53] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-18 13:39:53] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 101, 2) exited non-zero on ‘Message/ast_msg_queue’


(David55) #2

The log shows a successful send. I think you will need to provide the protocol logs produced by sip set debug on.


(Rana hashem) #3

Really destroying SIP dialog ‘1c15778527ea35522637eeb767e847bb@192.168.1.6:5060’ Method: OPTIONS

<— SIP read from UDP:192.168.1.4:5060 —>
MESSAGE sip:101@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.n8PbiBOdC;rport
From: sip:100@192.168.1.4;tag=5qoR-LSNa
To: sip:101@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: EmPZEZ-bTw
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:23 GMT
Content-Encoding: deflate
Content-Type: message/imdn+xml
Content-Length: 208
Priority: non-urgent
User-Agent: Linphone Desktop/4.2.5 (Windows 10 Version 2009, Qt 5.14.2) LinphoneCore/4.4.19

x▒m▒▒n!▒c.kֈũ▒N▒󰐖▒▒▒(▒▒▒"V▒h▒▒9▒1▒▒▒▒ϸ▒\q▒b▒D▒5d▒.▒▒▒▒fJZw▒Z1.+%'kr H▒m▒▒u▒=▒▒\iz▒▒~\▒5%▒殑▒!▒ dH2\▒,A(sR▒▒▒▒▒▒ULj#B▒▒▒▒▒&▒{.▒N0 ▒▒▒,▒▒▒▒▒a▒s6!▒▒▒֞S▒3k▒C▒▒▒▒▒▒▒▒?▒▒H
<------------->
— (14 headers 2 lines) —
Sending to 192.168.1.4:5060 (no NAT)
Receiving message!

<— Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.n8PbiBOdC;received=192.168.1.4;rport=5060
From: sip:100@192.168.1.4;tag=5qoR-LSNa
To: sip:101@192.168.1.6;tag=as5873c72c
Call-ID: EmPZEZ-bTw
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘EmPZEZ-bTw’ in 32000 ms (Method: MESSAGE)

<— SIP read from UDP:192.168.1.4:5060 —>
MESSAGE sip:101@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.SRpZsZI-b;rport
From: sip:100@192.168.1.4;tag=801k6GIOo
To: sip:101@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: wuYPA7dlan
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:25 GMT
Content-Type: application/im-iscomposing+xml
Content-Length: 170
Priority: non-urgent
Expires: 0
User-Agent: Linphone Desktop/4.2.5 (Windows 10 Version 2009, Qt 5.14.2) LinphoneCore/4.4.19

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>active60

<------------->
— (14 headers 1 lines) —
Sending to 192.168.1.4:5060 (no NAT)
Receiving message!

<— Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.SRpZsZI-b;received=192.168.1.4;rport=5060
From: sip:100@192.168.1.4;tag=801k6GIOo
To: sip:101@192.168.1.6;tag=as3780dbc0
Call-ID: wuYPA7dlan
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘wuYPA7dlan’ in 32000 ms (Method: MESSAGE)

<— SIP read from UDP:192.168.1.4:5060 —>
MESSAGE sip:101@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.IxfS8CtYn;rport
From: sip:100@192.168.1.4;tag=hxtJFh0j~
To: sip:101@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: N0SzvtPmMc
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:27 GMT
Content-Type: text/plain
Content-Length: 7
User-Agent: Linphone Desktop/4.2.5 (Windows 10 Version 2009, Qt 5.14.2) LinphoneCore/4.4.19

uuuuuuu
<------------->
— (12 headers 1 lines) —
Sending to 192.168.1.4:5060 (no NAT)
Receiving message!
Looking for 101 in messages (domain 192.168.1.6)

<— Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.IxfS8CtYn;received=192.168.1.4;rport=5060
From: sip:100@192.168.1.4;tag=hxtJFh0j~
To: sip:101@192.168.1.6;tag=as7bb24a44
Call-ID: N0SzvtPmMc
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘N0SzvtPmMc’ in 32000 ms (Method: MESSAGE)

<— SIP read from UDP:192.168.1.4:5060 —>
MESSAGE sip:101@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.NJ5ZRh4A3;rport
From: sip:100@192.168.1.4;tag=xhW4CceKu
To: sip:101@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: -R-DbEz0bI
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:27 GMT
Content-Type: application/im-iscomposing+xml
Content-Length: 170
Priority: non-urgent
Expires: 0
User-Agent: Linphone Desktop/4.2.5 (Windows 10 Version 2009, Qt 5.14.2) LinphoneCore/4.4.19

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>active60

<------------->
— (14 headers 1 lines) —
Sending to 192.168.1.4:5060 (no NAT)
Receiving message!

<— Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.NJ5ZRh4A3;received=192.168.1.4;rport=5060
From: sip:100@192.168.1.4;tag=xhW4CceKu
To: sip:101@192.168.1.6;tag=as2bc487bd
Call-ID: -R-DbEz0bI
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘-R-DbEz0bI’ in 32000 ms (Method: MESSAGE)

<— SIP read from UDP:192.168.1.4:5060 —>

<------------->

<— SIP read from UDP:192.168.1.4:5060 —>
MESSAGE sip:101@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.GqCXtyKFt;rport
From: sip:100@192.168.1.4;tag=zazYggqMK
To: sip:101@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: NsuY7Bur9O
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:28 GMT
Content-Type: text/plain
Content-Length: 5
User-Agent: Linphone Desktop/4.2.5 (Windows 10 Version 2009, Qt 5.14.2) LinphoneCore/4.4.19

jjjjj
<------------->
— (12 headers 1 lines) —
Sending to 192.168.1.4:5060 (no NAT)
Receiving message!
Looking for 101 in messages (domain 192.168.1.6)

<— Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.GqCXtyKFt;received=192.168.1.4;rport=5060
From: sip:100@192.168.1.4;tag=zazYggqMK
To: sip:101@192.168.1.6;tag=as362a057d
Call-ID: NsuY7Bur9O
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘NsuY7Bur9O’ in 32000 ms (Method: MESSAGE)
Reliably Transmitting (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK5b1ef39a
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as23a9606b
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 55409b0d61f2b1de585654ea0b0131ab@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:18:33 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


Retransmitting #1 (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK5b1ef39a
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as23a9606b
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 55409b0d61f2b1de585654ea0b0131ab@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:18:33 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


Retransmitting #2 (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK5b1ef39a
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as23a9606b
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 55409b0d61f2b1de585654ea0b0131ab@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:18:33 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


<— SIP read from UDP:192.168.1.150:61003 —>
MESSAGE sip:100@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.u6hDeGrOP;rport
From: sip:101@192.168.1.6;tag=zQ61f9yVs
To: sip:100@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: MiBeLjyJPS
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:34 GMT
Content-Type: application/im-iscomposing+xml
Content-Length: 170
Priority: non-urgent
Expires: 0
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>active60

<------------->
— (14 headers 1 lines) —
Sending to 192.168.1.150:61003 (no NAT)
Receiving message!

<— Transmitting (no NAT) to 192.168.1.150:61003 —>
SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.u6hDeGrOP;received=192.168.1.150;rport=61003
From: sip:101@192.168.1.6;tag=zQ61f9yVs
To: sip:100@192.168.1.6;tag=as706a4bc5
Call-ID: MiBeLjyJPS
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘MiBeLjyJPS’ in 32000 ms (Method: MESSAGE)

<— SIP read from UDP:192.168.1.150:61003 —>
MESSAGE sip:100@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.u6hDeGrOP;rport
From: sip:101@192.168.1.6;tag=zQ61f9yVs
To: sip:100@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: MiBeLjyJPS
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:34 GMT
Content-Type: application/im-iscomposing+xml
Content-Length: 170
Priority: non-urgent
Expires: 0
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>active60

<------------->
— (14 headers 1 lines) —

<— Transmitting (no NAT) to 192.168.1.150:61003 —>
SIP/2.0 202 Accepted
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.u6hDeGrOP;received=192.168.1.150;rport=61003
From: sip:101@192.168.1.6;tag=zQ61f9yVs
To: sip:100@192.168.1.6;tag=as706a4bc5
Call-ID: MiBeLjyJPS
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>

<— SIP read from UDP:192.168.1.150:61003 —>
MESSAGE sip:100@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.4DzmUU9M~;rport
From: sip:101@192.168.1.6;tag=YsaW8XKBL
To: sip:100@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: lGvvMEhhgD
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:35 GMT
Content-Type: text/plain
Content-Length: 8
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14

زننن
<------------->
— (12 headers 1 lines) —
Sending to 192.168.1.150:61003 (no NAT)
Receiving message!
Looking for 100 in messages (domain 192.168.1.6)

<— Transmitting (no NAT) to 192.168.1.150:61003 —>
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.4DzmUU9M~;received=192.168.1.150;rport=61003
From: sip:101@192.168.1.6;tag=YsaW8XKBL
To: sip:100@192.168.1.6;tag=as35c19974
Call-ID: lGvvMEhhgD
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘lGvvMEhhgD’ in 32000 ms (Method: MESSAGE)

<— SIP read from UDP:192.168.1.150:61003 —>
MESSAGE sip:100@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.4DzmUU9M~;rport
From: sip:101@192.168.1.6;tag=YsaW8XKBL
To: sip:100@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: lGvvMEhhgD
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:35 GMT
Content-Type: text/plain
Content-Length: 8
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14

زننن
<------------->
— (12 headers 1 lines) —

<— Transmitting (no NAT) to 192.168.1.150:61003 —>
SIP/2.0 202 Accepted
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.4DzmUU9M~;received=192.168.1.150;rport=61003
From: sip:101@192.168.1.6;tag=YsaW8XKBL
To: sip:100@192.168.1.6;tag=as35c19974
Call-ID: lGvvMEhhgD
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>

<— SIP read from UDP:192.168.1.150:61003 —>
MESSAGE sip:100@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.u6hDeGrOP;rport
From: sip:101@192.168.1.6;tag=zQ61f9yVs
To: sip:100@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: MiBeLjyJPS
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:34 GMT
Content-Type: application/im-iscomposing+xml
Content-Length: 170
Priority: non-urgent
Expires: 0
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>active60

<------------->
— (14 headers 1 lines) —

<— Transmitting (no NAT) to 192.168.1.150:61003 —>
SIP/2.0 202 Accepted
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.u6hDeGrOP;received=192.168.1.150;rport=61003
From: sip:101@192.168.1.6;tag=zQ61f9yVs
To: sip:100@192.168.1.6;tag=as706a4bc5
Call-ID: MiBeLjyJPS
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>

<— SIP read from UDP:192.168.1.150:61003 —>
MESSAGE sip:100@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.hHcODK0cT;rport
From: sip:101@192.168.1.6;tag=oETrRsLjg
To: sip:100@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: ZS7CtfmP6m
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:36 GMT
Content-Type: application/im-iscomposing+xml
Content-Length: 170
Priority: non-urgent
Expires: 0
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>active60

<------------->
— (14 headers 1 lines) —
Sending to 192.168.1.150:61003 (no NAT)
Receiving message!

<— Transmitting (no NAT) to 192.168.1.150:61003 —>
SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.hHcODK0cT;received=192.168.1.150;rport=61003
From: sip:101@192.168.1.6;tag=oETrRsLjg
To: sip:100@192.168.1.6;tag=as2a4ebb6e
Call-ID: ZS7CtfmP6m
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘ZS7CtfmP6m’ in 32000 ms (Method: MESSAGE)
Retransmitting #3 (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK5b1ef39a
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as23a9606b
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 55409b0d61f2b1de585654ea0b0131ab@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:18:33 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


<— SIP read from UDP:192.168.1.150:61003 —>
MESSAGE sip:100@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.gd~8ZRY8r;rport
From: sip:101@192.168.1.6;tag=rKrTDu03X
To: sip:100@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: HzaYaDdwIt
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Fri, 18 Jun 2021 15:18:37 GMT
Content-Type: text/plain
Content-Length: 8
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14

للاا
<------------->
— (12 headers 1 lines) —
Sending to 192.168.1.150:61003 (no NAT)
Receiving message!
Looking for 100 in messages (domain 192.168.1.6)

<— Transmitting (no NAT) to 192.168.1.150:61003 —>
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.1.150:61003;branch=z9hG4bK.gd~8ZRY8r;received=192.168.1.150;rport=61003
From: sip:101@192.168.1.6;tag=rKrTDu03X
To: sip:100@192.168.1.6;tag=as6e79b065
Call-ID: HzaYaDdwIt
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘HzaYaDdwIt’ in 32000 ms (Method: MESSAGE)
Retransmitting #4 (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK5b1ef39a
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as23a9606b
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 55409b0d61f2b1de585654ea0b0131ab@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:18:33 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


Really destroying SIP dialog ‘55409b0d61f2b1de585654ea0b0131ab@192.168.1.6:5060’ Method: OPTIONS

<— SIP read from UDP:192.168.1.4:5060 —>

<------------->

<— SIP read from UDP:192.168.1.150:61003 —>

<------------->
Reliably Transmitting (no NAT) to 192.168.1.150:61003:
OPTIONS sip:101@192.168.1.150:61003;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK2b9e2a56
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as061c1e78
To: sip:101@192.168.1.150:61003;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 348b20a01bdd1671727ec1707135cb1f@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:18:41 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


<— SIP read from UDP:192.168.1.150:61003 —>
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK2b9e2a56
From: “Unknown” sip:Unknown@192.168.1.6;tag=as061c1e78
To: sip:101@192.168.1.150:61003;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp;tag=Tm8lr
Call-ID: 348b20a01bdd1671727ec1707135cb1f@192.168.1.6:5060
CSeq: 102 OPTIONS

<------------->
— (6 headers 0 lines) —
Really destroying SIP dialog ‘348b20a01bdd1671727ec1707135cb1f@192.168.1.6:5060’ Method: OPTIONS
freepbxCLI> sip set debug off
SIP Debugging Disabled
== Spawn extension (macro-dial-one, s, 56) exited non-zero on ‘SIP/101-00000002’ in macro ‘dial-one’
== Spawn extension (macro-exten-vm, s, 14) exited non-zero on ‘SIP/101-00000002’ in macro ‘exten-vm’
== Spawn extension (ext-local, 100, 3) exited non-zero on ‘SIP/101-00000002’
== Spawn extension (macro-hangupcall, s, 7) exited non-zero on ‘SIP/101-00000002’ in macro ‘hangupcall’
== Spawn extension (ext-local, h, 1) exited non-zero on ‘SIP/101-00000002’
[2021-06-18 17:19:46] NOTICE[1732]: chan_sip.c:30545 sip_poke_noanswer: Peer ‘101’ is now UNREACHABLE! Last qualify: 873
[2021-06-18 17:20:49] NOTICE[1732]: chan_sip.c:25012 handle_response_peerpoke: Peer ‘101’ is now Reachable. (1045ms / 2000ms)
[2021-06-18 17:22:01] NOTICE[1732]: chan_sip.c:30545 sip_poke_noanswer: Peer ‘101’ is now UNREACHABLE! Last qualify: 976
freepbx
CLI> sip


(Rana hashem) #4

freepbx*CLI> core set verbose 5
Console verbose was 2 and is now 5.
– Channel SIP/101-00000004 left ‘simple_bridge’ basic-bridge <833d49c4-a58e-4b72-96a9-90cae0fc0448>
== Spawn extension (macro-dial-one, s, 56) exited non-zero on ‘SIP/101-00000004’ in macro ‘dial-one’
== Spawn extension (macro-exten-vm, s, 14) exited non-zero on ‘SIP/101-00000004’ in macro ‘exten-vm’
== Spawn extension (ext-local, 100, 3) exited non-zero on ‘SIP/101-00000004’
– Executing [h@ext-local:1] Macro(“SIP/101-00000004”, “hangupcall,”) in new stack
– Executing [s@macro-hangupcall:1] GotoIf(“SIP/101-00000004”, “1?theend”) in new stack
– Goto (macro-hangupcall,s,3)
– Channel SIP/100-00000005 left ‘simple_bridge’ basic-bridge <833d49c4-a58e-4b72-96a9-90cae0fc0448>
– Executing [s@macro-hangupcall:3] ExecIf(“SIP/101-00000004”, “0?Set(CDR(recordingfile)=)”) in new stack
– Executing [s@macro-hangupcall:4] NoOp(“SIP/101-00000004”, "SIP/100-00000005 montior file= ") in new stack
– Executing [s@macro-hangupcall:5] GotoIf(“SIP/101-00000004”, “1?skipagi”) in new stack
– Goto (macro-hangupcall,s,7)
– Executing [s@macro-hangupcall:7] Hangup(“SIP/101-00000004”, “”) in new stack
== Spawn extension (macro-hangupcall, s, 7) exited non-zero on ‘SIP/101-00000004’ in macro ‘hangupcall’
== Spawn extension (ext-local, h, 1) exited non-zero on ‘SIP/101-00000004’


(David55) #5

There is no outbound dialogue and, either your logging doesn’t include the normal verbose output, or the dialplan to handle the message hasn’t been executed this time, even though it was last time.

I presume the content type problem is the use of compression.

I don’t understand why 100 is sometimes found in the message context and sometimes not.


(Rana hashem) #6

what do u men I have extension 100 on desktop linephone and 101 on smartphone and same config tow use them …

sip show debug on …
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:48:40 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


Retransmitting #4 (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK415e318b
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as51251912
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 4848a4b07e56caec0efa2f562334f990@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:48:40 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


Really destroying SIP dialog ‘4848a4b07e56caec0efa2f562334f990@192.168.1.6:5060’ Method: OPTIONS

<— SIP read from UDP:192.168.1.4:5060 —>
INVITE sip:101@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.yAeR3ANAX;rport
From: “omer RIT” sip:100@192.168.1.6;tag=aoHiq91~z
To: sip:101@192.168.1.6
CSeq: 20 INVITE
Call-ID: mWdGgJRu~S
Max-Forwards: 70
Supported: replaces, outbound, gruu
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, PRACK, UPDATE
Content-Type: application/sdp
Content-Length: 267
Contact: sip:100@192.168.1.4;transport=udp;expires=3600;+sip.instance=“urn:uuid:8b6a0da6-d801-0087-a3c0-583551f19284
User-Agent: Linphone Desktop/4.2.5 (Windows 10 Version 2009, Qt 5.14.2) LinphoneCore/4.4.19

v=0
o=100 4026 1597 IN IP4 192.168.1.4
s=Talk
c=IN IP4 192.168.1.4
t=0 0
a=rtcp-xr:rcvr-rtt=all:10000 stat-summary=loss,dup,jitt,TTL voip-metrics
m=audio 7078 RTP/AVPF 0 8 101
a=rtpmap:101 telephone-event/8000
a=rtcp-fb:* trr-int 1000
a=rtcp-fb:* ccm tmmbr
<------------->
— (13 headers 10 lines) —
Sending to 192.168.1.4:5060 (no NAT)
Sending to 192.168.1.4:5060 (no NAT)
Using INVITE request as basis request - mWdGgJRu~S
Found peer ‘100’ for ‘100’ from 192.168.1.4:5060

<— Reliably Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.yAeR3ANAX;received=192.168.1.4;rport=5060
From: “omer RIT” sip:100@192.168.1.6;tag=aoHiq91~z
To: sip:101@192.168.1.6;tag=as01c2ed2d
Call-ID: mWdGgJRu~S
CSeq: 20 INVITE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“03ab6924”
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘mWdGgJRu~S’ in 6400 ms (Method: INVITE)

<— SIP read from UDP:192.168.1.4:5060 —>
ACK sip:101@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.yAeR3ANAX;rport
Call-ID: mWdGgJRu~S
From: “omer RIT” sip:100@192.168.1.6;tag=aoHiq91~z
To: sip:101@192.168.1.6;tag=as01c2ed2d
Contact: sip:100@192.168.1.4;transport=udp;expires=3600;+sip.instance=“urn:uuid:8b6a0da6-d801-0087-a3c0-583551f19284
Max-Forwards: 70
CSeq: 20 ACK

<------------->
— (8 headers 0 lines) —

<— SIP read from UDP:192.168.1.4:5060 —>
INVITE sip:101@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.ClP46Ar7G;rport
From: “omer RIT” sip:100@192.168.1.6;tag=aoHiq91~z
To: sip:101@192.168.1.6
CSeq: 21 INVITE
Call-ID: mWdGgJRu~S
Max-Forwards: 70
Supported: replaces, outbound, gruu
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, PRACK, UPDATE
Content-Type: application/sdp
Content-Length: 267
Contact: sip:100@192.168.1.4;transport=udp;expires=3600;+sip.instance=“urn:uuid:8b6a0da6-d801-0087-a3c0-583551f19284
User-Agent: Linphone Desktop/4.2.5 (Windows 10 Version 2009, Qt 5.14.2) LinphoneCore/4.4.19
Authorization: Digest realm=“asterisk”, nonce=“03ab6924”, algorithm=MD5, username=“100”, uri=“sip:101@192.168.1.6:5060”, response=“49da394a9aaf6772e06e5f40c485371b”

v=0
o=100 4026 1597 IN IP4 192.168.1.4
s=Talk
c=IN IP4 192.168.1.4
t=0 0
a=rtcp-xr:rcvr-rtt=all:10000 stat-summary=loss,dup,jitt,TTL voip-metrics
m=audio 7078 RTP/AVPF 0 8 101
a=rtpmap:101 telephone-event/8000
a=rtcp-fb:* trr-int 1000
a=rtcp-fb:* ccm tmmbr
<------------->
— (14 headers 10 lines) —
Sending to 192.168.1.4:5060 (no NAT)
Using INVITE request as basis request - mWdGgJRu~S
Found peer ‘100’ for ‘100’ from 192.168.1.4:5060
== Using SIP VIDEO TOS bits 136
== Using SIP VIDEO CoS mark 6
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Got SDP version 1597 and unique parts [100 4026 IN IP4 192.168.1.4]
[2021-06-18 17:48:48] NOTICE[1732][C-00000009]: chan_sip.c:10509 process_sdp: Received AVPF profile in audio offer but AVPF is not enabled, enabling: audio 7078 RTP/AVPF 0 8 101
Found RTP audio format 0
Found RTP audio format 8
Found RTP audio format 101
Found audio description format telephone-event for ID 101
Capabilities: us - (ulaw|alaw|vp8), peer - audio=(ulaw|alaw)/video=(nothing)/text=(nothing), combined - (ulaw|alaw)
Non-codec capabilities (dtmf): us - 0x1 (telephone-event|), peer - 0x1 (telephone-event|), combined - 0x1 (telephone-event|)
Peer audio RTP is at port 192.168.1.4:7078
Peer doesn’t provide video
Looking for 101 in from-internal (domain 192.168.1.6)
sip_route_dump: route/path hop: sip:100@192.168.1.4;transport=udp

<— Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.ClP46Ar7G;received=192.168.1.4;rport=5060
From: “omer RIT” sip:100@192.168.1.6;tag=aoHiq91~z
To: sip:101@192.168.1.6
Call-ID: mWdGgJRu~S
CSeq: 21 INVITE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: sip:101@192.168.1.6:5060
Content-Length: 0

<------------>
== Using SIP VIDEO TOS bits 136
== Using SIP VIDEO CoS mark 6
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
== Spawn extension (from-internal, 101, 1) exited non-zero on ‘SIP/101-0000000c’
Audio is at 19384
Adding codec ulaw to SDP
Adding codec alaw to SDP
Adding non-codec 0x1 (telephone-event) to SDP
Reliably Transmitting (no NAT) to 192.168.1.150:58040:
INVITE sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK7ff9dd4e
Max-Forwards: 70
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp
Contact: sip:100@192.168.1.6:5060
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 INVITE
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:48:48 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
P-Asserted-Identity: “Omer RIT” sip:100@192.168.1.6
Content-Type: application/sdp
Content-Length: 261

v=0
o=root 1999318117 1999318117 IN IP4 192.168.1.6
s=Asterisk PBX 17.9.3
c=IN IP4 192.168.1.6
t=0 0
m=audio 19384 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=maxptime:150
a=sendrecv


<— Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.ClP46Ar7G;received=192.168.1.4;rport=5060
From: “omer RIT” sip:100@192.168.1.6;tag=aoHiq91~z
To: sip:101@192.168.1.6;tag=as6e7e7685
Call-ID: mWdGgJRu~S
CSeq: 21 INVITE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: sip:101@192.168.1.6:5060
P-Asserted-Identity: “Ahmed RIT” sip:101@192.168.1.6
Content-Length: 0

<------------>
Retransmitting #1 (no NAT) to 192.168.1.150:58040:
INVITE sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK7ff9dd4e
Max-Forwards: 70
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp
Contact: sip:100@192.168.1.6:5060
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 INVITE
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:48:48 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
P-Asserted-Identity: “Omer RIT” sip:100@192.168.1.6
Content-Type: application/sdp
Content-Length: 261

v=0
o=root 1999318117 1999318117 IN IP4 192.168.1.6
s=Asterisk PBX 17.9.3
c=IN IP4 192.168.1.6
t=0 0
m=audio 19384 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=maxptime:150
a=sendrecv


<— SIP read from UDP:192.168.1.4:5060 —>

<------------->
Retransmitting #2 (no NAT) to 192.168.1.150:58040:
INVITE sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK7ff9dd4e
Max-Forwards: 70
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp
Contact: sip:100@192.168.1.6:5060
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 INVITE
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:48:48 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
P-Asserted-Identity: “Omer RIT” sip:100@192.168.1.6
Content-Type: application/sdp
Content-Length: 261

v=0
o=root 1999318117 1999318117 IN IP4 192.168.1.6
s=Asterisk PBX 17.9.3
c=IN IP4 192.168.1.6
t=0 0
m=audio 19384 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=maxptime:150
a=sendrecv


<— SIP read from UDP:192.168.1.150:58040 —>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK7ff9dd4e
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 INVITE

<------------->
— (6 headers 0 lines) —

<— SIP read from UDP:192.168.1.150:58040 —>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK7ff9dd4e
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp;tag=prrRBch
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 INVITE
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14
Supported: replaces, outbound, gruu

<------------->
— (8 headers 0 lines) —
sip_route_dump: no route/path

<— Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.ClP46Ar7G;received=192.168.1.4;rport=5060
From: “omer RIT” sip:100@192.168.1.6;tag=aoHiq91~z
To: sip:101@192.168.1.6;tag=as6e7e7685
Call-ID: mWdGgJRu~S
CSeq: 21 INVITE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: sip:101@192.168.1.6:5060
P-Asserted-Identity: “Ahmed RIT” sip:101@192.168.1.6
Content-Length: 0

<------------>

<— SIP read from UDP:192.168.1.150:58040 —>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK7ff9dd4e
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp;tag=prrRBch
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 INVITE
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14
Supported: replaces, outbound, gruu

<------------->
— (8 headers 0 lines) —
sip_route_dump: no route/path
Reliably Transmitting (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK5abaf2ab
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as367867ab
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 4614691924ea275533c581fd06526288@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:48:54 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


Retransmitting #1 (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK5abaf2ab
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as367867ab
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 4614691924ea275533c581fd06526288@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:48:54 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


<— SIP read from UDP:192.168.1.150:58040 —>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK7ff9dd4e
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp;tag=prrRBch
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 INVITE
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14
Supported: replaces, outbound, gruu

<------------->
— (8 headers 0 lines) —
sip_route_dump: no route/path
Retransmitting #2 (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK5abaf2ab
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as367867ab
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 4614691924ea275533c581fd06526288@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:48:54 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


Retransmitting #3 (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK5abaf2ab
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as367867ab
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 4614691924ea275533c581fd06526288@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:48:54 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


<— SIP read from UDP:192.168.1.150:58040 —>

<------------->
Retransmitting #4 (no NAT) to 172.31.48.1:21444:
OPTIONS sip:104@172.31.48.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK5abaf2ab
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as367867ab
To: sip:104@172.31.48.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 4614691924ea275533c581fd06526288@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Fri, 18 Jun 2021 15:48:54 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


Really destroying SIP dialog ‘4614691924ea275533c581fd06526288@192.168.1.6:5060’ Method: OPTIONS
Really destroying SIP dialog ‘9keHol~kfL’ Method: REGISTER

<— SIP read from UDP:192.168.1.4:5060 —>

<------------->

<— SIP read from UDP:192.168.1.150:58040 —>
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK7ff9dd4e
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp;tag=prrRBch
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 INVITE
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14
Supported: replaces, outbound, gruu
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, PRACK, UPDATE
Contact: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp;expires=3600;+sip.instance=“urn:uuid:103ad439-63db-0025-8978-40dfba36f240”;+org.linphone.specs=“ephemeral,groupchat,groupchat/1.1,lime”
Content-Type: application/sdp
Content-Length: 146

v=0
o=101 3958 793 IN IP4 192.168.1.150
s=Talk
c=IN IP4 192.168.1.150
t=0 0
m=audio 7206 RTP/AVP 0 8 101
a=rtpmap:101 telephone-event/8000
<------------->
— (12 headers 7 lines) —
Got SDP version 793 and unique parts [101 3958 IN IP4 192.168.1.150]
Found RTP audio format 0
Found RTP audio format 8
Found RTP audio format 101
Found audio description format telephone-event for ID 101
Capabilities: us - (ulaw|alaw|vp8), peer - audio=(ulaw|alaw)/video=(nothing)/text=(nothing), combined - (ulaw|alaw)
Non-codec capabilities (dtmf): us - 0x1 (telephone-event|), peer - 0x1 (telephone-event|), combined - 0x1 (telephone-event|)
Peer audio RTP is at port 192.168.1.150:7206
sip_route_dump: route/path hop: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp
set_destination: Parsing sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp for address/port to send to
set_destination: set destination to 192.168.1.150:58040
Transmitting (no NAT) to 192.168.1.150:58040:
ACK sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK4680f40c
Max-Forwards: 70
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: <sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str
Contact: sip:100@192.168.1.6:5060
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 ACK
User-Agent: FPBX-15.0.17.34(17.9.3)
Content-Length: 0


<— SIP read from UDP:192.168.1.150:58040 —>
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK7ff9dd4e
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp;tag=prrRBch
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 INVITE
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14
Supported: replaces, outbound, gruu
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, PRACK, UPDATE
Contact: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp;expires=3600;+sip.instance=“urn:uuid:103ad439-63db-0025-8978-40dfba36f240”;+org.linphone.specs=“ephemeral,groupchat,groupchat/1.1,lime”
Content-Type: application/sdp
Content-Length: 146

v=0
o=101 3958 793 IN IP4 192.168.1.150
s=Talk
c=IN IP4 192.168.1.150
t=0 0
m=audio 7206 RTP/AVP 0 8 101
a=rtpmap:101 telephone-event/8000
<------------->
— (12 headers 7 lines) —
set_destination: Parsing sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp for address/port to send to
set_destination: set destination to 192.168.1.150:58040
Transmitting (no NAT) to 192.168.1.150:58040:
ACK sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK2befafba
Max-Forwards: 70
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: <sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str
Contact: sip:100@192.168.1.6:5060
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 ACK
User-Agent: FPBX-15.0.17.34(17.9.3)
Content-Length: 0


<— SIP read from UDP:192.168.1.150:58040 —>
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK7ff9dd4e
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp;tag=prrRBch
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 INVITE
User-Agent: LinphoneiOS/4.4.2 (iPhone) LinphoneSDK/4.5.14
Supported: replaces, outbound, gruu
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, PRACK, UPDATE
Contact: sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp;expires=3600;+sip.instance=“urn:uuid:103ad439-63db-0025-8978-40dfba36f240”;+org.linphone.specs=“ephemeral,groupchat,groupchat/1.1,lime”
Content-Type: application/sdp
Content-Length: 146

v=0
o=101 3958 793 IN IP4 192.168.1.150
s=Talk
c=IN IP4 192.168.1.150
t=0 0
m=audio 7206 RTP/AVP 0 8 101
a=rtpmap:101 telephone-event/8000
<------------->
— (12 headers 7 lines) —
set_destination: Parsing sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp for address/port to send to
set_destination: set destination to 192.168.1.150:58040
Transmitting (no NAT) to 192.168.1.150:58040:
ACK sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-groupchat-str=GC_MSG;pn-call-snd=notes_of_the_optimistic.caf;pn-msg-snd=msg.caf;pn-timeout=0;pn-silent=1;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK117a23d1
Max-Forwards: 70
From: “Omer RIT” sip:100@192.168.1.6;tag=as0d1ac23e
To: <sip:101@192.168.1.150:58040;pn-provider=apns;pn-prid=CE9EAEB67B5AD22EA4B546A0023DF2465C21D698D3C7354BC862C1B4A483B8B7:remote&D07F2AD347B4F0FBC494AE8A1B40CEA67598DB2CA0C3C00A84606987310A22C0:voip;pn-param=ABCD1234.org.linphone.phone.remote&voip;pn-msg-str
Contact: sip:100@192.168.1.6:5060
Call-ID: 220ddc7434e836277e965c2b158c48b3@192.168.1.6:5060
CSeq: 102 ACK
User-Agent: FPBX-15.0.17.34(17.9.3)
Content-Length: 0


Audio is at 10422
Adding codec ulaw to SDP
Adding codec alaw to SDP
Adding non-codec 0x1 (telephone-event) to SDP

<— Reliably Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.ClP46Ar7G;received=192.168.1.4;rport=5060
From: “omer RIT” sip:100@192.168.1.6;tag=aoHiq91~z
To: sip:101@192.168.1.6;tag=as6e7e7685
Call-ID: mWdGgJRu~S
CSeq: 21 INVITE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE


(Rana hashem) #7

[root@freepbx ~]# less /var/log/asterisk/full
[2021-06-18 09:43:02] Asterisk 17.9.3 built by mockbuild @ jenkins7 on a x86_64 running Linux on 2021-04-07 07:34:04 UTC
[2021-06-18 09:43:02] VERBOSE[8174] logger.c: Asterisk Queue Logger restarted
[2021-06-18 09:43:02] VERBOSE[8174] asterisk.c: Remote UNIX connection disconnected
[2021-06-18 09:45:03] WARNING[1894] chan_sip.c: Retransmission timeout reached on transmission 12587950077039810775152270186931e7 for seqno 102 (Critical Request) – See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 6397ms with no response
[2021-06-18 09:45:03] WARNING[1894] chan_sip.c: Retransmission timeout reached on transmission 37609957044810775152236a36089683e7 for seqno 102 (Critical Request) – See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 6400ms with no response
[2021-06-18 09:45:03] WARNING[1894] chan_sip.c: Retransmission timeout reached on transmission 11248281704981077515226587318568e7 for seqno 102 (Critical Request) – See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 6400ms with no response
[2021-06-18 09:51:21] VERBOSE[1382] asterisk.c: Remote UNIX connection
[2021-06-18 09:51:21] VERBOSE[8964] asterisk.c: Remote UNIX connection disconnected
[2021-06-18 09:51:21] VERBOSE[1382] asterisk.c: Remote UNIX connection
[2021-06-18 09:51:21] VERBOSE[8970] asterisk.c: Remote UNIX connection disconnected
[2021-06-18 09:51:21] VERBOSE[1382] asterisk.c: Remote UNIX connection
[2021-06-18 09:51:21] VERBOSE[8972] asterisk.c: Remote UNIX connection disconnected
[2021-06-18 09:51:21] VERBOSE[1382] asterisk.c: Remote UNIX connection
[2021-06-18 09:51:21] VERBOSE[8974] asterisk.c: Remote UNIX connection disconnected
[2021-06-18 09:51:29] VERBOSE[1382] asterisk.c: Remote UNIX connection
[2021-06-18 09:51:29] VERBOSE[9080] loader.c: Reloading module ‘res_odbc.so’ (ODBC resource)
[2021-06-18 09:51:29] NOTICE[9080] res_odbc.c: Registered ODBC class ‘asteriskcdrdb’ dsn->[MySQL-asteriskcdrdb]
[2021-06-18 09:51:29] VERBOSE[9080] loader.c: Reloading module ‘extconfig’ (Configuration)
[2021-06-18 09:51:29] VERBOSE[9080] loader.c: Reloading module ‘res_config_odbc.so’ (Realtime ODBC configuration)
[2021-06-18 09:51:29] VERBOSE[9080] loader.c: Reloading module ‘cdr’ (CDR Engine)
[2021-06-18 09:51:29] ERROR[9080] config_options.c: Unable to load config file ‘cdr.conf’
[2021-06-18 09:51:29] VERBOSE[9080] loader.c: Reloading module ‘cdr_adaptive_odbc.so’ (Adaptive ODBC CDR backend)
[2021-06-18 09:51:29] VERBOSE[9080] cdr_adaptive_odbc.c: Found adaptive CDR table cdr@asteriskcdrdb.
[2021-06-18 09:51:29] VERBOSE[9080] cdr_adaptive_odbc.c: Found alias start for column calldate in cdr@asteriskcdrdb
[2021-06-18 09:51:29] VERBOSE[9080] loader.c: Reloading module ‘pbx_config.so’ (Text Extension Configuration)
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘CFDEVSTATE’ to ‘TRUE’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘MIXMON_BEEP’ to ‘’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘MONITOR_REC_OPTION’ to ‘b’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘DNDDEVSTATE’ to ‘TRUE’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘FMDEVSTATE’ to ‘TRUE’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘QUEDEVSTATE’ to ‘TRUE’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘OPERATOR_XTN’ to ‘’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘VM_DDTYPE’ to ‘u’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘VM_GAIN’ to ‘’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘VM_OPTS’ to ‘’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘VMX_LOOPS’ to ‘1’
[2021-06-18 09:51:29] VERBOSE[9080] pbx_variables.c: Setting global variable ‘VMX_OPTS_DOVM’ to ‘’
/var/log/asterisk/full


(David55) #8

In one case it is reported not found, in the other case it acknowledged as accepted, but the request URI is the same.


(Rana hashem) #9

What do you suggest me to do to change the softphone type,or
what?
:disappointed_relieved::disappointed_relieved::disappointed_relieved::disappointed_relieved:


(Rana hashem) #10

[root@freepbx ~]# tail -f /var/log/asterisk/full [2021-06-18 13:39:12] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:101,sip:100@192.168.1.4”) in new stack [2021-06-18 13:39:12] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack [2021-06-18 13:39:12] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 101, 2) exited non-zero on ‘Message/ast_msg_queue’ [2021-06-18 13:39:22] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:100,sip:101@192.168.1.6”) in new stack [2021-06-18 13:39:22] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack [2021-06-18 13:39:22] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 100, 2) exited non-zero on ‘Message/ast_msg_queue’ [2021-06-18 13:39:26] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:100,sip:101@192.168.1.6”) in new stack [2021-06-18 13:39:26] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack [2021-06-18 13:39:26] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 100, 2) exited non-zero on ‘Message/ast_msg_queue’ [2021-06-18 13:39:37] VERBOSE[4697] asterisk.c: Remote UNIX connection disconnected [2021-06-18 13:39:42] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:100,sip:101@192.168.1.6”) in new stack [2021-06-18 13:39:42] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack [2021-06-18 13:39:42] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 100, 2) exited non-zero on ‘Message/ast_msg_queue’ [2021-06-18 13:39:46] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:101,sip:100@192.168.1.4”) in new stack [2021-06-18 13:39:46] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack [2021-06-18 13:39:46] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 101, 2) exited non-zero on ‘Message/ast_msg_queue’ [2021-06-18 13:39:50] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:100,sip:101@192.168.1.6”) in new stack [2021-06-18 13:39:50] VERBOSE[1338][C-00000002] pbx.c: Executing [100@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack [2021-06-18 13:39:50] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 100, 2) exited non-zero on ‘Message/ast_msg_queue’ [2021-06-18 13:39:53] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:101,sip:100@192.168.1.4”) in new stack [2021-06-18 13:39:53] VERBOSE[1338][C-00000002] pbx.c: Executing [101@astsms:2] Hangup(“Message/ast_msg_queue”, “”) in new stack [2021-06-18 13:39:53] VERBOSE[1338][C-00000002] pbx.c: Spawn extension (astsms, 101, 2) exited non-zero on ‘Message/ast_msg_queue’


(David55) #11

This is not showing any protocol activity. Either you didn’t have protocol debugging on this time, or the message was rejected before it got that far.

I’d suggest you need to display ${MESSAGE_SEND_STATUS} to get a better idea of whether Asterisk thinks the message was send.


(Rana hashem) #12

how i can do this :sob:


(Rana hashem) #13

https://programmersought.com/article/58603937977/

what do u thank about this tatoriall with freepbx15 distro ?


(David55) #14

I’m under the impression that the messaging sending dialplan is custom, in which case you can add a priority between the MessageSend and the Hangup, which does Noop( ${MESSAGE_SEND_STATUS}), which will cause the value to be logged at any verbosity level that includes output of the dialplan line about to be executed. You can also, for example, use the Verbose, etc., to explicitly log it.

(You could also replace the Hangup line, as it doesn’t actually do anything useful.


(Rana hashem) #15

<------------->
— (6 headers 0 lines) —
Really destroying SIP dialog ‘2c18223642becddf2e562dd82c0e291e@127.0.0.1:5060’ M ethod: MESSAGE
Reliably Transmitting (no NAT) to 172.23.32.1:21444:
OPTIONS sip:104@172.23.32.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK6a2fd815
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as42f31e5a
To: sip:104@172.23.32.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 151fa20a357cebe80b4e970c23c3d683@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Sat, 19 Jun 2021 12:17:06 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
Content-Length: 0


Retransmitting #1 (no NAT) to 172.23.32.1:21444:
OPTIONS sip:104@172.23.32.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK6a2fd815
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as42f31e5a
To: sip:104@172.23.32.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 151fa20a357cebe80b4e970c23c3d683@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Sat, 19 Jun 2021 12:17:06 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
Content-Length: 0


<— SIP read from UDP:192.168.1.4:5060 —>
MESSAGE sip:108@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.KzEHfsnEU;rport
From: sip:100@192.168.1.6;tag=YBmt5C-Jz
To: sip:108@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: 4n1fgfjS9O
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Sat, 19 Jun 2021 12:17:07 GMT
Content-Type: application/im-iscomposing+xml
Content-Length: 170
Priority: non-urgent
Expires: 0
User-Agent: Linphone Desktop/4.2.5 (Windows 10 Version 2009, Qt 5.14.2) Linphone Core/4.4.19

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>active60

<------------->
— (14 headers 1 lines) —
Sending to 192.168.1.4:5060 (no NAT)
Receiving message!

<— Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.KzEHfsnEU;received=192.168.1.4; rport=5060
From: sip:100@192.168.1.6;tag=YBmt5C-Jz
To: sip:108@192.168.1.6;tag=as10c11416
Call-ID: 4n1fgfjS9O
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘4n1fgfjS9O’ in 32000 ms (Method: MESSAGE)
Retransmitting #2 (no NAT) to 172.23.32.1:21444:
OPTIONS sip:104@172.23.32.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK6a2fd815
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as42f31e5a
To: sip:104@172.23.32.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 151fa20a357cebe80b4e970c23c3d683@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Sat, 19 Jun 2021 12:17:06 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
Content-Length: 0


<— SIP read from UDP:192.168.1.4:5060 —>

<------------->

<— SIP read from UDP:192.168.1.4:5060 —>
MESSAGE sip:108@192.168.1.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.-1bJueIwh;rport
From: sip:100@192.168.1.6;tag=iuL6gfJa9
To: sip:108@192.168.1.6
CSeq: 20 MESSAGE
Call-ID: jHRSBGXOJY
Max-Forwards: 70
Supported: replaces, outbound, gruu
Date: Sat, 19 Jun 2021 12:17:08 GMT
Content-Type: text/plain
Content-Length: 3
User-Agent: Linphone Desktop/4.2.5 (Windows 10 Version 2009, Qt 5.14.2) Linphone Core/4.4.19

yyy
<------------->
— (12 headers 1 lines) —
Sending to 192.168.1.4:5060 (no NAT)
Receiving message!
Looking for 108 in astsms (domain 192.168.1.6)

<— Transmitting (no NAT) to 192.168.1.4:5060 —>
SIP/2.0 202 Accepted
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK.-1bJueIwh;received=192.168.1.4; rport=5060
From: sip:100@192.168.1.6;tag=iuL6gfJa9
To: sip:108@192.168.1.6;tag=as17281fb4
Call-ID: jHRSBGXOJY
CSeq: 20 MESSAGE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘jHRSBGXOJY’ in 32000 ms (Method: MESSAGE)
– Executing [108@astsms:1] MessageSend(“Message/ast_msg_queue”, “sip:108,”" sip:100@192.168.1.6") in new stack
Reliably Transmitting (NAT) to 192.168.1.4:55702:
MESSAGE sip:108@192.168.1.4:55702;ob SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK4539e4e2;rport
Max-Forwards: 70
From: “Unknown” sip:100@192.168.1.6;tag=as6b575a47
To: sip:108@192.168.1.4:55702;ob
Contact: sip:100@192.168.1.6:5060
Call-ID: 72d5a8261bc62f314a6c9c606e74336c@127.0.0.1:5060
CSeq: 102 MESSAGE
User-Agent: FPBX-15.0.17.34(17.9.3)
Content-Type: text/plain;charset=UTF-8
Content-Length: 3

yyy

Scheduling destruction of SIP dialog ‘72d5a8261bc62f314a6c9c606e74336c@127.0.0.1 :5060’ in 6400 ms (Method: MESSAGE)
– Executing [108@astsms:2] NoOp(“Message/ast_msg_queue”, “Send status is SU CCESS”) in new stack
– Auto fallthrough, channel ‘Message/ast_msg_queue’ status is ‘UNKNOWN’

<— SIP read from UDP:192.168.1.4:55702 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.6:5060;rport=5060;received=192.168.1.6;branch=z9hG4bK 4539e4e2
Call-ID: 72d5a8261bc62f314a6c9c606e74336c@127.0.0.1:5060
From: “Unknown” sip:100@192.168.1.6;tag=as6b575a47
To: sip:108@192.168.1.4;ob;tag=z9hG4bK4539e4e2
CSeq: 102 MESSAGE
Content-Length: 0

<------------->
— (7 headers 0 lines) —
Really destroying SIP dialog ‘72d5a8261bc62f314a6c9c606e74336c@127.0.0.1:5060’ M ethod: MESSAGE
Retransmitting #3 (no NAT) to 172.23.32.1:21444:
OPTIONS sip:104@172.23.32.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK6a2fd815
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as42f31e5a
To: sip:104@172.23.32.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 151fa20a357cebe80b4e970c23c3d683@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Sat, 19 Jun 2021 12:17:06 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
Content-Length: 0


Retransmitting #4 (no NAT) to 172.23.32.1:21444:
OPTIONS sip:104@172.23.32.1:21444 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK6a2fd815
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.6;tag=as42f31e5a
To: sip:104@172.23.32.1:21444
Contact: sip:Unknown@192.168.1.6:5060
Call-ID: 151fa20a357cebe80b4e970c23c3d683@192.168.1.6:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-15.0.17.34(17.9.3)
Date: Sat, 19 Jun 2021 12:17:06 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
Content-Length: 0


Really destroying SIP dialog ‘151fa20a357cebe80b4e970c23c3d683@192.168.1.6:5060’ Method: OPTIONS

<— SIP read from UDP:192.168.1.4:55702 —>
SUBSCRIBE sip:101@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:55702;rport;branch=z9hG4bKPj190dffbab9cb4d8f9dab72d ebfddc7b6
Max-Forwards: 70
From: sip:108@192.168.1.6;tag=48c287b1b6414c2183cd5ce3671d4ae0
To: sip:101@192.168.1.6;tag=as26020ce9
Contact: sip:108@192.168.1.4:55702;ob
Call-ID: 11940a87d16849fdb0b55cc715939098
CSeq: 3992 SUBSCRIBE
Event: presence
Expires: 600
Supported: replaces, 100rel, timer, norefersub
Accept: application/pidf+xml, application/xpidf+xml
Allow-Events: presence, message-summary, refer
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Sending to 192.168.1.4:55702 (no NAT)

<— Transmitting (no NAT) to 192.168.1.4:55702 —>
SIP/2.0 481 Call/Transaction Does Not Exist
Via: SIP/2.0/UDP 192.168.1.4:55702;branch=z9hG4bKPj190dffbab9cb4d8f9dab72debfddc 7b6;received=192.168.1.4;rport=55702
From: sip:108@192.168.1.6;tag=48c287b1b6414c2183cd5ce3671d4ae0
To: sip:101@192.168.1.6;tag=as26020ce9
Call-ID: 11940a87d16849fdb0b55cc715939098
CSeq: 3992 SUBSCRIBE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘11940a87d16849fdb0b55cc715939098’ in 32000 ms (Method: SUBSCRIBE)

<— SIP read from UDP:192.168.1.4:55702 —>
SUBSCRIBE sip:101@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:55702;rport;branch=z9hG4bKPj81bd0c4026d5430da9d76c7 4b36b25c7
Max-Forwards: 70
From: sip:108@192.168.1.6;tag=8c3eda753e0845bf8ebfa94c8884d64d
To: sip:101@192.168.1.6
Contact: sip:108@192.168.1.4:55702;ob
Call-ID: 401fcf1687ec4601a3a3278d6227db07
CSeq: 12287 SUBSCRIBE
Event: presence
Expires: 600
Supported: replaces, 100rel, timer, norefersub
Accept: application/pidf+xml, application/xpidf+xml
Allow-Events: presence, message-summary, refer
User-Agent: MicroSIP/3.20.6
Content-Length: 0

<------------->
— (15 headers 0 lines) —
Sending to 192.168.1.4:55702 (no NAT)
Creating new subscription
Sending to 192.168.1.4:55702 (no NAT)
sip_route_dump: route/path hop: sip:108@192.168.1.4:55702;ob
Found peer ‘108’ for ‘108’ from 192.168.1.4:55702

<— Transmitting (NAT) to 192.168.1.4:55702 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.4:55702;branch=z9hG4bKPj81bd0c4026d5430da9d76c74b36b2 5c7;received=192.168.1.4;rport=55702
From: sip:108@192.168.1.6;tag=8c3eda753e0845bf8ebfa94c8884d64d
To: sip:101@192.168.1.6;tag=as47f06dc0
Call-ID: 401fcf1687ec4601a3a3278d6227db07
CSeq: 12287 SUBSCRIBE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“3f0d59a1”
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘401fcf1687ec4601a3a3278d6227db07’ in 6400 ms (Method: SUBSCRIBE)

<— SIP read from UDP:192.168.1.4:55702 —>
SUBSCRIBE sip:101@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:55702;rport;branch=z9hG4bKPj127792c779874087b9e3965 ce1e390c2
Max-Forwards: 70
From: sip:108@192.168.1.6;tag=8c3eda753e0845bf8ebfa94c8884d64d
To: sip:101@192.168.1.6
Contact: sip:108@192.168.1.4:55702;ob
Call-ID: 401fcf1687ec4601a3a3278d6227db07
CSeq: 12288 SUBSCRIBE
Event: presence
Expires: 600
Supported: replaces, 100rel, timer, norefersub
Accept: application/pidf+xml, application/xpidf+xml
Allow-Events: presence, message-summary, refer
User-Agent: MicroSIP/3.20.6
Authorization: Digest username=“108”, realm=“asterisk”, nonce=“3f0d59a1”, uri=“s ip:101@192.168.1.6:5060”, response=“003e71376f0034f4bcbbc47bd83a0e8a”, algorithm =MD5
Content-Length: 0

<------------->
— (16 headers 0 lines) —
Creating new subscription
Sending to 192.168.1.4:55702 (NAT)
Found peer ‘108’ for ‘108’ from 192.168.1.4:55702
Looking for 101 in from-internal (domain 192.168.1.6)
Scheduling destruction of SIP dialog ‘401fcf1687ec4601a3a3278d6227db07’ in 61000 0 ms (Method: SUBSCRIBE)

<— Transmitting (NAT) to 192.168.1.4:55702 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.4:55702;branch=z9hG4bKPj127792c779874087b9e3965ce1e39 0c2;received=192.168.1.4;rport=55702
From: sip:108@192.168.1.6;tag=8c3eda753e0845bf8ebfa94c8884d64d
To: sip:101@192.168.1.6;tag=as47f06dc0
Call-ID: 401fcf1687ec4601a3a3278d6227db07
CSeq: 12288 SUBSCRIBE
Server: FPBX-15.0.17.34(17.9.3)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLIS H, MESSAGE
Supported: replaces, timer
Expires: 600
Contact: sip:101@192.168.1.6:5060;expires=600
Content-Length: 0

<------------>
Reliably Transmitting (NAT) to 192.168.1.4:55702:
NOTIFY sip:108@192.168.1.4:55702;ob SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK12c62c7c;rport
Max-Forwards: 70
From: sip:101@192.168.1.6;tag=as47f06dc0
To: sip:108@192.168.1.6;tag=8c3eda753e0845bf8ebfa94c8884d64d
Contact: sip:101@192.168.1.6:5060
Call-ID: 401fcf1687ec4601a3a3278d6227db07
CSeq: 102 NOTIFY
User-Agent: FPBX-15.0.17.34(17.9.3)
Subscription-State: active
Event: presence
Content-Type: application/pidf+xml
Content-Length: 524

<?xml version="1.0" encoding="ISO-8859-1"?>


pp:person
ep:activitiesep:away/</ep:activities>
</pp:person>
Unavailable

sip:101@192.168.1.6
closed


<— SIP read from UDP:192.168.1.4:55702 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.6:5060;rport=5060;received=192.168.1.6;branch=z9hG4bK 12c62c7c
Call-ID: 401fcf1687ec4601a3a3278d6227db07
From: sip:101@192.168.1.6;tag=as47f06dc0
To: sip:108@192.168.1.6;tag=8c3eda753e0845bf8ebfa94c8884d64d
CSeq: 102 NOTIFY
Contact: sip:108@192.168.1.4:55702;ob
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Content-Length: 0

<------------->
— (10 headers 0 lines) —

<— SIP read from UDP:192.168.1.4:55702 —>


(David55) #16

108 has told Asterisk the the message was successfully received.


(Rana hashem) #17

still line-phone on laptop receive messages but csip do not receive


(Rana hashem) #18

but on lin phone on the same laptop i see linphone do not accept any messages from csip messages-sends


(Jared Busch) #19

Learn to use code tags and don’t spam cross post to other sites.


(Rana hashem) #20

hi mister
I’m still an obstruct I want a solution from my mistake:sob::sob: