Legend 100D question 5

[BTU789]

Hi, my customer has had some issues in the expansion carrier. This all started when the 007MLM in slot 6 went bad. After I replaced the vm, slot 7 (408 gs/ls mlx) and slot 8 (408 gs/ls mlx) didn't work. But the 100d in slot 9 worked. Then I replaced the 408 in slot 7. The 408 in slot 8 and the 100d in slot 9 do not work. I replaced the backplane and the 100d card today. Everything seems to work except the trunks associated with the 100d are forever busied out. No matter how many times I reset the slot, busy out and restore the slot, or busyout and restore the trunks, the trunks remain busied out. Any ideas would be helpful because I'm at a loss. Hopefully it's not the processor.
Thanks,
Brian

 

[Telecomboy]

Just make sure you have a backup in case you need to restore it. Then, default the system and reprogram the PRI from scratch. I am thinking something was corrupted in the programming causing the lines to always be busy. To default the system: Maintenance, Slot, 00 Enter, Demand Test, F3 Twice, F2 for Yes. This will erase all programming on the processor.

 

[BTU789]

So, that means I have to reprogram the whole system from scratch correct? Not just the T1.

 

[Telecomboy]

Yes. But that is why you have the backup. If you default it, program the PRI card, and the lines are still busy- just restore it. If you default it, program the PRI, and now the lines are free- you know it is corrupt programming and you will need to program it from scratch. A headache, but if it solves the issue it is worth it.

 

[BTU789]

I have an old backup on my laptop from 2012. How do I restore this backup file from my laptop?

 

[Telecomboy]

There is a separate Restore and Backup (I believe it is on the main page of wispm).

 

[BTU789]

So I defaulted the system. It is in key mode and I'm trying to change that. But, I am now able to make outbound calls from the T1. I haven't even put the lines in the pool yet. Is it because it's in key mode?

 

[Telecomboy]

I assume you are just grabbing the line via the operator console. Then yes, by default it will put the lines on the operator phone. I would program it hybrid and then program the PRI card and test. It looks like defaulting cleared the issue.

 

[BTU789]

I found the restore option under tools on the top of winspm.

 

[BTU789]

Thanks Telecomboy for all your help. I'll post the end result when I'm done.

 

[BTU789]

I restored the system programming using a backup file that was on my laptop from 2012. The system is up and running. Tested inbound and outbound and it looks good so far.

Thanks again Telecomboy for all the advice and the time that you gave to me to help fix my cutomers issues.

Brian

 

[Telecomboy]

No problem. Glad it is working.

 

[CarGoSki]

advice was offered to restore a backup a few days ago. I do understand how things can become foggy in battle.
If weekly backups are turned on then you can at least count on a backup from the previous Sunday at 2am to use.
Merlin 100D bottom line is that you have to un-build all of the trunk programming from the slot it came from and the slot it is going to before you move to card from one slot to another. As you have found the 100d is very particular about existing programming and responds by not working as you expect it.

 

[BTU789]

You're correct CarGoSki, you did offer that advice. Sorry if I overlooked that part.
Brian

 

[CarGoSki]

Thanks for the star.

 

[BTU789]

Alright so I'm back at the customer. Outbound calls go out on the T1. Inbound are still coming in on the POTS lines. The customer had the main number and all DID's forwarded to the POTS lines when the T1 was down. They say the called Broadview and had them unforwarded. They also had Broadview onsite yesterday and they are saying they can't see the phone system. I wish I was here when Broadview was here so we could hammer this out. Today, I've defaulted the system and restored a backup again just in case I may have done something after the restore the other day. Same thing though, inbound come in on the POTS lines. I thought that once the system sees the T1 up all calls should be directed to the T1.

 

[BTU789]

Now they tell me when inbound calls are unforwarded the calls ring once and get disconnected. So they put the forwarding to the POTS lines back on for now. The system programming looks good to me. But is there something I may have missed? When I do a system restore I shouldn't have to tweak any programming correct?

 

[BTU789]

Broadview just removed the forwarding and now the calls come through the T1! It's a provider miracle! LOL

 

[CarGoSki]

If you had the password to Monitor in spm and could turn on tracing for the trunks you would have been able to see if the calls truly hit your system. Having to rely on the provider to give good information is dodgy. You can find the monitor password if you examine winspm.exe in a hex reader app. Once you find the password and connect to monitor you can issue ? to learn the commands. Be sure to turn off all tracing before you quit or they will always run and occupy cpu.

 

[BTU789]

Thanks again CarGoSki, everything is working now. And yes I have the monitor password. The only small issue they have is with the MWL. They stay on even when the mailbox is cleared. I've already seen some other posts on here about what to try. I've tried all the usual stuff like deleting and recreating the mailbox and busying out the ports. Next I'll be resetting the voicemail itself and see what happens.

 

[Telecomboy]

Is it a merlin messaging? Did you rotary enable the vm ports? Also, it is the last port of the voicemail being used that sends the mwl on/off signal. Make sure that port is working/programmed properly.