[OpenSIPS-Users] event_rabbitmq connection closed

[Răzvan Crainea]

Hello!

What you can do is to use the event_virtual module[1] to failover to a 
new method in case one is down. Using the FAILOVER mode, you could add 
another rabbitmq connection that will only be used in case the first one 
is down/closes the connection.

[1] http://www.opensips.org/html/docs/modules/2.3.x/event_virtual.html

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 10/03/2016 01:05 PM, Чалков Артём wrote:
> Hello everyone!
> I use event_rabbitmq on opensips v.2.1.3.
> My config:
>         if (!raise_event("E_SIP_CALL", $avp(rabb_message))) {
>                 xlog("L_ERR", "[RABBITMQ] cannot raise E_SIP_CALL1 
> event ");
>         } else {
>                 xlog("L_INFO", "[RABBITMQ] E_SIP_CALL1 event raised ");
>         }
> My rabbitmq-server sometimes closes TCP-connection, closed by opensips 
> and i see errors like that:
> Oct  3 11:08:48 opensips-pres /usr/sbin/opensips[8057]: [RABBITMQ] 
> E_SIP_CALL1 event raised
> Oct  3 11:08:48 opensips-pres /usr/sbin/opensips[8033]: 
> ERROR:event_rabbitmq:amqp_check_status: Connection closed
> Oct  3 11:08:48 opensips-pres /usr/sbin/opensips[8033]: 
> ERROR:event_rabbitmq:rmq_error: closing channel: (end-of-stream)
> Oct  3 11:08:48 opensips-pres /usr/sbin/opensips[8033]: 
> ERROR:event_rabbitmq:rmq_error: closing connection: (end-of-stream)
> Oct  3 11:08:48 opensips-pres /usr/sbin/opensips[8033]: 
> ERROR:event_rabbitmq:rmq_process: cannot send message
> So, by the log, it seems like opensips don't understand that sending 
> is not successful and ,as consequence, i cant do any worakaround. 
> Could i somehow configure opensips to do some actions when TCP or AMQP 
> connection closes?
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20161003/c4299064/attachment-0001.htm>