SYNC_DROP call logs
Page 1 of 1
SYNC_DROP call logs
I would like to know what could be the reason(s) for an SYNC_DROP in call logs?
This morning I had 2 NAPs that had a lot of SYNC_DROP and I would like to understand why?
This morning I had 2 NAPs that had a lot of SYNC_DROP and I would like to understand why?
Guest- Guest
Re: SYNC_DROP call logs
SYNC_DROP indicates that the call leg is no more present in toolpack_engine after re-synchronizing, and must thus be freed in the CAF (Customer Application Framework) application too.
If you do not have a SIP Proxy IP address on any NAP, the engine might be stopped working and the error can be seen regarding the NAPs that do not have SIP Proxy IP addresses.
So it is required to enter one of the IP addresses in the ACL to NAP SIP Proxy. It will still work and receive the calls from all the IPs even it is only receiving NAP for the calls. But leaving the NAP SIP proxy empty might cause a problem.
If you do not have a SIP Proxy IP address on any NAP, the engine might be stopped working and the error can be seen regarding the NAPs that do not have SIP Proxy IP addresses.
So it is required to enter one of the IP addresses in the ACL to NAP SIP Proxy. It will still work and receive the calls from all the IPs even it is only receiving NAP for the calls. But leaving the NAP SIP proxy empty might cause a problem.
Guest- Guest
Similar topics
» Inbound call no ringing
» How can I trace a call in FreeSBC?
» How much latency does this add to a call?
» call rate limiting
» Call Drops
» How can I trace a call in FreeSBC?
» How much latency does this add to a call?
» call rate limiting
» Call Drops
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum