you are making an outbound call to your own box, so the three calls are the outbound call, the inbound of the same call (which will of course have a different uuid), and i assume the 3rd is whatever happens with that inbound leg. In this case, its tricky to track them, but also totally unnecessary to make a call that way. Why are you looping back to yourself with a sip call instead of calling the correct intended destination to start with?
On Feb 1, 2018, at 5:53 AM, Kinshuk Bairagi <kinshuk1989@gmail.com> wrote:
Hi
I am trying to track the status of the calls while making call via esl_inbound socket interface, but while making call, the call forks into multiple legs and new uuid's are generated without any ability to track them. Is there something wrong?
Command Issued : originate {origination_uuid=95622d76-9a98-48d7-a53b-6f55598d78e1,origination_caller_id_number=9876,origination_caller_id_number=0000,originate_timeout=30}sofia/internal/1001@10.85.185.65 <mailto:1001@10.85.185.65> &park()
This causes multiple call-legs, with 3 uuids : Portal Screenshot https://i.imgur.com/ahPdvFK.png <https://i.imgur.com/ahPdvFK.png>
Log : https://gist.github.com/kingster/88d9e64368e3a2af4a6f603d81100457 <https://gist.github.com/kingster/88d9e64368e3a2af4a6f603d81100457>
How can I track co-relation between this call-legs? What is the reason that 3 call legs being created, any way to skip that?
Thanks Kinshuk