Furthermore @tdixon81 the ticket system is not a place to ask questions. It is a place to report bugs, submit improvements and add feature requests. Its not a place to go to for āsupportā or to ask questions about how the product works. Especially when you asked relatively the same thing in this thread except accused Sangoma of trying to get $$$ because of a setting that has documentation copied over from Asterisk that you couldnāt understand.
I am submitting this ticket to request more information on all of the Asterisk SIP Settings. For instance - when you see 423 Interval too brief, āā¦,ā minimum 3600 seconds - what is that and where is it coming from? What registry setting will do the trick?
A quick google search lead me to the RFC for the SIP protocol and specifically your error of 423 (RFC 3261 - SIP: Session Initiation Protocol)
The server is rejecting the request because the expiration time of
the resource refreshed by the request is too short. This response
can be used by a registrar to reject a registration whose Contact
header field expiration time was too small. The use of this response
and the related Min-Expires header field are described in Sections
10.2.8, 10.3, and 20.23.
To me the error is clear. The server doesnāt like what you are telling it you want the expiration to be. In fact the server is going as far as telling you itās too short. Letting you know it needs to be increased.
If I follow this out and read section 20.23 I see
20.23 Min-Expires
The Min-Expires header field conveys the minimum refresh interval
supported for soft-state elements managed by that server. This
includes Contact header fields that are stored by a registrar. The
header field contains a decimal integer number of seconds from 0 to
(2**32)-1. The use of the header field in a 423 (Interval Too Brief)
response is described in Sections 10.2.8, 10.3, and 21.4.17.
Example:
Min-Expires: 60
If anything I would blame your provider who has failed to tell you that this is a required setting for them (not for SIPStation, Voip.ms, SIP.Usā¦ the list goes on). Although their server IS telling you about the misconfiguration with error code 423 and the Min-Expires header. However perhaps itās your provider looking to get more $$$ through support. Or in reality itās your provider who doesnāt want everyone to register to them every 60 seconds. Who knows why but youād have to ask them. (Also note that the Min-Expires in the RFC is 60 as well)
In this RFC there are over 40 responses a server can reply back with and each response can mean something different in the context of a call. Writing a wiki to describe all outcomes of all responses of all RFC responses would get out of control and would be different for each server, providerā¦ etc.
Furthermore you went and increased maxexpiry, minexpiry and defaultexpiry globally for all of your extensions when you should have just set these values on your trunks (in trunks). As now you will most-likely have registration issues with your phones.
FreePBX is a Unified Communications tool built on top of Asterisk. FreePBXās goal is to not explain everything to you for every setting that exists in Asterisk and how that setting relates to the over 40 different RFC responses a server replies with.
https://issues.freepbx.org/browse/FREEPBX-15674
*Note: I work for Sangoma and I provided this response for free.
than I initially thoughtā¦ 