Re: [reSIProcate] Custom SRV lookups

[Alan Hawrylyshen <alan@xxxxxxxxxx>]

On Apr 26, 2005, at 15.55, Sandeep Sharma wrote:

> I know this is not the SIP standard way (RFC 3263), but in some cases
> the SIP domains may want to advertise their availability only to
> partners that know about this CUSTOM SRV lookup (and not to everyone).
>
> Initiating proxies you may want to differentiate one type of SIP 
> domains
> from another type (for business reasons) based on custom SRV lookups.

This is a very unusual requirement and potentially not the best way to 
achieve the result.

> Does resiprocate provide a configurable way to achieve that? Anyone 
> else
> having to do it?

This isn't a problem with resiprocate per-se but a problem with the RFC 
and/or the mechanism your partners have chosen to implement. The NAPTR 
-> SRV mapping is the point where this can be controlled. If you want 
to use an alternate SRV record name you can map the NAPTR query to the 
alternate name.  If you are trying to setup an alternate SRV 
nomenclature that isn't SIP related then you'd have to modify 
reSIProcate to do this.  I think the approach you are proposing is 
fraught with danger. Perhaps the general SIP community and suite of 
protocols already solves the problem you have.  Can you post a 
description of the desired end result and requirements?

Love to help, but want to discourage proliferation of non-standard 
solutions in a space where there are many, many ways to skin the cat 
already.

Alan Hawrylyshen

Alan Hawrylyshen
reSIProcate Project Administrator
http://resiprocate.org/
a l a n a t j a s o m i d o t c o m