[SIPForum-techwg] SIPconnect/1.1 v03 onlist - section 7.1.4.1.6 "Other 4xx Responses"

Spencer Dawkins spencer at wonderhamster.org
Wed Feb 4 10:48:10 EST 2009


The current text in this section says

1.1.1.1.1         Other 4xx Responses
 

Any 4xx-class response to a REGISTER request not explicitly identified above SHOULD be treated in a similar manner as section 7.1.4.1.1 unless it can automatically be resolved by the SIP-PBX internally - i.e., unless it is part of an explicit negotiation mechanism or procedure.  It SHOULD be treated as a delivery failure but with a higher maximum retry interval of 960 seconds (16 minutes).  

 

Spencer: John pointed out that the one-day maximum retry interval (for other 4xx responses) is way longer than the 16 minutes for 5xx/6xx specified below. Does this make sense to people? Should 5XX/6XX also be one-day? Telechat decision was to discuss onlist.


I had made a change for these 4xx responses to be 16 minutes (that's what the text says in my working copy) to match 5xx/6xx, but people on the call weren't comfortable with that.

I'm not seeing one-day retry intervals for enterprise PBXes as reasonable, in either case. My inclination is to leave the current text at 16 minutes for both 4xx and 5xx/6xx responses, but I wanted to check with the working group before making that decision.

Thoughts?

Thanks,

Spencer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/pipermail/techwg/attachments/20090204/81c09adc/attachment-0001.html 


More information about the techwg mailing list