[reSIProcate] Mulitple ENUM Servers

[Scott Godin]

FYI - I've looked at this solution and there appears to be a number of
issues:

 

Note:  Each ENUM server in the list is queried at the same time - I'm
not sure if this is correct.

1.        If all ENUM servers return not-found or error then mDoingEnum
and mNumSuffixes never get reset and we do not fallback to
lookupInternal.

2.       Changes to onDnsResult - looks like they will break normal DNS
resolution - ie. if mNumSuffixes is 0, then we do not call
onNaptrResult.

 

Scott

 

From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of
FrankYuan
Sent: Wednesday, March 22, 2006 6:10 PM
To: Jason Fischl
Cc: resiprocate-devel at list.sipfoundry.org
Subject: Re: [reSIProcate] Mulitple ENUM Servers

 

Jason,

I have implemented and tested the changes to support more than ENUM DNS
servers.

Here are changes:
1. added variable mNumSuffixes in DnsResult.hxx
2. modified lookup() ,  onDnsResult(), and onEnumResult() in
DnsResult.cxx.

DnsResult.hxx and DnsResult.cxx are attached.
Feel free to modify or check in if you think these changes are ok.



Thanks
 
Frank Yuan
Emergent-Netsolutions.com
972-359-6600



Jason Fischl wrote: 

	Is StatelessHandler solidly tested or not?
	 
	Will it be deprecated or not?
	 
	    

 
StatelessHandler is deprecated.
 
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060803/48298d4c/attachment.htm>