Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Sip-Servlets MSS-3.0.0.FINAL
Roadmap-Fix
New issue 249 by [email protected]: Connection to only 2 SRV records in
DNS Lookup are Attempted
http://code.google.com/p/sipservlets/issues/detail?id=249
What steps will reproduce the problem?
1. Setup DNS Server (bind or dnsmasq) to return 4 SRV records for _sip._udp
for yourdomain.com with same priority (10) and same weightage (25) and
pointing to some ports on your local machine.
2. Write a simple app to create and send a new Sip Message request to
[email protected] domain as Route header.
3. Deploy and start the app. Capture the generated Sip requests over UDP
using wireshark
What is the expected output? What do you see instead?
Mobicents should initiate Sip Transaction to first target over UDP
transport. In case of no response (transaction timeout of 32 seconds),
invoke connection to second target and so on.
However, observed that Mobicents tries only 2 of the target IP/Ports (based
on Priority/Weightage) and not 3rd/4th targets.
What version of the product are you using? On what operating system?
mss-1.7.0.FINAL-apache-tomcat-6.0.35 on Redhat 6
Please provide any additional information below.
Section 4.3 of RFC 3263 mentions following procedure to process outgoing
SIP request for which multiple SRV records are returned in DNS lookup:
For SIP requests, failure occurs if the transaction layer reports a
503 error response or a transport failure of some sort (generally,
due to fatal ICMP errors in UDP or connection failures in TCP).
Failure also occurs if the transaction layer times out without ever
having received any response, provisional or final (i.e., timer B or
timer F in RFC 3261 [1] fires). If a failure occurs, the client
SHOULD create a new request, which is identical to the previous, but
has a different value of the Via branch ID than the previous (and
therefore constitutes a new SIP transaction). That request is sent
to the next element in the list as specified by RFC 2782.
As mentioned here, no limit has been defined on SRV records to which Sip
Request should be sent out.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
