19 Jul
2021
19 Jul
'21
7:18 p.m.
Hi all,
I have a question for my kamailio configuration which works like this:
- INVITE arrives to kamailio
- HTTP async request to API endpoint
- Resume, use of rtjson module for parallel forking and loop to kamailio
itself
- One of the invite is "transformed" in serial forking with rtjson module
and it is sent with a delay to TWILIO SIP Domain (landline/mobile phone
numbers)
Twilio is giving me some troubles because it answers with a 200 OK but the
call it is still in establishing/ringing on the "landline" side and as
expected when reaching the timeout (no answer from phone number on TWILIO
side) kamailio is receiving a BYE.
Now the question, how to handle next number to call through Twilio?
I was thinking of using rtjson_next_route() when handling the in-dialog BYE
but as it is not a failure route so it does not work, or I'm doing it wrong.
Thanks in advance for any help/hint.
Filippo
19 Jul
19 Jul
7:39 p.m.
I think what you’re asking is: if a call is answered and hung up, can Kamailio make
another call to somewhere else?
If so, the answer is no; proxies just can’t do that. Forking deals with the management
early-stage requests during their pendency. Once a final dispositive reply for a request
is received from the upstream UA, the transaction is finished. Kamailio cannot initiate
new transactions in that sense.
So, to roll over to another route after an answer+hangup, you’d need to implement this on
the calling UA side.
Is that an accurate understanding of your question?
—
Sent from mobile, with due apologies for brevity and errors.
On Jul 19, 2021, at 12:19 PM, Filippo Graziola
<filippo.graziola(a)gmail.com> wrote:
Hi all,
I have a question for my kamailio configuration which works like this:
- INVITE arrives to kamailio
- HTTP async request to API endpoint
- Resume, use of rtjson module for parallel forking and loop to kamailio itself
- One of the invite is "transformed" in serial forking with rtjson module and
it is sent with a delay to TWILIO SIP Domain (landline/mobile phone numbers)
Twilio is giving me some troubles because it answers with a 200 OK but the call it is
still in establishing/ringing on the "landline" side and as expected when
reaching the timeout (no answer from phone number on TWILIO side) kamailio is receiving a
BYE.
Now the question, how to handle next number to call through Twilio?
I was thinking of using rtjson_next_route() when handling the in-dialog BYE but as it is
not a failure route so it does not work, or I'm doing it wrong.
Thanks in advance for any help/hint.
Filippo
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
21 Jul
21 Jul
9:09 a.m.
Hi, thanks for answering. Based on your answer I was able to move the
call sequence to Twilio instead of handling in kamailio, now I send
the INVITE from kamailio to Twilio and in Twilio make a request to my
own API endpoint to create the call sequence and call logs.
thanks
Filippo
I think what you’re asking is: if a call is answered and hung up, can
Kamailio make another call to somewhere else?
If so, the answer is no; proxies just can’t do that. Forking deals
with the management early-stage requests during their pendency. Once a
final dispositive reply for a request is received from the upstream
UA, the transaction is finished. Kamailio cannot initiate new
transactions in that sense.
So, to roll over to another route after an answer+hangup, you’d need
to implement this on the calling UA side.
Is that an accurate understanding of your question?
Il giorno lun 19 lug 2021 alle ore 18:18 Filippo Graziola <
filippo.graziola(a)gmail.com> ha scritto:
Hi all,
I have a question for my kamailio configuration which works like this:
- INVITE arrives to kamailio
- HTTP async request to API endpoint
- Resume, use of rtjson module for parallel forking and loop to kamailio
itself
- One of the invite is "transformed" in serial forking with rtjson module
and it is sent with a delay to TWILIO SIP Domain (landline/mobile phone
numbers)
Twilio is giving me some troubles because it answers with a 200 OK but the
call it is still in establishing/ringing on the "landline" side and as
expected when reaching the timeout (no answer from phone number on TWILIO
side) kamailio is receiving a BYE.
Now the question, how to handle next number to call through Twilio?
I was thinking of using rtjson_next_route() when handling the in-dialog
BYE but as it is not a failure route so it does not work, or I'm doing it
wrong.
Thanks in advance for any help/hint.
Filippo
1223
days inactive
1225
days old
2 comments
2 participants
participants (2)
-
Alex Balashov -
Filippo Graziola