[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  Koochy Black <koochy@a...>
 Subject :  Re: [yate] Sending Error Codes, when routing is done in Database
 Date :  Thu, 13 Aug 2009 11:51:41 +0200
Thank you Monica...it's now working....I've changes the offlineauto to
no....it was uncommented but default was yes...

Thank you!
monica schrieb:
> Hi,
>
> Your b) case should work. Case a) won't work, register does not work
> as regexroute where you can add more params by separating them with ;
> For each param you want to add you must add a new column in the
> returned row.
>
> If you want to return a custom error make sure that offlineauto=no in
> [call.route] section. If it's set to yes and location in result is
> null then error will be set to offline automatically.
>
> Regards,
>
> Monica Tepelus
>
> Koochy Black wrote:
>> Hi again,
>>
>> We have set-up routing via database..it's working pretty good...but I've
>> some problems sending error codes back to yate.
>> Example:
>>
>> In regexroute.conf sending error workls like:
>> ^123456789$=-;error=noconn
>>
>> but if I try to make in database it wont work. I've tried some
>> variations:
>> a)    Giving error code back in the action/location field
>>  +-----------------------------------------------------------------+-------+-----------+
>>
>> | location                                                          
>>                             | error | context   |
>> +-----------------------------------------------------------------+-------+-----------+
>>
>> | -;error=busy  | NULL  | sn-xxx |
>> +-----------------------------------------------------------------+-------+-----------+
>>
>> I've tried location='error=noauth'...did not work.....
>>
>> b)    Giving error code in a error filed
>> +-----------------------------------------------------------------+-------+-----------+
>>
>> | location                                                        |
>> error | context   |
>> +-----------------------------------------------------------------+-------+-----------+
>>
>> | NULL | busy | sn-xxx|
>> +-----------------------------------------------------------------+-------+-----------+
>>
>>
>> c) Giving error code in reason / code Field
>>
>>
>> But all variation did not work. Do someone have a hint for me.
>>
>> Thanks in advance
>>