NEC SL1100 NO DTMF

[daddybadger]

Hello,

Strange issue, I have a barrier working on a mobile sim that rings an analogue trunk. When answered pressing 3 should open the barrier, but this is not happening. It worked up until the point the firmware was upgraded from v2 to v7.13. I've swapped the hardware but will not work for love nor money. There are no issues with DTMF if the customer calls externally to an auto attendant.

Help appreciated.

 

[belevedere]

Check 14-02-1 for signal type = DTMF. If there are any analog ports involved, make sure 15-03-01 is set to DP for that port, and 15-03-03 is set to special.
Disconnect your external equipment from that trunk, swap in a known working CO line and test it. This verifies that the trunk port in the system is in fact sending the DTMF tones.
With that in place you might try going through the trunk test. MB 90-68.

 

[daddybadger]

Thanks, the barrier is calling in via a mobile sim so isnt connected to the line port of the system. I've already run the trunk test, that doesnt resolve it and as its effectively an external call and the digital extensions pick up this call.

As i stated this worked previously up until a firmware upgrade.

 

[belevedere]

What happens if you called in from a 2500 set? Do you hear any digits from that? I know there is an issue with DTMF using the iPhone. The upgrade may have changed some default parameters in the system.

http://hints.macworld.com/article.php?story=20110228091107335

 

[daddybadger]

That's the thing I don't get because I can clearly hear dtmf. It's not the barrier at fault because I've tested it straight from the line box. I checked the DTMF settings 80-02 and they're both the same data for V2 and v7.13

 

[OzzieGeorge]

I have, in the past had a DTMF register die. Only way I could fix it was to replace the main board!

 

[daddybadger]

thats not good @ozziegeorge. I swapped the kit Friday just gone with no improvement.

 

[daddybadger]

Weirdly enough, the kit that I swapped out I took home, defaulted and reprogrammed from scratch connected to my analogiue line - made a test call and it worked. So i'm now lost as to where the fault is. I'm due back at this customer today and hope it works.

 

[belevedere]

I have seen in the past a case where something strange was going on in the 1100 system. We get a back up, default the system, test at default. Then re-load the back up and everything worked fine. This is the case when the inmail stops working and it won't let you re-activate it. Usually when someone uploads all with hardware checked. At least you know the KSU is OK. You can use one of the PCPro tools that lets you compare your database to the default values. I woulds use that tool if after the upload it fails again. Then you know it's your database.

 

[daddybadger]

Thanks belvedere, had thought about the comparison of databases as a last resort but have a working KSU on board. I'll compare them once I've swapped the kit out again. The inmail probably sounds correct as it wouldn't respond to 555 from any extension.

 

[daddybadger]

Ok so looks like the inmail was at fault here. @belvedere do you know how to compare the dB? I thought it was under the file menu but can't find it.

 

[belevedere]

You can find it under tools.
To get the inmail back do the following;
Get a back up. Power down. Press and hold the red button on the CPU. Hold it while you power up. Keep holding it for ~10 seconds. Then release it. When the system comes up at default, check for the inmail operation. Next, reload your back up, DO NOT include blade configuration. Once the load is done, reset the system. I'd use the reset from PCPro tools icon. It's a second init, which is a reset. Test when back up. You might lose their AA script. You can back that up using USER1 with WEBPro before defaulting. Reload it later, or re-record it.

We found that sometimes when a full upload with hardware is done, it kills the inmail.
All told your looking at ~ 30 minutes of down time.

 

[OzzieGeorge]

I have in the past lost the inmail during an expansion as the memory locations change and yes you have to default it as belvedere says to get it back.