[Blink] Blink responds to SIP OPTIONS Message with "500 Unhandled by dialog usages"

[Adrian Georgescu]

The purpose of that Options is to keep the NAT bindings alive. As long as there is a response the goal has been achieved. A 200 or 500 response code does not really matter.

So there is nothing to solve here.

On Jul 17, 2011, at 10:11 PM, duane.larson at gmail.com wrote:

> The call continues. OpenSIPS will keep sending OPTIONS pings every X seconds while the call continues. It doesn't kill the call. 
> 
> On Jul 16, 2011 2:26am, Saul Ibarra Corretge <saul at ag-projects.com> wrote: 
> > Hi, 
> > 
> > 
> > 
> > 
> > 
> > On Jul 14, 2011, at 10:26 PM, duane.larson at gmail.com wrote: 
> > 
> > 
> > 
> > 
> > 
> > > I have just enabled OpenSIPS Dialog ping interval option that will monitor if a call is still active or dead. I have noticed that with a Counterpath Bria client or the Jitsi client when they receive the OPTIONS message from OpenSIPS they return a 200 OK, but the Blink client returns a 500 Unhandled by dialog usages. 
> > 
> > 
> > > 
> > 
> > 
> > 
> > 
> > 
> > What does OpenSIPS do when it receives a 500 reply to an in-dialog OPTIONS? Does it assume the dialog is dead? 
> > 
> > 
> > 
> > 
> > 
> > -- 
> > 
> > 
> > Saúl Ibarra Corretgé 
> > 
> > 
> > AG Projects 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________ 
> > 
> > 
> > Blink mailing list 
> > 
> > 
> > Blink at lists.ag-projects.com 
> > 
> > 
> > http://lists.ag-projects.com/mailman/listinfo/blink 
> > 
> > 
> >_______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink