This is really helpful development.
I am facing one issue, when I use this.
RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams.
Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment.
How can I avoid this? Any help is appreciated.
Thank you
Mitesh
That's great, thank you!
Cheers,
Daniel
On 06.09.18 11:15, Richard Fuchs wrote:
- This is now supported as per
*
*
- Cheers
*
- On 2018-09-05 05:39, Daniel-Constantin Mierla wrote:
*
- There is the dlg.terminate_dlg rpc command that requires callid,
*
- from-tag and to-tag as parameters:
*
*
*
- So it expects something like:
*
<?xml version="1.0" encoding="UTF-8"?>
*
<methodCall>
*
- <methodName>dlg.terminate_dlg</methodName>
*
<params>
*
<param><value><string>_CALLID_VALUE__</string></value></param>
*
<param><value><string>_FROM_TAG_VALUE__</string></value></param>
*
<param><value><string>_TO_TAG_VALUE__</string></value></param>
*
</params>
*
</methodCall>
*
- I planned to make the from-tag and to-tag optional for quite some
*
- time, but didn't get the time for it yet.
*
- Cheers,
*
- Daniel
*
- On 05.09.18 08:52, Richard Fuchs wrote:
*
- Yup that's exactly right.
*
- It would be fairly simple to implement an additional XMLRPC format
*
- if there's a particular one that's more friendly towards Kamailio.
*
- Cheers
*
- On 2018-09-05 02:42, Daniel-Constantin Mierla wrote:
*
- Looking quickly at the readme of rtpengine application and digging
*
- a bit with google, it is something like rtpengine has to be started
*
- with
*
- -b http(s)://myrpcserver.ip/path -x 1
*
- and then the xmlrpc request is going to be sent to that url, having
*
- a format like:
*
<?xml version="1.0" encoding="UTF-8"?>
*
<methodCall>
*
- <methodName>teardown</methodName>
*
<params>
*
<param><value><string>_CALLID_VALUE__</string></value></param>
*
</params>
*
</methodCall>
*
- Is it right? If yes, then I can try to make a sample config that
*
- could handle it using xmlops, xhttp and jsonrpcs modules.
*
- Cheers,
*
- Daniel
*
- On 05.09.18 08:24, Richard Fuchs wrote:
*
- It does an XMLRPC callback. Currently there's two formats for it,
*
- one is a sems sbc teardown request (using the from-tag), the other
*
- is a generic "teardown" command using the call ID.
*
- Cheers
*
- On 2018-09-04 07:52, Daniel-Constantin Mierla wrote:
*
- Hello,
*
- what do you get from rtpengine on rtp timeout? An RPC call back
*
- or an http request?
*
- Cheers,
*
- Daniel
*
- On 04.09.18 12:48, Igor Olhovskiy wrote:
*
>* Hi all!
*
>
>* Is there any way to end dialog in Kamailio on RTP Timeout event
*
>* on RTPEngine?
*
>
>* Or only look at logs/redis database with external tool?
*
>
>* Regards, Igor
*
>
>
>* _______________________________________________
*
>* Kamailio (SER) - Users Mailing List
*
>* sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
*
>* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
*
- --
*
- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com
*
- www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda
*
- Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com
*
- Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com
*
*
- Kamailio (SER) - Users Mailing List
*
- sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
*
*
*
- Kamailio (SER) - Users Mailing List
*
- sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
*
*
- --
*
- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com
*
- www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda
*
- Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com
*
- Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com
*
*
- Kamailio (SER) - Users Mailing List
*
- sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
*
*
- --
*
- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com
*
- www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda
*
- Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com
*
- Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com
*
*
- Kamailio (SER) - Users Mailing List
*
- sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
*
*
Hi,
Any thoughts on this?
Mitesh
On 26-Dec-2019, at 1:36 PM, Miteshkumar Thakkar mitesh.thakkar@plivo.com wrote:
This is really helpful development.
I am facing one issue, when I use this. RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams.
Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment. How can I avoid this? Any help is appreciated.
Thank you Mitesh That's great, thank you! Cheers, Daniel On 06.09.18 11:15, Richard Fuchs wrote:
This is now supported as per https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e67018... https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e6701822070a72
Cheers
On 2018-09-05 05:39, Daniel-Constantin Mierla wrote:
There is the dlg.terminate_dlg rpc command that requires callid, from-tag and to-tag as parameters:
https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_... https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_dlg
So it expects something like:
<?xml version="1.0" encoding="UTF-8"?>
<methodCall> <methodName>dlg.terminate_dlg</methodName> <params> <param><value><string>_CALLID_VALUE__</string></value></param> <param><value><string>_FROM_TAG_VALUE__</string></value></param> <param><value><string>_TO_TAG_VALUE__</string></value></param> </params> </methodCall>
I planned to make the from-tag and to-tag optional for quite some time, but didn't get the time for it yet.
Cheers, Daniel
On 05.09.18 08:52, Richard Fuchs wrote:
Yup that's exactly right.
It would be fairly simple to implement an additional XMLRPC format if there's a particular one that's more friendly towards Kamailio.
Cheers
On 2018-09-05 02:42, Daniel-Constantin Mierla wrote:
Looking quickly at the readme of rtpengine application and digging a bit with google, it is something like rtpengine has to be started with
-b http(s)://myrpcserver.ip/path -x 1
and then the xmlrpc request is going to be sent to that url, having a format like:
<?xml version="1.0" encoding="UTF-8"?>
<methodCall> <methodName>teardown</methodName> <params> <param><value><string>_CALLID_VALUE__</string></value></param> </params> </methodCall>
Is it right? If yes, then I can try to make a sample config that could handle it using xmlops, xhttp and jsonrpcs modules.
Cheers, Daniel
On 05.09.18 08:24, Richard Fuchs wrote:
It does an XMLRPC callback. Currently there's two formats for it, one is a sems sbc teardown request (using the from-tag), the other is a generic "teardown" command using the call ID.
Cheers
On 2018-09-04 07:52, Daniel-Constantin Mierla wrote: > > Hello, > > what do you get from rtpengine on rtp timeout? An RPC call back > or an http request? > > Cheers, > Daniel > > > On 04.09.18 12:48, Igor Olhovskiy wrote: >> Hi all! >> >> Is there any way to end dialog in Kamailio on RTP Timeout event >> on RTPEngine? >> >> Or only look at logs/redis database with external tool? >> >> Regards, Igor >> >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ > www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda > Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ > Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ > > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/
Kamailio (SER) - Users Mailing List sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/
Kamailio (SER) - Users Mailing List sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/
Hello,
is the call looped via rtpengine twice? Like
UA1 ---- K+RTPENGINE ---- SIP Server ----- K+RTPENGINE ---- UA2
Cheers, Daniel
On 22.01.20 08:21, Miteshkumar Thakkar wrote:
Hi,
Any thoughts on this?
Mitesh
On 26-Dec-2019, at 1:36 PM, Miteshkumar Thakkar <mitesh.thakkar@plivo.com mailto:mitesh.thakkar@plivo.com> wrote:
This is really helpful development. I am facing one issue, when I use this. RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams. Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment. How can I avoid this? Any help is appreciated. Thank you Mitesh
That's great, thank you! Cheers, Daniel On 06.09.18 11:15, Richard Fuchs wrote: >/This is now supported as per / >/https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e6701822070a72 / > >/Cheers / > >/On 2018-09-05 05:39, Daniel-Constantin Mierla wrote: / >> >>/There is the dlg.terminate_dlg rpc command that requires callid, / >>/from-tag and to-tag as parameters: / >> >>/ * / >>/https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_dlg / >> >>/So it expects something like: / >> >>/<?xml version="1.0" encoding="UTF-8"?> / >>/<methodCall> / >>/<methodName>dlg.terminate_dlg</methodName> / >>/<params> / >>/<param><value><string>_CALLID_VALUE__</string></value></param> / >>/<param><value><string>_FROM_TAG_VALUE__</string></value></param> / >>/<param><value><string>_TO_TAG_VALUE__</string></value></param> / >>/</params> / >>/</methodCall> / >> >>/I planned to make the from-tag and to-tag optional for quite some / >>/time, but didn't get the time for it yet. / >> >>/Cheers, / >>/Daniel / >> >>/On 05.09.18 08:52, Richard Fuchs wrote: / >>>/Yup that's exactly right. / >>> >>>/It would be fairly simple to implement an additional XMLRPC format / >>>/if there's a particular one that's more friendly towards Kamailio. / >>> >>>/Cheers / >>> >>>/On 2018-09-05 02:42, Daniel-Constantin Mierla wrote: / >>>> >>>>/Looking quickly at the readme of rtpengine application and digging / >>>>/a bit with google, it is something like rtpengine has to be started / >>>>/with / >>>> >>>>/-b http(s)://myrpcserver.ip/path -x 1 / >>>> >>>>/and then the xmlrpc request is going to be sent to that url, having / >>>>/a format like: / >>>> >>>>/<?xml version="1.0" encoding="UTF-8"?> / >>>>/<methodCall> / >>>>/<methodName>teardown</methodName> / >>>>/<params> / >>>>/<param><value><string>_CALLID_VALUE__</string></value></param> / >>>>/</params> / >>>>/</methodCall> / >>>> >>>>/Is it right? If yes, then I can try to make a sample config that / >>>>/could handle it using xmlops, xhttp and jsonrpcs modules. / >>>> >>>>/Cheers, / >>>>/Daniel / >>>> >>>> >>>>/On 05.09.18 08:24, Richard Fuchs wrote: / >>>>>/It does an XMLRPC callback. Currently there's two formats for it, / >>>>>/one is a sems sbc teardown request (using the from-tag), the other / >>>>>/is a generic "teardown" command using the call ID. / >>>>> >>>>>/Cheers / >>>>> >>>>>/On 2018-09-04 07:52, Daniel-Constantin Mierla wrote: / >>>>>> >>>>>>/Hello, / >>>>>> >>>>>>/what do you get from rtpengine on rtp timeout? An RPC call back / >>>>>>/or an http request? / >>>>>> >>>>>>/Cheers, / >>>>>>/Daniel / >>>>>> >>>>>> >>>>>>/On 04.09.18 12:48, Igor Olhovskiy wrote: / >>>>>>>/Hi all! / >>>>>>> >>>>>>>/Is there any way to end dialog in Kamailio on RTP Timeout event / >>>>>>>/on RTPEngine? / >>>>>>> >>>>>>>/Or only look at logs/redis database with external tool? / >>>>>>> >>>>>>>/Regards, Igor / >>>>>>> >>>>>>> >>>>>>>/_______________________________________________ / >>>>>>>/Kamailio (SER) - Users Mailing List / >>>>>>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >>>>>> >>>>>>/-- / >>>>>>/Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> / >>>>>>/www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> / >>>>>>/Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> / >>>>>>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/> / >>>>>> >>>>>> >>>>>>/_______________________________________________ / >>>>>>/Kamailio (SER) - Users Mailing List / >>>>>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >>>>> >>>>> >>>>>/_______________________________________________ / >>>>>/Kamailio (SER) - Users Mailing List / >>>>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >>>> >>>>/-- / >>>>/Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> / >>>>/www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> / >>>>/Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> / >>>>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/> / >>> >>> >>>/_______________________________________________ / >>>/Kamailio (SER) - Users Mailing List / >>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >>/-- / >>/Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> / >>/www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> / >>/Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> / >>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/> / > > >/_______________________________________________ / >/Kamailio (SER) - Users Mailing List / >/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / -- Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/>
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
No, that is not the case. It is visiting K+RTPENGINE only once.
Mitesh
On 22-Jan-2020, at 1:00 PM, Daniel-Constantin Mierla miconda@gmail.com wrote:
Hello,
is the call looped via rtpengine twice? Like
UA1 ---- K+RTPENGINE ---- SIP Server ----- K+RTPENGINE ---- UA2
Cheers, Daniel
On 22.01.20 08:21, Miteshkumar Thakkar wrote:
Hi,
Any thoughts on this?
Mitesh
On 26-Dec-2019, at 1:36 PM, Miteshkumar Thakkar <mitesh.thakkar@plivo.com mailto:mitesh.thakkar@plivo.com> wrote:
This is really helpful development. I am facing one issue, when I use this. RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams. Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment. How can I avoid this? Any help is appreciated. Thank you Mitesh That's great, thank you! Cheers, Daniel On 06.09.18 11:15, Richard Fuchs wrote:
This is now supported as per https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e67018... https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e6701822070a72
Cheers
On 2018-09-05 05:39, Daniel-Constantin Mierla wrote:
There is the dlg.terminate_dlg rpc command that requires callid, from-tag and to-tag as parameters:
https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_... https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_dlg
So it expects something like:
<?xml version="1.0" encoding="UTF-8"?>
<methodCall> <methodName>dlg.terminate_dlg</methodName> <params> <param><value><string>_CALLID_VALUE__</string></value></param> <param><value><string>_FROM_TAG_VALUE__</string></value></param> <param><value><string>_TO_TAG_VALUE__</string></value></param> </params> </methodCall>
I planned to make the from-tag and to-tag optional for quite some time, but didn't get the time for it yet.
Cheers, Daniel
On 05.09.18 08:52, Richard Fuchs wrote:
Yup that's exactly right.
It would be fairly simple to implement an additional XMLRPC format if there's a particular one that's more friendly towards Kamailio.
Cheers
On 2018-09-05 02:42, Daniel-Constantin Mierla wrote: > > Looking quickly at the readme of rtpengine application and digging > a bit with google, it is something like rtpengine has to be started > with > > -b http(s)://myrpcserver.ip/path -x 1 > > and then the xmlrpc request is going to be sent to that url, having > a format like: > > <?xml version="1.0" encoding="UTF-8"?> > <methodCall> > <methodName>teardown</methodName> > <params> > <param><value><string>_CALLID_VALUE__</string></value></param> > </params> > </methodCall> > > Is it right? If yes, then I can try to make a sample config that > could handle it using xmlops, xhttp and jsonrpcs modules. > > Cheers, > Daniel > > > On 05.09.18 08:24, Richard Fuchs wrote: >> It does an XMLRPC callback. Currently there's two formats for it, >> one is a sems sbc teardown request (using the from-tag), the other >> is a generic "teardown" command using the call ID. >> >> Cheers >> >> On 2018-09-04 07:52, Daniel-Constantin Mierla wrote: >>> >>> Hello, >>> >>> what do you get from rtpengine on rtp timeout? An RPC call back >>> or an http request? >>> >>> Cheers, >>> Daniel >>> >>> >>> On 04.09.18 12:48, Igor Olhovskiy wrote: >>>> Hi all! >>>> >>>> Is there any way to end dialog in Kamailio on RTP Timeout event >>>> on RTPEngine? >>>> >>>> Or only look at logs/redis database with external tool? >>>> >>>> Regards, Igor >>>> >>>> >>>> _______________________________________________ >>>> Kamailio (SER) - Users Mailing List >>>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>> -- >>> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ >>> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda >>> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ >>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ >>> >>> >>> _______________________________________________ >>> Kamailio (SER) - Users Mailing List >>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ > www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda > Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ > Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/
Kamailio (SER) - Users Mailing List sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/
Kamailio (SER) - Users Mailing List sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/
Have you run rtpengine in debug mode to see if it gives some hints why is retrying the same command?
Is it happening for every call and coming over the same connection?
I do not know if this is by design, but if there is something to be tune, I think the best place is inside RTPEngine, geting the response that dialog is not found seems the right one from my point of view, given that the rpc command can be used by other apps.
Cheers, Daniel
On 22.01.20 08:34, Miteshkumar Thakkar wrote:
No, that is not the case. It is visiting K+RTPENGINE only once.
Mitesh
On 22-Jan-2020, at 1:00 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Hello,
is the call looped via rtpengine twice? Like
UA1 ---- K+RTPENGINE ---- SIP Server ----- K+RTPENGINE ---- UA2
Cheers, Daniel
On 22.01.20 08:21, Miteshkumar Thakkar wrote:
Hi,
Any thoughts on this?
Mitesh
On 26-Dec-2019, at 1:36 PM, Miteshkumar Thakkar <mitesh.thakkar@plivo.com mailto:mitesh.thakkar@plivo.com> wrote:
This is really helpful development. I am facing one issue, when I use this. RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams. Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment. How can I avoid this? Any help is appreciated. Thank you Mitesh
That's great, thank you! Cheers, Daniel On 06.09.18 11:15, Richard Fuchs wrote: >/This is now supported as per / >/https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e6701822070a72 / > >/Cheers / > >/On 2018-09-05 05:39, Daniel-Constantin Mierla wrote: / >> >>/There is the dlg.terminate_dlg rpc command that requires callid, / >>/from-tag and to-tag as parameters: / >> >>/ * / >>/https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_dlg / >> >>/So it expects something like: / >> >>/<?xml version="1.0" encoding="UTF-8"?> / >>/<methodCall> / >>/<methodName>dlg.terminate_dlg</methodName> / >>/<params> / >>/<param><value><string>_CALLID_VALUE__</string></value></param> / >>/<param><value><string>_FROM_TAG_VALUE__</string></value></param> / >>/<param><value><string>_TO_TAG_VALUE__</string></value></param> / >>/</params> / >>/</methodCall> / >> >>/I planned to make the from-tag and to-tag optional for quite some / >>/time, but didn't get the time for it yet. / >> >>/Cheers, / >>/Daniel / >> >>/On 05.09.18 08:52, Richard Fuchs wrote: / >>>/Yup that's exactly right. / >>> >>>/It would be fairly simple to implement an additional XMLRPC format / >>>/if there's a particular one that's more friendly towards Kamailio. / >>> >>>/Cheers / >>> >>>/On 2018-09-05 02:42, Daniel-Constantin Mierla wrote: / >>>> >>>>/Looking quickly at the readme of rtpengine application and digging / >>>>/a bit with google, it is something like rtpengine has to be started / >>>>/with / >>>> >>>>/-b http(s)://myrpcserver.ip/path -x 1 / >>>> >>>>/and then the xmlrpc request is going to be sent to that url, having / >>>>/a format like: / >>>> >>>>/<?xml version="1.0" encoding="UTF-8"?> / >>>>/<methodCall> / >>>>/<methodName>teardown</methodName> / >>>>/<params> / >>>>/<param><value><string>_CALLID_VALUE__</string></value></param> / >>>>/</params> / >>>>/</methodCall> / >>>> >>>>/Is it right? If yes, then I can try to make a sample config that / >>>>/could handle it using xmlops, xhttp and jsonrpcs modules. / >>>> >>>>/Cheers, / >>>>/Daniel / >>>> >>>> >>>>/On 05.09.18 08:24, Richard Fuchs wrote: / >>>>>/It does an XMLRPC callback. Currently there's two formats for it, / >>>>>/one is a sems sbc teardown request (using the from-tag), the other / >>>>>/is a generic "teardown" command using the call ID. / >>>>> >>>>>/Cheers / >>>>> >>>>>/On 2018-09-04 07:52, Daniel-Constantin Mierla wrote: / >>>>>> >>>>>>/Hello, / >>>>>> >>>>>>/what do you get from rtpengine on rtp timeout? An RPC call back / >>>>>>/or an http request? / >>>>>> >>>>>>/Cheers, / >>>>>>/Daniel / >>>>>> >>>>>> >>>>>>/On 04.09.18 12:48, Igor Olhovskiy wrote: / >>>>>>>/Hi all! / >>>>>>> >>>>>>>/Is there any way to end dialog in Kamailio on RTP Timeout event / >>>>>>>/on RTPEngine? / >>>>>>> >>>>>>>/Or only look at logs/redis database with external tool? / >>>>>>> >>>>>>>/Regards, Igor / >>>>>>> >>>>>>> >>>>>>>/_______________________________________________ / >>>>>>>/Kamailio (SER) - Users Mailing List / >>>>>>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >>>>>> >>>>>>/-- / >>>>>>/Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> / >>>>>>/www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> / >>>>>>/Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> / >>>>>>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/> / >>>>>> >>>>>> >>>>>>/_______________________________________________ / >>>>>>/Kamailio (SER) - Users Mailing List / >>>>>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >>>>> >>>>> >>>>>/_______________________________________________ / >>>>>/Kamailio (SER) - Users Mailing List / >>>>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >>>> >>>>/-- / >>>>/Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> / >>>>/www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> / >>>>/Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> / >>>>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/> / >>> >>> >>>/_______________________________________________ / >>>/Kamailio (SER) - Users Mailing List / >>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >>/-- / >>/Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> / >>/www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> / >>/Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> / >>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/> / > > >/_______________________________________________ / >/Kamailio (SER) - Users Mailing List / >/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / -- Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/>
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
On 22-Jan-2020, at 1:57 PM, Daniel-Constantin Mierla miconda@gmail.com wrote:
Have you run rtpengine in debug mode to see if it gives some hints why is retrying the same command?
Is it happening for every call and coming over the same connection?
I do not know if this is by design, but if there is something to be tune, I think the best place is inside RTPEngine, geting the response that dialog is not found seems the right one from my point of view, given that the rpc command can be used by other apps.
Agree. I have posted the same to RTPEngine. They have taken care and created a patch for that. Thank you very much for help.
A small concern: When Kamailio receives an event dlg.terminate_dlg from RTPEngine, I am calling KSR.xmlrpc.dispatch_rpc() to process the event. Functionality is working fine. It is ending the dialog but with that it is generating below errors.
27(179) ERROR: pv [pv_core.c:704]: pv_get_callid(): cannot parse Call-Id header 27(179) ERROR: dialog [dlg_handlers.c:679]: pre_match_parse(): bad request or missing CALLID/TO hdr :-/
Should I worry about it?
Cheers, Daniel
On 22.01.20 08:34, Miteshkumar Thakkar wrote:
No, that is not the case. It is visiting K+RTPENGINE only once.
Mitesh
On 22-Jan-2020, at 1:00 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Hello,
is the call looped via rtpengine twice? Like
UA1 ---- K+RTPENGINE ---- SIP Server ----- K+RTPENGINE ---- UA2
Cheers, Daniel
On 22.01.20 08:21, Miteshkumar Thakkar wrote:
Hi,
Any thoughts on this?
Mitesh
On 26-Dec-2019, at 1:36 PM, Miteshkumar Thakkar <mitesh.thakkar@plivo.com mailto:mitesh.thakkar@plivo.com> wrote:
This is really helpful development. I am facing one issue, when I use this. RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams. Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment. How can I avoid this? Any help is appreciated. Thank you Mitesh That's great, thank you! Cheers, Daniel On 06.09.18 11:15, Richard Fuchs wrote:
This is now supported as per https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e67018... https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e6701822070a72
Cheers
On 2018-09-05 05:39, Daniel-Constantin Mierla wrote: > > There is the dlg.terminate_dlg rpc command that requires callid, > from-tag and to-tag as parameters: > > * > https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_... https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_dlg > > So it expects something like: > > <?xml version="1.0" encoding="UTF-8"?> > <methodCall> > <methodName>dlg.terminate_dlg</methodName> > <params> > <param><value><string>_CALLID_VALUE__</string></value></param> > <param><value><string>_FROM_TAG_VALUE__</string></value></param> > <param><value><string>_TO_TAG_VALUE__</string></value></param> > </params> > </methodCall> > > I planned to make the from-tag and to-tag optional for quite some > time, but didn't get the time for it yet. > > Cheers, > Daniel > > On 05.09.18 08:52, Richard Fuchs wrote: >> Yup that's exactly right. >> >> It would be fairly simple to implement an additional XMLRPC format >> if there's a particular one that's more friendly towards Kamailio. >> >> Cheers >> >> On 2018-09-05 02:42, Daniel-Constantin Mierla wrote: >>> >>> Looking quickly at the readme of rtpengine application and digging >>> a bit with google, it is something like rtpengine has to be started >>> with >>> >>> -b http(s)://myrpcserver.ip/path -x 1 >>> >>> and then the xmlrpc request is going to be sent to that url, having >>> a format like: >>> >>> <?xml version="1.0" encoding="UTF-8"?> >>> <methodCall> >>> <methodName>teardown</methodName> >>> <params> >>> <param><value><string>_CALLID_VALUE__</string></value></param> >>> </params> >>> </methodCall> >>> >>> Is it right? If yes, then I can try to make a sample config that >>> could handle it using xmlops, xhttp and jsonrpcs modules. >>> >>> Cheers, >>> Daniel >>> >>> >>> On 05.09.18 08:24, Richard Fuchs wrote: >>>> It does an XMLRPC callback. Currently there's two formats for it, >>>> one is a sems sbc teardown request (using the from-tag), the other >>>> is a generic "teardown" command using the call ID. >>>> >>>> Cheers >>>> >>>> On 2018-09-04 07:52, Daniel-Constantin Mierla wrote: >>>>> >>>>> Hello, >>>>> >>>>> what do you get from rtpengine on rtp timeout? An RPC call back >>>>> or an http request? >>>>> >>>>> Cheers, >>>>> Daniel >>>>> >>>>> >>>>> On 04.09.18 12:48, Igor Olhovskiy wrote: >>>>>> Hi all! >>>>>> >>>>>> Is there any way to end dialog in Kamailio on RTP Timeout event >>>>>> on RTPEngine? >>>>>> >>>>>> Or only look at logs/redis database with external tool? >>>>>> >>>>>> Regards, Igor >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Kamailio (SER) - Users Mailing List >>>>>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>> >>>>> -- >>>>> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ >>>>> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda >>>>> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ >>>>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ >>>>> >>>>> >>>>> _______________________________________________ >>>>> Kamailio (SER) - Users Mailing List >>>>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>> >>>> >>>> _______________________________________________ >>>> Kamailio (SER) - Users Mailing List >>>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>> -- >>> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ >>> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda >>> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ >>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ >> >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ > www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda > Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ > Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/
Kamailio (SER) - Users Mailing List sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/
On 13.02.20 10:43, Miteshkumar Thakkar wrote:
On 22-Jan-2020, at 1:57 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Have you run rtpengine in debug mode to see if it gives some hints why is retrying the same command?
Is it happening for every call and coming over the same connection?
I do not know if this is by design, but if there is something to be tune, I think the best place is inside RTPEngine, geting the response that dialog is not found seems the right one from my point of view, given that the rpc command can be used by other apps.
Agree. I have posted the same to RTPEngine. They have taken care and created a patch for that. Thank you very much for help.
OK, good to know.
A small concern: When Kamailio receives an event dlg.terminate_dlg from RTPEngine, I am calling KSR.xmlrpc.dispatch_rpc() to process the event. Functionality is working fine. It is ending the dialog but with that it is generating below errors.
27(179) ERROR: pv [pv_core.c:704]: pv_get_callid(): cannot parse Call-Id header 27(179) ERROR: dialog [dlg_handlers.c:679]: pre_match_parse(): bad request or missing CALLID/TO hdr :-/
Should I worry about it?
Do you access $ci and use other dialog module functions when processing the xmlrpc command (inside the xmlrpc event route callback function)?
Cheers, Daniel
Cheers, Daniel
On 22.01.20 08:34, Miteshkumar Thakkar wrote:
No, that is not the case. It is visiting K+RTPENGINE only once.
Mitesh
On 22-Jan-2020, at 1:00 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Hello,
is the call looped via rtpengine twice? Like
UA1 ---- K+RTPENGINE ---- SIP Server ----- K+RTPENGINE ---- UA2
Cheers, Daniel
On 22.01.20 08:21, Miteshkumar Thakkar wrote:
Hi,
Any thoughts on this?
Mitesh
On 26-Dec-2019, at 1:36 PM, Miteshkumar Thakkar <mitesh.thakkar@plivo.com mailto:mitesh.thakkar@plivo.com> wrote:
This is really helpful development. I am facing one issue, when I use this. RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams. Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment. How can I avoid this? Any help is appreciated. Thank you Mitesh
That's great, thank you! Cheers, Daniel On 06.09.18 11:15, Richard Fuchs wrote: >/This is now supported as per / >/https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e6701822070a72 / > >/Cheers / > >/On 2018-09-05 05:39, Daniel-Constantin Mierla wrote: / >> >>/There is the dlg.terminate_dlg rpc command that requires callid, / >>/from-tag and to-tag as parameters: / >> >>/ * / >>/https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_dlg / >> >>/So it expects something like: / >> >>/<?xml version="1.0" encoding="UTF-8"?> / >>/<methodCall> / >>/<methodName>dlg.terminate_dlg</methodName> / >>/<params> / >>/<param><value><string>_CALLID_VALUE__</string></value></param> / >>/<param><value><string>_FROM_TAG_VALUE__</string></value></param> / >>/<param><value><string>_TO_TAG_VALUE__</string></value></param> / >>/</params> / >>/</methodCall> / >> >>/I planned to make the from-tag and to-tag optional for quite some / >>/time, but didn't get the time for it yet. / >> >>/Cheers, / >>/Daniel / >> >>/On 05.09.18 08:52, Richard Fuchs wrote: / >>>/Yup that's exactly right. / >>> >>>/It would be fairly simple to implement an additional XMLRPC format / >>>/if there's a particular one that's more friendly towards Kamailio. / >>> >>>/Cheers / >>> >>>/On 2018-09-05 02:42, Daniel-Constantin Mierla wrote: / >>>> >>>>/Looking quickly at the readme of rtpengine application and digging / >>>>/a bit with google, it is something like rtpengine has to be started / >>>>/with / >>>> >>>>/-b http(s)://myrpcserver.ip/path -x 1 / >>>> >>>>/and then the xmlrpc request is going to be sent to that url, having / >>>>/a format like: / >>>> >>>>/<?xml version="1.0" encoding="UTF-8"?> / >>>>/<methodCall> / >>>>/<methodName>teardown</methodName> / >>>>/<params> / >>>>/<param><value><string>_CALLID_VALUE__</string></value></param> / >>>>/</params> / >>>>/</methodCall> / >>>> >>>>/Is it right? If yes, then I can try to make a sample config that / >>>>/could handle it using xmlops, xhttp and jsonrpcs modules. / >>>> >>>>/Cheers, / >>>>/Daniel / >>>> >>>> >>>>/On 05.09.18 08:24, Richard Fuchs wrote: / >>>>>/It does an XMLRPC callback. Currently there's two formats for it, / >>>>>/one is a sems sbc teardown request (using the from-tag), the other / >>>>>/is a generic "teardown" command using the call ID. / >>>>> >>>>>/Cheers / >>>>> >>>>>/On 2018-09-04 07:52, Daniel-Constantin Mierla wrote: / >>>>>> >>>>>>/Hello, / >>>>>> >>>>>>/what do you get from rtpengine on rtp timeout? An RPC call back / >>>>>>/or an http request? / >>>>>> >>>>>>/Cheers, / >>>>>>/Daniel / >>>>>> >>>>>> >>>>>>/On 04.09.18 12:48, Igor Olhovskiy wrote: / >>>>>>>/Hi all! / >>>>>>> >>>>>>>/Is there any way to end dialog in Kamailio on RTP Timeout event / >>>>>>>/on RTPEngine? / >>>>>>> >>>>>>>/Or only look at logs/redis database with external tool? / >>>>>>> >>>>>>>/Regards, Igor / >>>>>>> >>>>>>> >>>>>>>/_______________________________________________ / >>>>>>>/Kamailio (SER) - Users Mailing List / >>>>>>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >>>>>> >>>>>>/-- / >>>>>>/Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> / >>>>>>/www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> / >>>>>>/Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> / >>>>>>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/> / >>>>>> >>>>>> >>>>>>/_______________________________________________ / >>>>>>/Kamailio (SER) - Users Mailing List / >>>>>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >>>>> >>>>> >>>>>/_______________________________________________ / >>>>>/Kamailio (SER) - Users Mailing List / >>>>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >>>> >>>>/-- / >>>>/Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> / >>>>/www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> / >>>>/Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> / >>>>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/> / >>> >>> >>>/_______________________________________________ / >>>/Kamailio (SER) - Users Mailing List / >>>/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >>/-- / >>/Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> / >>/www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> / >>/Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> / >>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/> / > > >/_______________________________________________ / >/Kamailio (SER) - Users Mailing List / >/sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> / >/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / -- Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com/> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com/>
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
On 13-Feb-2020, at 3:31 PM, Daniel-Constantin Mierla miconda@gmail.com wrote:
On 13.02.20 10:43, Miteshkumar Thakkar wrote:
On 22-Jan-2020, at 1:57 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Have you run rtpengine in debug mode to see if it gives some hints why is retrying the same command?
Is it happening for every call and coming over the same connection?
I do not know if this is by design, but if there is something to be tune, I think the best place is inside RTPEngine, geting the response that dialog is not found seems the right one from my point of view, given that the rpc command can be used by other apps.
Agree. I have posted the same to RTPEngine. They have taken care and created a patch for that. Thank you very much for help.
OK, good to know.
A small concern: When Kamailio receives an event dlg.terminate_dlg from RTPEngine, I am calling KSR.xmlrpc.dispatch_rpc() to process the event. Functionality is working fine. It is ending the dialog but with that it is generating below errors.
27(179) ERROR: pv [pv_core.c:704]: pv_get_callid(): cannot parse Call-Id header 27(179) ERROR: dialog [dlg_handlers.c:679]: pre_match_parse(): bad request or missing CALLID/TO hdr :-/
Should I worry about it?
Do you access $ci and use other dialog module functions when processing the xmlrpc command (inside the xmlrpc event route callback function)?
Not really. Here is what I am doing:
local rpc_method = KSR.pv.get("$rm") or "" if rpc_method == "POST" or rpc_method == "GET" then if not (KSR.xmlrpc.dispatch_rpc()) then logger.log("err", "error") end end
-Mitesh
Cheers, Daniel
Cheers, Daniel
On 22.01.20 08:34, Miteshkumar Thakkar wrote:
No, that is not the case. It is visiting K+RTPENGINE only once.
Mitesh
On 22-Jan-2020, at 1:00 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Hello,
is the call looped via rtpengine twice? Like
UA1 ---- K+RTPENGINE ---- SIP Server ----- K+RTPENGINE ---- UA2
Cheers, Daniel
On 22.01.20 08:21, Miteshkumar Thakkar wrote:
Hi,
Any thoughts on this?
Mitesh
> On 26-Dec-2019, at 1:36 PM, Miteshkumar Thakkar <mitesh.thakkar@plivo.com mailto:mitesh.thakkar@plivo.com> wrote: > > This is really helpful development. > I am facing one issue, when I use this. > RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams. > Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment. > How can I avoid this? Any help is appreciated. > Thank you > Mitesh > That's great, thank you! > Cheers, > Daniel > On 06.09.18 11:15, Richard Fuchs wrote: > > This is now supported as per > > https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e67018... https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e6701822070a72 > > > > Cheers > > > > On 2018-09-05 05:39, Daniel-Constantin Mierla wrote: > >> > >> There is the dlg.terminate_dlg rpc command that requires callid, > >> from-tag and to-tag as parameters: > >> > >> * > >> https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_... https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_dlg > >> > >> So it expects something like: > >> > >> <?xml version="1.0" encoding="UTF-8"?> > >> <methodCall> > >> <methodName>dlg.terminate_dlg</methodName> > >> <params> > >> <param><value><string>_CALLID_VALUE__</string></value></param> > >> <param><value><string>_FROM_TAG_VALUE__</string></value></param> > >> <param><value><string>_TO_TAG_VALUE__</string></value></param> > >> </params> > >> </methodCall> > >> > >> I planned to make the from-tag and to-tag optional for quite some > >> time, but didn't get the time for it yet. > >> > >> Cheers, > >> Daniel > >> > >> On 05.09.18 08:52, Richard Fuchs wrote: > >>> Yup that's exactly right. > >>> > >>> It would be fairly simple to implement an additional XMLRPC format > >>> if there's a particular one that's more friendly towards Kamailio. > >>> > >>> Cheers > >>> > >>> On 2018-09-05 02:42, Daniel-Constantin Mierla wrote: > >>>> > >>>> Looking quickly at the readme of rtpengine application and digging > >>>> a bit with google, it is something like rtpengine has to be started > >>>> with > >>>> > >>>> -b http(s)://myrpcserver.ip/path -x 1 > >>>> > >>>> and then the xmlrpc request is going to be sent to that url, having > >>>> a format like: > >>>> > >>>> <?xml version="1.0" encoding="UTF-8"?> > >>>> <methodCall> > >>>> <methodName>teardown</methodName> > >>>> <params> > >>>> <param><value><string>_CALLID_VALUE__</string></value></param> > >>>> </params> > >>>> </methodCall> > >>>> > >>>> Is it right? If yes, then I can try to make a sample config that > >>>> could handle it using xmlops, xhttp and jsonrpcs modules. > >>>> > >>>> Cheers, > >>>> Daniel > >>>> > >>>> > >>>> On 05.09.18 08:24, Richard Fuchs wrote: > >>>>> It does an XMLRPC callback. Currently there's two formats for it, > >>>>> one is a sems sbc teardown request (using the from-tag), the other > >>>>> is a generic "teardown" command using the call ID. > >>>>> > >>>>> Cheers > >>>>> > >>>>> On 2018-09-04 07:52, Daniel-Constantin Mierla wrote: > >>>>>> > >>>>>> Hello, > >>>>>> > >>>>>> what do you get from rtpengine on rtp timeout? An RPC call back > >>>>>> or an http request? > >>>>>> > >>>>>> Cheers, > >>>>>> Daniel > >>>>>> > >>>>>> > >>>>>> On 04.09.18 12:48, Igor Olhovskiy wrote: > >>>>>>> Hi all! > >>>>>>> > >>>>>>> Is there any way to end dialog in Kamailio on RTP Timeout event > >>>>>>> on RTPEngine? > >>>>>>> > >>>>>>> Or only look at logs/redis database with external tool? > >>>>>>> > >>>>>>> Regards, Igor > >>>>>>> > >>>>>>> > >>>>>>> _______________________________________________ > >>>>>>> Kamailio (SER) - Users Mailing List > >>>>>>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >>>>>> > >>>>>> -- > >>>>>> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ > >>>>>> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda > >>>>>> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ > >>>>>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Kamailio (SER) - Users Mailing List > >>>>>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Kamailio (SER) - Users Mailing List > >>>>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >>>> > >>>> -- > >>>> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ > >>>> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda > >>>> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ > >>>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ > >>> > >>> > >>> _______________________________________________ > >>> Kamailio (SER) - Users Mailing List > >>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >> > >> -- > >> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ > >> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda > >> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ > >> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ > > > > > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- > Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ > www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda > Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ > Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/
On 13.02.20 11:25, Miteshkumar Thakkar wrote:
On 13-Feb-2020, at 3:31 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
On 13.02.20 10:43, Miteshkumar Thakkar wrote:
On 22-Jan-2020, at 1:57 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Have you run rtpengine in debug mode to see if it gives some hints why is retrying the same command?
Is it happening for every call and coming over the same connection?
I do not know if this is by design, but if there is something to be tune, I think the best place is inside RTPEngine, geting the response that dialog is not found seems the right one from my point of view, given that the rpc command can be used by other apps.
Agree. I have posted the same to RTPEngine. They have taken care and created a patch for that. Thank you very much for help.
OK, good to know.
A small concern: When Kamailio receives an event dlg.terminate_dlg from RTPEngine, I am calling KSR.xmlrpc.dispatch_rpc() to process the event. Functionality is working fine. It is ending the dialog but with that it is generating below errors.
27(179) ERROR: pv [pv_core.c:704]: pv_get_callid(): cannot parse Call-Id header 27(179) ERROR: dialog [dlg_handlers.c:679]: pre_match_parse(): bad request or missing CALLID/TO hdr :-/
Should I worry about it?
Do you access $ci and use other dialog module functions when processing the xmlrpc command (inside the xmlrpc event route callback function)?
Not really. Here is what I am doing:
*local *rpc_method = /KSR.pv.get/(*"$rm"*) *or **""* * **if *rpc_method == *"POST" **or *rpc_method == *"GET" **then* * if not *(KSR.xmlrpc.dispatch_rpc()) *then* * **/logger/*.log(*"err"*, *"error"*) *end* * end*
Where is this piece of code executed?
Daniel
-Mitesh
Cheers, Daniel
Cheers, Daniel
On 22.01.20 08:34, Miteshkumar Thakkar wrote:
No, that is not the case. It is visiting K+RTPENGINE only once.
Mitesh
On 22-Jan-2020, at 1:00 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Hello,
is the call looped via rtpengine twice? Like
UA1 ---- K+RTPENGINE ---- SIP Server ----- K+RTPENGINE ---- UA2
Cheers, Daniel
On 22.01.20 08:21, Miteshkumar Thakkar wrote: > Hi, > > Any thoughts on this? > > Mitesh > >> On 26-Dec-2019, at 1:36 PM, Miteshkumar Thakkar >> <mitesh.thakkar@plivo.com mailto:mitesh.thakkar@plivo.com> wrote: >> >> This is really helpful development. >> I am facing one issue, when I use this. >> RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams. >> Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment. >> How can I avoid this? Any help is appreciated. >> Thank you >> Mitesh >> >> That's great, thank you! >> >> Cheers, >> >> Daniel >> >> On 06.09.18 11:15, Richard Fuchs wrote: >> >> >/This is now supported as per / >> >> >/https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e67018... >> / >> >> > >> >> >/Cheers / >> >> > >> >> >/On 2018-09-05 05:39, Daniel-Constantin Mierla wrote: / >> >> >> >> >> >>/There is the dlg.terminate_dlg rpc command that requires >> callid, / >> >> >>/from-tag and to-tag as parameters: / >> >> >> >> >> >>/ * / >> >> >>/https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_... >> / >> >> >> >> >> >>/So it expects something like: / >> >> >> >> >> >>/<?xml version="1.0" encoding="UTF-8"?> / >> >> >>/<methodCall> / >> >> >>/<methodName>dlg.terminate_dlg</methodName> / >> >> >>/<params> / >> >> >>/<param><value><string>_CALLID_VALUE__</string></value></param> >> / >> >> >>/<param><value><string>_FROM_TAG_VALUE__</string></value></param> >> / >> >> >>/<param><value><string>_TO_TAG_VALUE__</string></value></param> >> / >> >> >>/</params> / >> >> >>/</methodCall> / >> >> >> >> >> >>/I planned to make the from-tag and to-tag optional for >> quite some / >> >> >>/time, but didn't get the time for it yet. / >> >> >> >> >> >>/Cheers, / >> >> >>/Daniel / >> >> >> >> >> >>/On 05.09.18 08:52, Richard Fuchs wrote: / >> >> >>>/Yup that's exactly right. / >> >> >>> >> >> >>>/It would be fairly simple to implement an additional >> XMLRPC format / >> >> >>>/if there's a particular one that's more friendly towards >> Kamailio. / >> >> >>> >> >> >>>/Cheers / >> >> >>> >> >> >>>/On 2018-09-05 02:42, Daniel-Constantin Mierla wrote: / >> >> >>>> >> >> >>>>/Looking quickly at the readme of rtpengine application and >> digging / >> >> >>>>/a bit with google, it is something like rtpengine has to >> be started / >> >> >>>>/with / >> >> >>>> >> >> >>>>/-b http(s)://myrpcserver.ip/path -x 1 / >> >> >>>> >> >> >>>>/and then the xmlrpc request is going to be sent to that >> url, having / >> >> >>>>/a format like: / >> >> >>>> >> >> >>>>/<?xml version="1.0" encoding="UTF-8"?> / >> >> >>>>/<methodCall> / >> >> >>>>/<methodName>teardown</methodName> / >> >> >>>>/<params> / >> >> >>>>/<param><value><string>_CALLID_VALUE__</string></value></param> >> / >> >> >>>>/</params> / >> >> >>>>/</methodCall> / >> >> >>>> >> >> >>>>/Is it right? If yes, then I can try to make a sample >> config that / >> >> >>>>/could handle it using xmlops, xhttp and jsonrpcs modules. / >> >> >>>> >> >> >>>>/Cheers, / >> >> >>>>/Daniel / >> >> >>>> >> >> >>>> >> >> >>>>/On 05.09.18 08:24, Richard Fuchs wrote: / >> >> >>>>>/It does an XMLRPC callback. Currently there's two formats >> for it, / >> >> >>>>>/one is a sems sbc teardown request (using the from-tag), >> the other / >> >> >>>>>/is a generic "teardown" command using the call ID. / >> >> >>>>> >> >> >>>>>/Cheers / >> >> >>>>> >> >> >>>>>/On 2018-09-04 07:52, Daniel-Constantin Mierla wrote: / >> >> >>>>>> >> >> >>>>>>/Hello, / >> >> >>>>>> >> >> >>>>>>/what do you get from rtpengine on rtp timeout? An RPC call >> back / >> >> >>>>>>/or an http request? / >> >> >>>>>> >> >> >>>>>>/Cheers, / >> >> >>>>>>/Daniel / >> >> >>>>>> >> >> >>>>>> >> >> >>>>>>/On 04.09.18 12:48, Igor Olhovskiy wrote: / >> >> >>>>>>>/Hi all! / >> >> >>>>>>> >> >> >>>>>>>/Is there any way to end dialog in Kamailio on RTP Timeout >> event / >> >> >>>>>>>/on RTPEngine? / >> >> >>>>>>> >> >> >>>>>>>/Or only look at logs/redis database with external tool? / >> >> >>>>>>> >> >> >>>>>>>/Regards, Igor / >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>>/_______________________________________________ / >> >> >>>>>>>/Kamailio (SER) - Users Mailing List / >> >> >>>>>>>/sr-users at lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >> >>>>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >> >>>>>> >> >> >>>>>>/-- / >> >> >>>>>>/Daniel-Constantin Mierla -- www.asipto.com >> http://www.asipto.com/ / >> >> >>>>>>/www.twitter.com/miconda http://www.twitter.com/miconda >> -- www.linkedin.com/in/miconda >> http://www.linkedin.com/in/miconda / >> >> >>>>>>/Kamailio World Conference -- www.kamailioworld.com >> http://www.kamailioworld.com/ / >> >> >>>>>>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- >> www.asipto.com http://www.asipto.com/ / >> >> >>>>>> >> >> >>>>>> >> >> >>>>>>/_______________________________________________ / >> >> >>>>>>/Kamailio (SER) - Users Mailing List / >> >> >>>>>>/sr-users at lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >> >>>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >> >>>>> >> >> >>>>> >> >> >>>>>/_______________________________________________ / >> >> >>>>>/Kamailio (SER) - Users Mailing List / >> >> >>>>>/sr-users at lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >> >>>>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >> >>>> >> >> >>>>/-- / >> >> >>>>/Daniel-Constantin Mierla -- www.asipto.com >> http://www.asipto.com/ / >> >> >>>>/www.twitter.com/miconda http://www.twitter.com/miconda >> -- www.linkedin.com/in/miconda >> http://www.linkedin.com/in/miconda / >> >> >>>>/Kamailio World Conference -- www.kamailioworld.com >> http://www.kamailioworld.com/ / >> >> >>>>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- >> www.asipto.com http://www.asipto.com/ / >> >> >>> >> >> >>> >> >> >>>/_______________________________________________ / >> >> >>>/Kamailio (SER) - Users Mailing List / >> >> >>>/sr-users at lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >> >>>/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >> >> >> >> >>/-- / >> >> >>/Daniel-Constantin Mierla -- www.asipto.com >> http://www.asipto.com/ / >> >> >>/www.twitter.com/miconda http://www.twitter.com/miconda >> -- www.linkedin.com/in/miconda >> http://www.linkedin.com/in/miconda / >> >> >>/Kamailio World Conference -- www.kamailioworld.com >> http://www.kamailioworld.com/ / >> >> >>/Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- >> www.asipto.com http://www.asipto.com/ / >> >> > >> >> > >> >> >/_______________________________________________ / >> >> >/Kamailio (SER) - Users Mailing List / >> >> >/sr-users at lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >> >/https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users / >> >> -- >> >> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ >> >> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda >> >> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ >> >> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ >> > > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
On 13-Feb-2020, at 4:25 PM, Daniel-Constantin Mierla miconda@gmail.com wrote:
On 13.02.20 11:25, Miteshkumar Thakkar wrote:
On 13-Feb-2020, at 3:31 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
On 13.02.20 10:43, Miteshkumar Thakkar wrote:
On 22-Jan-2020, at 1:57 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Have you run rtpengine in debug mode to see if it gives some hints why is retrying the same command?
Is it happening for every call and coming over the same connection?
I do not know if this is by design, but if there is something to be tune, I think the best place is inside RTPEngine, geting the response that dialog is not found seems the right one from my point of view, given that the rpc command can be used by other apps.
Agree. I have posted the same to RTPEngine. They have taken care and created a patch for that. Thank you very much for help.
OK, good to know.
A small concern: When Kamailio receives an event dlg.terminate_dlg from RTPEngine, I am calling KSR.xmlrpc.dispatch_rpc() to process the event. Functionality is working fine. It is ending the dialog but with that it is generating below errors.
27(179) ERROR: pv [pv_core.c:704]: pv_get_callid(): cannot parse Call-Id header 27(179) ERROR: dialog [dlg_handlers.c:679]: pre_match_parse(): bad request or missing CALLID/TO hdr :-/
Should I worry about it?
Do you access $ci and use other dialog module functions when processing the xmlrpc command (inside the xmlrpc event route callback function)?
Not really. Here is what I am doing:
local rpc_method = KSR.pv.get("$rm") or "" if rpc_method == "POST" or rpc_method == "GET" then if not (KSR.xmlrpc.dispatch_rpc()) then logger.log("err", "error") end end
Where is this piece of code executed?
This is the only code in function ksr_xhttp_event(e), which is executed when the event from RTPEngine is coming.
-Mitesh
Daniel
-Mitesh
Cheers, Daniel
Cheers, Daniel
On 22.01.20 08:34, Miteshkumar Thakkar wrote:
No, that is not the case. It is visiting K+RTPENGINE only once.
Mitesh
> On 22-Jan-2020, at 1:00 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote: > > Hello, > > is the call looped via rtpengine twice? Like > > UA1 ---- K+RTPENGINE ---- SIP Server ----- K+RTPENGINE ---- UA2 > > Cheers, > Daniel > > On 22.01.20 08:21, Miteshkumar Thakkar wrote: >> Hi, >> >> Any thoughts on this? >> >> Mitesh >> >>> On 26-Dec-2019, at 1:36 PM, Miteshkumar Thakkar <mitesh.thakkar@plivo.com mailto:mitesh.thakkar@plivo.com> wrote: >>> >>> This is really helpful development. >>> I am facing one issue, when I use this. >>> RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams. >>> Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment. >>> How can I avoid this? Any help is appreciated. >>> Thank you >>> Mitesh >>> That's great, thank you! >>> Cheers, >>> Daniel >>> On 06.09.18 11:15, Richard Fuchs wrote: >>> > This is now supported as per >>> > https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e67018... https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e6701822070a72 >>> > >>> > Cheers >>> > >>> > On 2018-09-05 05:39, Daniel-Constantin Mierla wrote: >>> >> >>> >> There is the dlg.terminate_dlg rpc command that requires callid, >>> >> from-tag and to-tag as parameters: >>> >> >>> >> * >>> >> https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_... https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_dlg >>> >> >>> >> So it expects something like: >>> >> >>> >> <?xml version="1.0" encoding="UTF-8"?> >>> >> <methodCall> >>> >> <methodName>dlg.terminate_dlg</methodName> >>> >> <params> >>> >> <param><value><string>_CALLID_VALUE__</string></value></param> >>> >> <param><value><string>_FROM_TAG_VALUE__</string></value></param> >>> >> <param><value><string>_TO_TAG_VALUE__</string></value></param> >>> >> </params> >>> >> </methodCall> >>> >> >>> >> I planned to make the from-tag and to-tag optional for quite some >>> >> time, but didn't get the time for it yet. >>> >> >>> >> Cheers, >>> >> Daniel >>> >> >>> >> On 05.09.18 08:52, Richard Fuchs wrote: >>> >>> Yup that's exactly right. >>> >>> >>> >>> It would be fairly simple to implement an additional XMLRPC format >>> >>> if there's a particular one that's more friendly towards Kamailio. >>> >>> >>> >>> Cheers >>> >>> >>> >>> On 2018-09-05 02:42, Daniel-Constantin Mierla wrote: >>> >>>> >>> >>>> Looking quickly at the readme of rtpengine application and digging >>> >>>> a bit with google, it is something like rtpengine has to be started >>> >>>> with >>> >>>> >>> >>>> -b http(s)://myrpcserver.ip/path -x 1 >>> >>>> >>> >>>> and then the xmlrpc request is going to be sent to that url, having >>> >>>> a format like: >>> >>>> >>> >>>> <?xml version="1.0" encoding="UTF-8"?> >>> >>>> <methodCall> >>> >>>> <methodName>teardown</methodName> >>> >>>> <params> >>> >>>> <param><value><string>_CALLID_VALUE__</string></value></param> >>> >>>> </params> >>> >>>> </methodCall> >>> >>>> >>> >>>> Is it right? If yes, then I can try to make a sample config that >>> >>>> could handle it using xmlops, xhttp and jsonrpcs modules. >>> >>>> >>> >>>> Cheers, >>> >>>> Daniel >>> >>>> >>> >>>> >>> >>>> On 05.09.18 08:24, Richard Fuchs wrote: >>> >>>>> It does an XMLRPC callback. Currently there's two formats for it, >>> >>>>> one is a sems sbc teardown request (using the from-tag), the other >>> >>>>> is a generic "teardown" command using the call ID. >>> >>>>> >>> >>>>> Cheers >>> >>>>> >>> >>>>> On 2018-09-04 07:52, Daniel-Constantin Mierla wrote: >>> >>>>>> >>> >>>>>> Hello, >>> >>>>>> >>> >>>>>> what do you get from rtpengine on rtp timeout? An RPC call back >>> >>>>>> or an http request? >>> >>>>>> >>> >>>>>> Cheers, >>> >>>>>> Daniel >>> >>>>>> >>> >>>>>> >>> >>>>>> On 04.09.18 12:48, Igor Olhovskiy wrote: >>> >>>>>>> Hi all! >>> >>>>>>> >>> >>>>>>> Is there any way to end dialog in Kamailio on RTP Timeout event >>> >>>>>>> on RTPEngine? >>> >>>>>>> >>> >>>>>>> Or only look at logs/redis database with external tool? >>> >>>>>>> >>> >>>>>>> Regards, Igor >>> >>>>>>> >>> >>>>>>> >>> >>>>>>> _______________________________________________ >>> >>>>>>> Kamailio (SER) - Users Mailing List >>> >>>>>>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>>>>> >>> >>>>>> -- >>> >>>>>> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ >>> >>>>>> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda >>> >>>>>> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ >>> >>>>>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ >>> >>>>>> >>> >>>>>> >>> >>>>>> _______________________________________________ >>> >>>>>> Kamailio (SER) - Users Mailing List >>> >>>>>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>>>> >>> >>>>> >>> >>>>> _______________________________________________ >>> >>>>> Kamailio (SER) - Users Mailing List >>> >>>>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>>> >>> >>>> -- >>> >>>> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ >>> >>>> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda >>> >>>> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ >>> >>>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> Kamailio (SER) - Users Mailing List >>> >>> sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >> >>> >> -- >>> >> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ >>> >> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda >>> >> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ >>> >> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ >>> > >>> > >>> > _______________________________________________ >>> > Kamailio (SER) - Users Mailing List >>> > sr-users at lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> -- >>> Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ >>> www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda >>> Kamailio World Conference -- www.kamailioworld.com http://www.kamailioworld.com/ >>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com http://www.asipto.com/ >> >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- > Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ > www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda > Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ > Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/
The xmlrpc module has its own callback, you should not use the one from xhttp module, see:
- https://kamailio.org/docs/modules/5.3.x/modules/xmlrpc.html#xmlrpc.pevent_ca...
Try with this one and see if the logs are still there. You may need to set some other modparams for xmlrpc module if you want to still use xhttp, so you split the handling based on URL.
On the other hand, I am not sure what causes those error messages, even when attempting to use xhttp callback, one seems to be trying to get value of $ci. Do you have topos module loaded? Any other event route callbacks that you have?
Cheers, Daniel
On 13.02.20 12:34, Miteshkumar Thakkar wrote:
[...]
On 22-Jan-2020, at 1:57 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Have you run rtpengine in debug mode to see if it gives some hints why is retrying the same command?
Is it happening for every call and coming over the same connection?
I do not know if this is by design, but if there is something to be tune, I think the best place is inside RTPEngine, geting the response that dialog is not found seems the right one from my point of view, given that the rpc command can be used by other apps.
Agree. I have posted the same to RTPEngine. They have taken care and created a patch for that. Thank you very much for help.
OK, good to know.
A small concern: When Kamailio receives an event dlg.terminate_dlg from RTPEngine, I am calling KSR.xmlrpc.dispatch_rpc() to process the event. Functionality is working fine. It is ending the dialog but with that it is generating below errors.
27(179) ERROR: pv [pv_core.c:704]: pv_get_callid(): cannot parse Call-Id header 27(179) ERROR: dialog [dlg_handlers.c:679]: pre_match_parse(): bad request or missing CALLID/TO hdr :-/
Should I worry about it?
Do you access $ci and use other dialog module functions when processing the xmlrpc command (inside the xmlrpc event route callback function)?
Not really. Here is what I am doing:
*local *rpc_method = /KSR.pv.get/(*"$rm"*) *or **""* * **if *rpc_method == *"POST" **or *rpc_method == *"GET" **then* * if not *(KSR.xmlrpc.dispatch_rpc()) *then* * **/logger/*.log(*"err"*, *"error"*) *end* * end*
Where is this piece of code executed?
This is the only code in function ksr_xhttp_event(e), which is executed when the event from RTPEngine is coming.
-Mitesh
On 13-Feb-2020, at 7:00 PM, Daniel-Constantin Mierla miconda@gmail.com wrote:
The xmlrpc module has its own callback, you should not use the one from xhttp module, see:
- https://kamailio.org/docs/modules/5.3.x/modules/xmlrpc.html#xmlrpc.pevent_ca... https://kamailio.org/docs/modules/5.3.x/modules/xmlrpc.html#xmlrpc.pevent_callback
Try with this one and see if the logs are still there. You may need to set some other modparams for xmlrpc module if you want to still use xhttp, so you split the handling based on URL.
I have removed use of xhttp. The xmlrpc is handling the event properly. Thanks for suggestion. But, those errors are still coming. :(
On the other hand, I am not sure what causes those error messages, even when attempting to use xhttp callback, one seems to be trying to get value of $ci. Do you have topos module loaded? Any other event route callbacks that you have?
No, the module todos is not loaded. I’m not trying to fetch value of $ci in the event handling.
Thank you, Mitesh
Cheers, Daniel
On 13.02.20 12:34, Miteshkumar Thakkar wrote:
[...]
> On 22-Jan-2020, at 1:57 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote: > > Have you run rtpengine in debug mode to see if it gives some hints why is retrying the same command? > > Is it happening for every call and coming over the same connection? > > I do not know if this is by design, but if there is something to be tune, I think the best place is inside RTPEngine, geting the response that dialog is not found seems the right one from my point of view, given that the rpc command can be used by other apps. > Agree. I have posted the same to RTPEngine. They have taken care and created a patch for that. Thank you very much for help.
OK, good to know.
A small concern: When Kamailio receives an event dlg.terminate_dlg from RTPEngine, I am calling KSR.xmlrpc.dispatch_rpc() to process the event. Functionality is working fine. It is ending the dialog but with that it is generating below errors.
27(179) ERROR: pv [pv_core.c:704]: pv_get_callid(): cannot parse Call-Id header 27(179) ERROR: dialog [dlg_handlers.c:679]: pre_match_parse(): bad request or missing CALLID/TO hdr :-/
Should I worry about it?
Do you access $ci and use other dialog module functions when processing the xmlrpc command (inside the xmlrpc event route callback function)?
Not really. Here is what I am doing:
local rpc_method = KSR.pv.get("$rm") or "" if rpc_method == "POST" or rpc_method == "GET" then if not (KSR.xmlrpc.dispatch_rpc()) then logger.log("err", "error") end end
Where is this piece of code executed?
This is the only code in function ksr_xhttp_event(e), which is executed when the event from RTPEngine is coming.
-Mitesh
-- Daniel-Constantin Mierla -- www.asipto.com http://www.asipto.com/ www.twitter.com/miconda http://www.twitter.com/miconda -- www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com http://www.asipto.com/ Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com http://www.kamailioworld.com/