On Sun, 2006-11-19 at 20:38 +0800, yuhang wrote: > Hi, > > Charlie wrote: > >The XXX server on 192.168.0.254 is not following the protocol. There > must be Expires information, either as a header or as a parameter on a > contact entry. > Thanks for Charlie's reply, and here's my opinion:
> 1) As far as i know, the Expires header is optional and the expires > parameter on a contact entry is not mandatory. but you must have one or the other. > 2) The problem here is that sipXtapi neither fires an event that > indicates a REGISTER failour nor an an event that indicates a REGISTER > success. I think sipXtapi should fire something even though it > receives a malformatted 200 OK message. (time out for example, if > sipXtapi can not recognize the malformatted 200 OK message) Since > sipXtapi may not deal with a malformatted 200 OK message properly, > UNREGISTERED event may not fired either. Trying to infer what was meant by a broken message is always a perilous thing to do. sipXtapi should certainly fire an event if/when the registration times out. > 3) When unregistering, sipXtapi doesn't include any expires > information in REGISTER message. Well, sometimes it does include > EXPIRES=0 parameter (notices that it is upper case) in Contacts > header. But it seems that OnDo Server can recognize neigher of the > unregister message. The OnDo Server always include "expires=3600" in > 200 OK message when replying sipXtapi's unregister message. So, i > think it's better to always include "expires=3600;" in REGISTER > message when sipXtapi tries to unregister. The 'expires' parameter token (indeed, all elements defined as 'token' in SIP) is by definition case insensitive. If some server is not recognizing it in upper case, that's a bug in the server. -- Scott Lawrence tel:+1-781-938-5306;ext=162 or sip:[EMAIL PROTECTED] sipXpbx project coordinator - SIPfoundry http://www.sipfoundry.org/sipX Chief Technology Officer - Pingtel Corp. http://www.pingtel.com/ _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
