-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
res.send fnAck is not called #70
Comments
I think the remote server sends ack with different Via branch. Do you think this is likely to be the cause? |
No, I dont think so. The ACK to a 200 OK is supposed to have a new VIa branch |
So, why fnAck is not called? I see these codes on drachtio-agent.js here
and here
Is there any possibility dialogId not matched? Thank you. |
I could get the meta object and it has following data. So, pendingAckOrPrack Map has empty key and fnAck function value, but parsed dialogId variable of _onMsg's token has "c3282b5eff174b7e86e0a90ef3ec87b3@10.1.32.34:3551;from-tag=3254d1188e224139a03edd619f912a85" and fnAck never called. i could not know the reason of empty dialogId, could you give me any suggestions? |
Anyway, is there any correct way to get the Ack request object? Because the remote server sends SDP body within ack and i should get the sdp body and parse it. |
Hi Dave, |
sorry for the delay on this; thx for your patience. Been super busy but will look into and have an update tomorrow |
…RACK message as a parameter (partial fix for #70)
this actually required a fix in drachtio server. You will need to upgrade to v0.8.4-rc5 (or latest develop branch) of the drachtio server. Additionally, I noticed that when calling the After updating your code please retest and let me know if this resolves your issue. |
It worked after updated drachtio-server(v0.8.3-13-ge19fe9216) and drachtio-srf(4.4.25). The fnAck callback is called and i could get ack req object and parse. Thank you. |
Hi Dave,
If the remote server send re-INVITE, i just send 200 OK with the current dialog's local sdp and the remote server send ack to me but it seems no fnAck callback is called.
I just implemented the dialog modify event like this.
SIP messages are as follows:
// re-INVITE from remote(no sdp)
2019-11-21 02:26:01.635942 recv 581 bytes from udp/[121.255.185.19]:3551 at 02:26:01.635839:
INVITE sip:2001@172.25.0.2:3601 SIP/2.0
Via: SIP/2.0/UDP 10.1.32.34:3551;branch=z9hG4bKe4bcbdc7015e4f62bcd4bdab905cfd7a
From: "2001"sip:3201@10.1.32.34:3551;tag=7a4df4ebb2d5430f8128211f8c37455b
To: sip:2001@172.25.0.2:3601;tag=gK90327p45c4j
Call-ID: 6dadae111eb345fd80b6965c761e6ccc@10.1.32.34:3551
CSeq: 157 INVITE
Max-Forwards: 70
Contact: sip:2001@10.1.32.34:3551
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, INFO
Supported: replaces
User-Agent: K 2.2.2
P-Asserted-Identity: sip:2001@10.1.32.34:3551
Content-Length: 0
2019-11-21 02:26:01.636565 send 364 bytes to udp/[121.255.185.19]:3551 at 02:26:01.636431:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.1.32.34:3551;branch=z9hG4bKe4bcbdc7015e4f62bcd4bdab905cfd7a;received=121.255.185.19;rport=3551
From: "2001"sip:3201@10.1.32.34:3551;tag=7a4df4ebb2d5430f8128211f8c37455b
To: sip:2001@172.25.0.2:3601;tag=gK90327p45c4j
Call-ID: 6dadae111eb345fd80b6965c761e6ccc@10.1.32.34:3551
CSeq: 157 INVITE
Content-Length: 0
// res.send
2019-11-21 02:26:01.688465 send 665 bytes to udp/[121.255.185.19]:3551 at 02:26:01.688286:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.1.32.34:3551;branch=z9hG4bKe4bcbdc7015e4f62bcd4bdab905cfd7a;received=121.255.185.19;rport=3551
From: "2001" sip:3201@10.1.32.34:3551;tag=7a4df4ebb2d5430f8128211f8c37455b
To: sip:2001@172.25.0.2:3601;tag=gK90327p45c4j
Call-ID: 6dadae111eb345fd80b6965c761e6ccc@10.1.32.34:3551
CSeq: 157 INVITE
Contact: sip:172.25.0.2:3601
Content-Type: application/sdp
Content-Length: 239
v=0
o=- 1574303161 1574303163 IN IP4 121.182.10.18
s=c
c=IN IP4 121.182.10.18
t=0 0
m=audio 10598 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=maxptime:150
a=sendrecv
// ack with sdp
2019-11-21 02:26:01.753607 recv 703 bytes from udp/[121.255.185.19]:3551 at 02:26:01.753462:
ACK sip:2001@172.25.0.2:3601 SIP/2.0
Via: SIP/2.0/UDP 10.1.32.34:3551;branch=z9hG4bK60455c20dfa1438790e254689baf6451
From: "2001"sip:3201@10.1.32.34:3551;tag=7a4df4ebb2d5430f8128211f8c37455b
To: sip:2001@172.25.0.2:3601;tag=gK90327p45c4j
Call-ID: 6dadae111eb345fd80b6965c761e6ccc@10.1.32.34:3551
CSeq: 157 ACK
Contact: sip:2001@10.1.32.34:3551
User-Agent: K 2.2.2
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 238
v=0
o=AudiocodesGW 407398170 407398144 IN IP4 10.1.132.21
s=Phone-Call
c=IN IP4 10.1.32.34
t=0 0
m=audio 10974 RTP/AVP 8 101
c=IN IP4 10.1.32.34
a=sendrecv
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
The text was updated successfully, but these errors were encountered: