Return appropriate "Congestion" message rather than 486 "Busy Here"

Started by MichiganTelephone, February 16, 2011, 06:55:43 PM

Previous topic - Next topic

MichiganTelephone

If you are using the OBi as a gateway from a FreePBX server, and you try to send more calls to a particular service than it will accept (for example, a second call to the LINE port when there is already a call in progress), FreePBX shows this:

Got SIP response 486 "Busy Here"

And apparently, it considers that the same as a line busy signal, so it won't allow the call to move on to another trunk.  You can overcome this by using the "Maximum Channels" setting on the trunk, but since the OBi can potentially be used as a gateway to up to three different services (the Line port, the OBiTALK network, and whatever you may have on the other service provider slot, not to even mention the possibility of accessing the auto-attendant), using Maximum Channels could easily block calls that could in fact complete (for example, the Line port may be in use, but the OBi could still bridge a call to a Google Voice account on the other Service Provider slot).

So what I'm asking for is an option, perhaps a checkbox or dropdown, that would let you choose to return a congestion message of some kind rather than "Busy Here", so that FreePBX and Asterisk can properly "fall through" to the next available trunk, if there is one available.  I'm not actually sure which SIP response might be the best, since none are explicitly labeled "congestion", though my suspicion is that 503 Service Unavailable would serve the purpose (anyone who knows more about SIP response codes than I do, feel free to chime in).  The only other likely candidate I see is 480 Temporarily Unavailable and I'm not sure if Asterisk would treat that any differently than a 503.  All I know is that in my testing there doesn't appear to be any way to get FreePBX and Asterisk to interpret 486 as congestion.

Oh, and if you wonder how the FreePBX developers feel about this sort of thing...
http://dev.freepbx.org/forum/possible-trunk-failover-problem
Bottom line is it's highly unlikely they will make any changes.
Inactive, no longer posting or responding to messages.  Goodbye and good luck.  Some of my old Obihai-related blog posts have been moved to http://tech.iprock.com - note this in NOT my blog; I have simply given the owner permission to repost some of my old stuff.

ShermanObi

This issue will be addressed in an upcoming firmware release.

MichiganTelephone

Inactive, no longer posting or responding to messages.  Goodbye and good luck.  Some of my old Obihai-related blog posts have been moved to http://tech.iprock.com - note this in NOT my blog; I have simply given the owner permission to repost some of my old stuff.