Re: Proxy port question

Hi luis,

One way would be for the client to support DNS SRV lookups (see http://www.voip-info.org/wiki-DNS+SRV). Given a domain name, those give you both the IP address and the port (as opposed to DNS A records, which only give the IP address)

Address resolution in SIP is governed by RFC3263 (http://www.faqs.org/rfcs/rfc3263.html)

To my knowledge, the current reference implementation only supports DNS A lookups (the ones that Java performs when you say 'InetAddress.getByName')

Regards,

Jeroen

  ----- Original Message ----- 
  From: Luis Alberto Teixeira 
  To: [email protected] 
  Sent: Wednesday, April 26, 2006 3:52 PM
  Subject: [nist-sip] Proxy port question


  Hi,

   

  I'm placing a doubt that possibly intersects the obvious. In a host where we are able to run more than one service using  the SIP protocol, it might be the case that our target service (for example a SIP Proxy) might not be able to run using the default 5060 port, as another service already have taken this port. So we cause it to run on a different port, like 5075 for example. On the client side, where ultimately it should not be aware of which port the proxy  listens to requests, how can this "discovery" be achieved (if indeed it can), in order to allow signaling to be exchanged between entities agnostic to each other's settings?

   

  Thanks.

   

  Luis Teixeira

   

   



------------------------------------------------------------------------------


  _______________________________________________
  nist-sip mailing list
  [email protected]
  http://www-x.antd.nist.gov/mailman/listinfo/nist-sip

_______________________________________________
nist-sip mailing list
[email protected]
http://www-x.antd.nist.gov/mailman/listinfo/nist-sip