just50415 / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
0 stars 0 forks source link

No 3263 support, port required on outbound proxy #14

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Configure the outbound proxy without a port.

What is the expected output? What do you see instead?

Ideally, using an outbound proxy with no port should cause NAPTR/SRV lookups to 
be used as specified in 3263 (which will result in TCP being used if DNS is set 
up to prefer it). Instead, no DNS lookups are performed, and no SIP traffic is 
observed. (As I understand it, you are using the NIST JAIN SIP stack, which has 
a 3263-compliant resolver here: 
http://code.google.com/p/jain-sip-rfc3263-router/ )

What version of the product are you using? On what operating system?
2.2.0 on emulator (OS X)

Please provide any additional information below.

Original issue reported on code.google.com by docfara...@gmail.com on 15 Mar 2011 at 3:56

GoogleCodeExporter commented 8 years ago
Thanks for this information.

But as it said in the RCs-e standard, the UE contains (or reads via OTA) the 
proxy configuration (IP:port or FQDN:port). So I think RFC3263 is not mandatory 
here.

Original comment by jmauffret@gmail.com on 16 May 2011 at 9:15