[OpenSIPS-Users] MWI indicator when integrating with Asterisk

[Bogdan-Andrei Iancu]

Hi Schneur ,

If you want to fork a request to destinations A and B (SIP uris), you 
can do:

....
append_branch("A");
$ru = B;
t_relay();
....

More branches, more append_branch()'s in your cfg.

Regards,
Bogdan

On 10/27/2011 06:24 PM, Schneur Rosenberg wrote:
> Thanks for the quick answer, is there anyway I can fork the rewrite
> host to send to a few servers so anyone of them can activate or
> deactivate the MWI?
>
> On Thu, Oct 27, 2011 at 5:04 PM, Dani Popa<dani.popa at gmail.com>  wrote:
>> hi,
>>
>> load module presence_mwi
>>
>> and
>>
>> if(is_method("SUBSCRIBE")) {
>>    if (!has_totag()) {
>>              if (avp_check("$hdr(Event)", "eq/message-summary/i")) {
>>                rewritehostport("asterisk.host");
>>                record_route();
>>                if (!t_relay()) {
>>                   t_reply("500", "Server internal error");
>>                }
>>                exit;
>>             }
>>    }
>> }
>>
>>
>> Dani
>> On 10/27/11 17:34, Schneur Rosenberg wrote:
>>> We have a Opensips server that is used to load balance a few asterisk
>>> servers, the opensips also handles registration, but asterisk handles
>>> everything else, everything works fine but I don't know how to get MWI
>>> indicator to work, I tried rewritehostport for the SUBSCRIBE but it
>>> did not work, can anyone please help me with this.
>>>
>>> Thanks
>>> S. Rosenebrg
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 19th of September 2011
OpenSIPS solutions and "know-how"