![]() |
|
|
#1 (permalink) |
|
PBXtech SILVER 25+ posts
![]() Join Date: Apr 2004
Posts: 36
![]() |
IP 406 problem
Hi there,
I have a problem with an IP 406 system. At first it was working fine, change numbering plan etc..Then after an immediate restart i got the following message: Constructor StaticHeap=52 DynamicHeap=8597036 NoCacheStaticHeap=3880460 NoCacheDynamicHeap=1255924 Overflow=0 Factory Test Status 00000001 Product Variation Status ffffffff Alarm Logging enabled (max entries=20, in use=0) found FLASH file: ..\modem\zmbin004.s37, len=790 found FLASH file: ..\modem\mcode.bin, len=40000 found FLASH file: ..\vcomp\48105ak.310, len=e2 found FLASH file: ..\vcomp\48105ae3.310, len=1ed40 found FLASH file: ..\nabranch\onehz.bin, len=3e80 found FLASH file: ding.pcm, len=40a htl 00010000 hth 20400000 Mapper: MTSS detected or bad chip Expanding MPPC image ... I resent the ip406.bin file but still the same problem. When i leave it off power for a few hours it may start again. When i try to make any changes and restart immediately though i get the same problem again. Anyone has an idea how to solve this? Thanks Andreas Iacovides Telecom Engineer |
|
|
|
|
|
#2 (permalink) |
|
Moderator
![]() Join Date: Sep 2003
Posts: 561
![]() |
Re: IP 406 problem
What is the actual symptom that prompted you to fire up monitor?
Without more info, sounds like you may have a unit that was loaded with a test configuration - avaya put out a tech tip (#24) to that effect. If so, all you have to do is default your unit. If you do so and it comes up configured for the wrong companding (A-law vs Mu-law in the system/telephony form) there is a specific DTE port procedure to correct this, let me know if you need it. (don't just change the option) Peter |
|
|
|
|
Advertisement
|
Sponsored links
|
|
|
#3 (permalink) |
|
PBXtech SILVER 25+ posts
![]() Join Date: Apr 2004
Posts: 36
![]() |
Re: IP 406 problem
Thanks for replying,
The actual problem is the the unit keeps reloading showing a looptest from the DTE port. I've tried the AT-X command and then sent the ip406.bin file again through the Manager. Is there another procedure that defaults the unit through DTE port? Thanks again Andreas Iacovides Telecom Engineer |
|
|
|
|
|
#4 (permalink) |
|
Moderator
![]() Join Date: Sep 2003
Posts: 561
![]() |
Re: IP 406 problem
Sounds like a defective... in any case probably more trouble than it's worth to fight with. Is it still in warranty? If so just get it replaced.
If not - try swapping the power supplies between the 406 and one of your expansion modules to eliminate the ps. Actually I would try that first regardless... :) Peter |
|
|
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Telco/Latency Problem | sdak | IP Office | 0 | November 18th, 2005 09:02 AM |
| Alliance IPO 406 together with Cisco Call Manager | ramam | IP Office | 0 | June 29th, 2005 06:20 AM |
| ISDN problem | Davide | Definity Servers | 3 | August 24th, 2004 03:19 AM |
| IP 406 resetting | crookie | IP Office | 10 | August 19th, 2004 02:59 AM |
| CFWD to external charging problem | hmursal152 | Meridian systems | 0 | July 17th, 2004 01:00 AM |