Antonio,

I created new network-interface, intended just for OCSM, and created the realm on top of it. One interesting thing I revealed in this analysis: if you create just network-iface, add proper host-route and connects comm-monitor to this iface, then nothing works. There are SYN requests from SBC to OCSM and SYN,ACK responses from OCSM to SBC in packet-trace captured on the network-interface, but there are no ACKs from SBC to OCSM. If you check log.atcp, then there will be no those SYN,ACKs only SYNs. So, SYN,ACK are lost somewhere between network-interface and atcpd daemon. IP address of OCSM does no appear in any acl or ip connection table or even in shell's 'netstat -a' output. Once you create realm, SBC stops blocking of the SYN,ACKs. So, without the realm, the network-interface is absolutely useless hole.

Regards, Daureen

Hello,

According to OCSM graph "Active calls" the number of active session had abruptly grown from normal ~8K to ~18K. This issue occurred on September 5 afternoon. After we connected comm-monitor to media ports on September 26 the number of session had fallen to normal 8K. There were no changes made on SBCs before September 5 that could cause the issue. Also there were no changes on network that could somehow reduce the bandwidth in mgmt vlan (and reduce the throughput of wancom0).

All SBCs connected to this OCSM generate ~5K session in total.

Regards,

D