|
|
Joined: Aug 2003
Posts: 1,281
Moderator-Telrad
|
Moderator-Telrad
Joined: Aug 2003
Posts: 1,281 |
What's the version of the MPD's ( both sites). I don't think n-12 cards were supportted in early version 7 and maybe not at all. You might have to be E2E. I have to check when I get back to my office but I 80% sure about that. You should also get the latest SB7 software.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Aug 2002
Posts: 4,925 Likes: 1
Administrator
|
|
Administrator
Joined: Aug 2002
Posts: 4,925 Likes: 1 |
I have a SB7.36 128 with a N12 card to NY Verizon providing the T1 only issues I had was verizion and the Bell in NY couldn't keep the pipe up so we were seeing the same errors. FYI the last verision of SB7 is 7.42 there were problem corrections as well as feature changes thru the 7's. Telrad did a no cost upgrade to all users (thru the dealers of corse) with 7.20 to bring them to 7.36 which fixed several bugs. But that freebe was atleast 3 or 4 years ago. 7.42 chipsets are available just shipped out a set last month.
|
|
|
|
|
Joined: Jul 2006
Posts: 11
Member
|
|
OP
Member
Joined: Jul 2006
Posts: 11 |
I remember that when the vendor came in to install our Emagen Voice Mail system they changed the chips. I don't know what they changed them to though. They also changed the Memory on the MPD units. I will have to wait for some downtime to pull the MDP to check what the chips are.
|
|
|
|
|
Joined: Aug 2003
Posts: 1,281
Moderator-Telrad
|
|
Moderator-Telrad
Joined: Aug 2003
Posts: 1,281 |
You can check on your laptop with no down time. Do you have access
|
|
|
|
|
Joined: Aug 2002
Posts: 4,925 Likes: 1
Administrator
|
|
Administrator
Joined: Aug 2002
Posts: 4,925 Likes: 1 |
Also check the frimware chips on the N12 while you have it down. They should be:
0.8(4B31) Frim
0.7(66A8) Main
0.7 (DEA3) Main
|
|
|
|
|
Joined: Jul 2006
Posts: 11
Member
|
|
OP
Member
Joined: Jul 2006
Posts: 11 |
MPD400 at the Main Office:
V1 (E3AC)
V0.4 (763F)
128 at the Branch Office:
MPD 1.4 (ED46)
V1.0 (282A)
The N12s are:
0.8 (4B31)
0.7 (DEA3)
0.7 (66A8)
|
|
|
|
|
Joined: Aug 2003
Posts: 1,281
Moderator-Telrad
|
|
Moderator-Telrad
Joined: Aug 2003
Posts: 1,281 |
Please gives us the versions of the MPD 128 and the MPD of the 400. 7.XX
|
|
|
|
|
Joined: Jul 2006
Posts: 11
Member
|
|
OP
Member
Joined: Jul 2006
Posts: 11 |
Hello,
On the 400 it is 7.23 with a handwritten "A" after the 7.23. This is on the module. The chips in the module have 7.39 printed on them.
On the 128 it has a "Printed" 7.20 with a handwritten 7.23 on the module.
Is there another way to check?
|
|
|
|
|
Joined: Aug 2003
Posts: 1,281
Moderator-Telrad
|
|
Moderator-Telrad
Joined: Aug 2003
Posts: 1,281 |
That's your problem. You need to be a higher version on the mpds software. At the very least 7.39
|
|
|
|
|
Joined: Jul 2006
Posts: 11
Member
|
|
OP
Member
Joined: Jul 2006
Posts: 11 |
I will physically check the 128 today. I noticed these errors listed in the "display last reset alarm history" on the 128,
*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 5h F7h C1h 18h 1h 15:30 JUL 24,2006
*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h 4h 15:30 JUL 24,2006
*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h 9h 15:30 JUL 24,2006
*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h Ah 15:30 JUL 24,2006
*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h 5h 15:30 JUL 24,2006
*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h Fh 15:30 JUL 24,2006
*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h Ch 15:30 JUL 24,2006
*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h 7h 15:30 JUL 24,2006
*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h 8h 15:30 JUL 24,2006
*** SOFTWARE ALARM MSG ***
FIRMWARE - ULD SOFTWARE ERROR
MSG (DEC) = 21 0 18 6 0h 4h F7h C1h 18h Dh 15:30 JUL 24,2006
Is this being caused by having the wrong chips in the MPD?
|
|
|
|
Forums84
Topics94,291
Posts638,815
Members49,767
| |
Most Online5,661
May 23rd, 2018
|
|
|
0 members (),
119
guests, and
421
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
![[Linked Image from sundance-communications.com]](https://www.sundance-communications.com/ad-icon/1013.gif){kind=icon}