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...

Cheers,
bob
_______________________________________________
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