Hi, i've just noticed the following behaviour: If a client sends a REGISTER to fetch it's bindings (e.g. from different AVM FritzBox'es), the REGISTER does not contain a "Contact"-Header and no expires (the Call-ID however is the same as in previous REGISTER-messages). This is valid according to RFC 3261, Chapter 10.2.3 "Fetching bindings":
10.2.3 Fetching Bindings A success response to any REGISTER request contains the complete list of existing bindings, regardless of whether the request contained a Contact header field. If no Contact header field is present in a REGISTER request, the list of bindings is left unchanged. (http://tools.ietf.org/html/rfc3261#section-10.2.3) In this case, the REGISTER is not cached and forwarded towards the core. No registration unloading takes place. Is this wanted? Thanks, Carsten -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany http://www.ng-voice.com mailto:[email protected] Office +49 40 5247593-0 Fax +49 40 5247593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/ _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
