[OpenSIPS-Users] msilo on failure_route
Dani Popa
dani.popa at gmail.com
Fri Feb 15 12:24:33 CET 2013
Thanks,
Dani
On Fri, Feb 15, 2013 at 1:22 PM, Bogdan-Andrei Iancu <bogdan at opensips.org>wrote:
> **
> Hi Dani,
>
> If you do parallel forking to all 5 registrations of the client and all
> fails, the failure route is triggered only once (as all branches belong to
> the same transaction and failure route is triggered when the transaction
> fails).
>
> So the final answer -> one time.
>
> Regards
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
>
> On 02/15/2013 12:22 PM, Dani Popa wrote:
>
> Five SIP clients with the same username.
>
> Dani
>
>
> On Fri, Feb 15, 2013 at 12:19 PM, Dani Popa <dani.popa at gmail.com> wrote:
>
>> Hi,
>>
>> Regarding msilo module and example from the documentation, one simple
>> question:
>>
>> if i have 5 clients already registered and non of them know IM(message
>> sip method), on next failure_route(it was taken from modules
>> documentation). haw many times the message is stored in database ? In fact
>> the question is, because of sip forking, how many times the IM message is
>> stored in db with m_store on failure_route.
>>
>> Thanks,
>> Dani
>>
>> failure_route[1] {
>> # forwarding failed -- check if the request was a MESSAGE
>> if (!method=="MESSAGE")
>> {
>> exit;
>> };
>>
>> log(1,"MSILO:the downstream UA doesn't support MESSAGEs\n");
>> # we have changed the R-URI with the contact address, ignore it now
>> if (m_store("$ou"))
>> {
>> log("MSILO: offline message stored\n");
>> t_reply("202", "Accepted");
>> }else{
>> log("MSILO: offline message NOT stored\n");
>> t_reply("503", "Service Unavailable");
>> };
>> }
>>
>>
>> --
>> Dani Popa
>>
>
>
>
> --
> Dani Popa
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
--
Dani Popa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130215/19fd0149/attachment.htm>
More information about the Users
mailing list