Sounds good - but I do not know howo to handle that.
Do you have a config example?
Von: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] Im Auftrag von Carsten Bock
Gesendet: Sonntag, 24. November 2013 20:52
An: SR-Users
Betreff: Re: [SR-Users] error handling
er.org] *Im Auftrag von *Brandon Armstead
> *Gesendet:* Sonntag, 24. November 2013 20:41
> *An:* Kamailio (SER) - Users Mailing List
> *Cc:* Kamailio (SER) - Users Mailing List
> *Betreff:* Re: [SR-Users] error handling
>
>
>
> Acc_db_request
>
> Sent from my iPhone
>
&g
uot;, "not found");
exit;
}
Von: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] Im Auftrag von Brandon Armstead
Gesendet: Sonntag, 24. November 2013 20:41
An: Kamailio (SER) - Users Mailing List
Cc: Kamailio (SER) - Users Mailing List
Betr
Acc_db_request
Sent from my iPhone
> On Nov 24, 2013, at 11:20 AM, Oliver Roth wrote:
>
> Hi all
>
> Question about error handling with kamailio.
>
> We send call to carrier and get back error 404.
> In carrierfailureroute we catch up this error and send call to an internal
> freeswitch th
Flag the call as missed internally in your accounting or write to the missed
acc table there is a method in acc documentation.
Sent from my iPhone
> On Nov 24, 2013, at 11:20 AM, Oliver Roth wrote:
>
> Hi all
>
> Question about error handling with kamailio.
>
> We send call to carrier and
Hi all
Question about error handling with kamailio.
We send call to carrier and get back error 404.
In carrierfailureroute we catch up this error and send call to an internal
freeswitch that plays a voiceprompt saying: "destination not available"
In accounting this calls is collected like a "no
