> -----Original Message-----
> From: Lawrence, Scott (BL60:9D30) 
> Sent: Monday, December 15, 2008 11:39 AM
> To: Joly, Robert (CAR:9D30)
> Cc: [email protected]
> Subject: Re: [sipX-dev] SIP messages misrouted inside sipXecs
> 
> 
> On Mon, 2008-12-15 at 11:26 -0500, Robert Joly wrote:
> > Hi,
> > A number of odd behaviors were reported today including 
> remote worker 
> > not working and basic calls generating an abnormally large 
> number of 
> > ACKs leading to endpoints timing out.
> > 
> > I looked into these problems and found that they had a common root 
> > cause which is that the sipXproxy does not see the INVITEs 
> resulting 
> > from the 302 redirection.  This behavior is caused by the fact that 
> > sipXregistrar does not call the AuthRouter redirect plug-in which 
> > normally ensures that sipXproxy sees these redirected INVITEs.
> > Further investigation revealed that this plug-in wasn't 
> called because 
> > it was preceded in the registrar-config file by the 
> HuntGroup redirect 
> > plug-in who is no longer with us :) That caused the 
> Redirect Server to 
> > skip all redirect plug-ins that followed it.  The 
> short-term fix which 
> > I will commit shortly is to remove the HuntGroup redirect 
> plug-in from 
> > the registrar configuration file but once this is done, I'll try to 
> > figure if there is an easy way to harden the SIP Redirect server to 
> > cope with plug-ins whose library won't load...
> 
> I removed the hunt group plugin last week... I didn't find it 
> configured anywhere - was your registry configuration 
> generated by sipXconfig?

Yes it was and it is generated based on velocity template
sipXconfig/neoconf/etc/sipxregistrar/registrar-config.vm.

> 
> I know I fixed the problem with non-loading plugins at least 
> once before, but it may have been in a different plugin chain.

I'll look into that later today.  A config file with stale plug-in
entries should not prevent the good ones from being used.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to