[OpenSIPS-Users] rabbit event not passing params 2.2

[Răzvan Crainea]

Hi, Tito!

Can you raise an event from a different application with the same 
routing-key (sip1dev) and the same exchange("")? Does it work? if it 
does, can you send me the trace for the working one?

Best regards,
Răzvan

On 02/02/2016 02:57 AM, Tito Cumpen wrote:
> Razvan,
>
> Here is the trace. Please let me know if you need anything else. Also 
> I remember there was mention of a user replication module coming out 
> for 2.X that would allow servers to be aware of users registered on 
> other opensips registrars.
>
>
> Thanks,
> Tito
>
> On Tue, Jan 26, 2016 at 3:42 AM, Răzvan Crainea <razvan at opensips.org 
> <mailto:razvan at opensips.org>> wrote:
>
>     Hi, Tito!
>
>     Can you send me a trace?
>
>     Thanks,
>     Răzvan
>
>
>     On 01/25/2016 10:41 PM, Tito Cumpen wrote:
>>     Hey Razvan,
>>
>>     This is still an issue with the latest dev build. The event is
>>     entirely empty when it is transmitted to the queue. I've tried
>>     modparam("event_rabbitmq", "sync_mode", 1) but it does not make a
>>     difference.
>>
>>     THanks,
>>     Tito
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>     -- 
>     Răzvan Crainea
>     OpenSIPS Core Developer
>     http://www.opensips-solutions.com
>
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto: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

-- 
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160202/52fb41e5/attachment.htm>