On Thu, 2009-03-05 at 15:34 -0500, Paul Mossman wrote: > Hi all, > > I'm looking into XTRN-419: MOH dialogs not terminated, where the > Polycom fails to send BYE to sipXpark. I am not able to reproduce > this on my system. > > One thing I notice in the attached 5dd1870e-d761efbb-7b9706bc.xml > siptrace is that sipXpark sends three separate OPTIONS requests to the > Polycom in the MOH dialog. That doesn't happen in my system, and is > probably has something to do with why my Polycom correctly sends the > BYE. > > I understand that this is legal for sipXpark to send the OPTIONS > requests. But I don't understand why it would need to do this at all, > since the options being queried are all advertised in the INVITE. I > also don't understand why it sends the second and third OPTIONS > requests, since it got an answer the first time. > > Can anyone tell me why sipXpark does this, and under what > conditions?
Do you have a trace? The sipXcallLib sends OPTIONS if it does not see an Accept header in the original INVITE (it's trying to see if the caller supports REFER), but I'm sure that's not the whole story. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
