Clarification with configuration of voice logger

[adityapranavbhuvanapalli]

I have 2 scenarios.

1. Voice Logger receives SIP INVITE and OK and RTP corresponding to the source and destination matching invite and ok.
2. Voice Logger receives RTP with no prior SIP packet sent

Can you please suggest what changes can be done in configuration to restrict voice logger only to record the 1st scenario and not 2nd?

[kingster]

Hi @adityapranavbhuvanapalli

I don't think that is possible to do this at the time of capture, however, you should be able to distinguish between the two based on the tracker data and have a cleanup script to delete the non-required files.

Does this help your use case? What is the exact problem that you are trying to solve?

[adityapranavbhuvanapalli]

Hi @kingster
In my application, along with voice logger, 2 networks are connected. When the corresponding networks are unavailable, my application broadcasts the packets which results in duplicate recordings.

I will try to implement a clean up script to delete the redundant ones.
In case, you think a better approach is possible, please let me know.
Thanks.