The call record audit runs in bit and it indicates that the call
records are hung/suspended.
Per proc errors.
20120813:110731822:65347876:hmm(8131):MED:[CM6_proc_err:pro=7187,err=517,seq=3093,da=0(0x0),da2=65789(0x100fd)]
20120813:110731822:65347877:hmm(8131):MED:[CM6_proc_err:pro=7187,err=517,seq=3093,da1=0(0x0),da2=65790(0x100fe)]
Unfortunately we don’t have MST and details of the call scenario captured as the interchange was performed by the customer to resolve the situation.
Though the problem reported that the calls done/received at the same time via ISDN trunks were working, only SIP trunks were affected, we don’t have any evidence that this is indeed what happened.
Considering the limited data to diagnose, the proc error is leading us to believe to be a prime suspect and which is on the similar footprints mentioned in defsw112797 (Call records hung after receiving 603 Decline response), and hence the best bet would be to recommend this customer to upgrade to SP7 or even higher SP8.01 where defsw112797 fix has been included. Unfortunately even after the upgrade the problem still persists, please ask them to collect MST with Call Trace, SIP, proc
error, denial events etc to analyze the scenario.
