[asterisk-dev] Introducing: Earl Grey : sip2cause.conf
Andrew Latham
lathama at gmail.com
Wed Nov 28 14:11:10 CST 2012
On Wed, Nov 28, 2012 at 3:02 PM, Olle E. Johansson <oej at edvina.net> wrote:
>
> 28 nov 2012 kl. 15:00 skrev Andrew Latham <lathama at gmail.com>:
>
>> On Wed, Nov 28, 2012 at 8:27 AM, Olle E. Johansson <oej at edvina.net> wrote:
>>> Friends,
>>> I just opened up a new branch for a small hack. There is a need in some very strange and unusual installations to be able to manipulate the sip-ISDN cause/response code tables. These are the ones used to convert from SIP codes to ISDN cause codes at hangup.
>>>
>>> The Earl Grey branch aims to make these configurable in a separate configuration file, sip2cause.conf, that will be needed in just a few cases, but for these cases, it's important. The branch will be created based on 1.8 LTS, but will hopefully also be ported to trunk.
>>>
>>> If you have any input on these conversions and how you like to be able to use them, now is the time to speak up!
>>>
>>> Cheers,
>>> /O
>>
>> I just read the README. Looks like fun when time is abundant. Could
>> you add a use case to the README file?
>
> I will. Like:
>
> "If you have a SIP proxy in front of Asterisk and want to send different hangup causes depending on if a 408 is local
> or remote. For a local one, you could invent a code, say 499, and translate that to the hangup cause you want,
> so that processing in the dialplan is different for a local or a remote timeout from the proxy."
>
> This is hard core stuff, for people who have full control of the platform used ;-)
> Previously it has caused patching asterisk unfortunately.
>
> /O
Sounds awesome, we await some silly examples with funny names to
explain these complex use cases. :D
--
~ Andrew "lathama" Latham lathama at gmail.com http://lathama.net ~
More information about the asterisk-dev
mailing list