[SR-Users] Keeping transactions in standby till future events

[Gustavo Garcia Bernardo]

Thank you, that is the functionality we needed but we were looking for something to be accessible from the script.   Perhaps we can build a module to export those APIs to the script, we will try it.

Best regards,
G.

-----Original Message-----
From: sr-users-bounces at lists.sip-router.org [mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of Henning Westerholt
Sent: lunes, 20 de junio de 2011 11:40
To: sr-users at lists.sip-router.org
Subject: Re: [SR-Users] Keeping transactions in standby till future events

On Monday 20 June 2011, Alex Balashov wrote:
> > "[t_supend] This function together with t_continue() can be used to
> > implement asynchronous actions: t_suspend() saves the transaction,
> > returns its identifiers, and t_continue() continues the SIP request
> > processing."
>
> These are just exported API functions though, right?  Not something
> that can be called from script?

Hi Alex,

yes, they are in the available in the public tm API:

int t_suspend(struct sip_msg *msg,
             unsigned int *hash_index, unsigned int *label)

int t_continue(unsigned int hash_index, unsigned int label,
             struct action *route)

Best regards,

Henning

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users at lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx