I have a CM3.1.2, 2 port network with a 2602 in each PN.
we are experiencing one-way calling issues on heavy IP phone usage days (when the 2602 seems to hit about 9mb in activity). I am at V25 on my 2602 firmware and tried to upgrade to V33. It loaded to the 2602 just fine and when I scheduled the download it completes fine (via 'test firmware download 1') but when I check 'status firmware download 1' it shows Aborted and reason code 6208. I can't find ANY documention on the reason codes.
So ANY help would be great on figuring out the problem with getting this loaded.
I am also curious about how the 2602's in seperate port networks load balances between the 2 on IP calls. It appears when I check the DCP's on each the 2nd port network 2602 carries about 1/3 the traffic.
we are experiencing one-way calling issues on heavy IP phone usage days (when the 2602 seems to hit about 9mb in activity). I am at V25 on my 2602 firmware and tried to upgrade to V33. It loaded to the 2602 just fine and when I scheduled the download it completes fine (via 'test firmware download 1') but when I check 'status firmware download 1' it shows Aborted and reason code 6208. I can't find ANY documention on the reason codes.
So ANY help would be great on figuring out the problem with getting this loaded.
I am also curious about how the 2602's in seperate port networks load balances between the 2 on IP calls. It appears when I check the DCP's on each the 2nd port network 2602 carries about 1/3 the traffic.
