SCN up calls unobtainable 2

[teletechman]

I have a customer that has 2 IPOs 1 IP500V2 8.1.69 one IP500V2 9.0.4 with an SCN that is up. What happens is once a day around 11am to noon EST the calls between site will try to connect then get unobtainable. I have a trace.

445182244mS CMLineRx: v=18
CMReleaseComp
Line: type=IPLine 18 Call: lid=0 id=92196 in=0
Cause=38, Network out of order
11:09:18 445182244mS CMTARGET: 343.92194.0 18727 DMastrangelo.1: Re-target after NetworkOOO - Try: Shortcode(3601)

and a SSA capture of the call

Call Details DELETED!

Call Ref: 18732 Call length: 00:00:06

Originator
Current State: Dialling Time in State: 00:00:04
Currently at: Extn 702, DMastrangelo
Button Number: 2
Button Type: Call Appearance (CA)
Dialed Digits: 3601

Destination
Current State: Seized Time in State: 00:00:03
Trunk Used: Line: 18 H.323 192.168.9.3 Channel: 1

Call target / Routing information
Original Target: Extn RLake
Call Recording: No
Redirected to Twin: No
Routed across SCN trunk: No
Retargeting Count: 0

Trace Output:
3/4/15 11:09:56 AM-176ms Line = 18, Channel = 1, Q.931 Message = ReleaseComplete, Call Ref = 18732, Direction = From Switch
3/4/15 11:09:56 AM-181ms Call Ref = 18732, Originator State = Dialling, Type = User, Destination State = Clearing, Type = Trunk
3/4/15 11:09:56 AM-181ms Call Ref = 18732, Disconnect from Destination End

The SCN runs fine after a reboot, testing I did was to log on while the problem is occuring and access each IPO. The SCNs show up and I can ping from both site to the other VIA SSA IP SCN trunk ping. This is a weird site as the custoomer has both 3 digit and 4 digit extensions location specific, we are in the process or correcting this and upgrading to the same release.
Mike

 

[teletechman]

Tech support says that this is due to a memory leak in the 8.1.6X releases, they have told me to upgrade and this should fix it. I will let you know so if anyone has this problem in the future you have fix.
Mike

 

[holdmusic34]

Star for posting 'resolution'.

That was left handed.

 

[vid151]

wow, I am having the exact same issue this week. Same release, same issue...

thank you so much for posting.