| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
On 2/11/10 14:03, Feb 11, Richard Stellingwerff wrote:
I didn't look at the contact header, I was looking for an expires header since that's what I saw in the REGISTER. In the contact header there is "<sip:1002@xxxxxxxxxxxxx:22080;rinstance=389fea2abfbcf67c>;expires=1200" Technically, in the REGISTER request, the expiration can be sent in either a Contact "expires" parameter or in a separate Expires header field: - If the field value has an "expires" parameter, that value MUST be taken as the requested expiration. - If there is no such parameter, but the request has an Expires header field, that value MUST be taken as the requested expiration. - If there is neither, a locally-configured default value MUST be taken as the requested expiration. However, it is possible that your registrar isn't set up to look for it in the Contact header field, in which case moving it to the Contact might fix the issues you're seeing. But that would just be a work-around. In any case, the registrar is out of spec in one way or another (either ignoring the Expires header field, or illegally lengthening the expiration), and a bug report for the registrar vendor is definitely in order. /a
|