20 Jun
2011
20 Jun
'11
12:15 a.m.
Is it possible to configure sip-router to keep a transaction for an incoming message (f.e.
an INVITE) without sending a response and without forwarding it, and then reference and
complete it in the future?
Using pseudocode this is the logic I would like to implement:
//When receiving an INVITE leave it pending
if (request is INVITE) {
store transactionID // This transactionID will be send somehow to the client
return
}
//When receiving a PUBLISH referencing a pending transaction complete the forwarding
if (request is PUBLISH) {
transactionId = header("X-TransactionId")
destination = header("X-Destination")
transactions [transactionID]. forward(destination)
}
Thank you very much,
G.
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
20 Jun
20 Jun
12:20 a.m.
There is no support for this. Kamailio in its proxy role (the role
you are invoking) is pretty much event-driven, in the sense that it's
processing is real-time and correlated to the receipt of messages to
be forwarded. It is externally stimulated into action.
Also, it would be quite problematic from the perspective of SIP
protocol mechanics. If you do not even send 100 Trying, the sending
UAC will retransmit the INVITE, and/or eventually assume your proxy is
down. If you do send 100 Trying but do not follow up, other timers
awaiting final positive or negative replies kick in and also expire.
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
11:06 a.m.
On Monday 20 June 2011, Gustavo Garcia Bernardo wrote:
Is it possible to configure sip-router to keep a
transaction for an
incoming message (f.e. an INVITE) without sending a response and without
forwarding it, and then reference and complete it in the future?
Using pseudocode this is the logic I would like to implement:
[..]
Hi Gustavo,
as Alex already wrote, its probably not the best or correct thing to do - but
have you already looked to the tm module? It provides some asynchronous
support. From the module README:
"[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."
Maybe this is helpful,
Henning
11:21 a.m.
Hi Henning,
On 06/20/2011 05:06 AM, Henning Westerholt 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?
Thanks,
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
11:39 a.m.
On Monday 20 June 2011, Alex Balashov wrote:
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
"[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?
1:41 p.m.
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(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org]
On Behalf Of Henning Westerholt
Sent: lunes, 20 de junio de 2011 11:40
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] Keeping transactions in standby till future events
On Monday 20 June 2011, Alex Balashov wrote:
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(a)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
"[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?
3:29 p.m.
2011/6/20 Henning Westerholt <henning.westerholt(a)1und1.de>de>:
as Alex already wrote, its probably not the best or
correct thing to do - but
have you already looked to the tm module? It provides some asynchronous
support. From the module README:
"[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."
Hi Henning, which would be the difference if the script does
t_newtran(), then reply 100 trying (of before) and then exit()?
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
4:08 p.m.
2011/6/20 Iñaki Baz Castillo <ibc(a)aliax.net>et>:
Auto reply: I think it would just generate a "ready-to-expire" server
transaction.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
"[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."
Hi Henning, which would be the difference if the script does
t_newtran(), then reply 100 trying (of before) and then exit()?
4719
days inactive
4720
days old
7 comments
4 participants
participants (4)
-
Alex Balashov -
Gustavo Garcia Bernardo -
Henning Westerholt -
Iñaki Baz Castillo