Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JsSIP stack enforces its own minimum expires on response to register. #52

Closed
anthmFS opened this issue Jan 25, 2013 · 1 comment
Closed

Comments

@anthmFS
Copy link

anthmFS commented Jan 25, 2013

JsSIP has a param register_min_expires that is set to 120. If a REGISTER has a 200OK with the expires param, its bound to honor that expires time. It cannot decide to do a higher value or the registration will be invalid during the delta between the 2.

from RFC 3261 section 10.3 Processing REGISTER Requests

  1. The registrar now processes each contact address in the Contact
    header field in turn. For each address, it determines the
    expiration interval as follows:

     -  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.
    
@jmillan
Copy link
Member

jmillan commented Jan 25, 2013

You are right @freeswitch.

Thanks for reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants