Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

sx200 SMDR Fail

Status
Not open for further replies.

guitartech

Technical User
Feb 11, 2008
80
CA
I'm working on a sx200 EL lw19

We changed providers and the old trunks were ground start analog, the new loop start.

The trunks work fine but the last smdr record that worked was in October, the same day we cut the lines over. No programming was changed, and I checked the smdr cabling too.

Is there a way to test from the printer port into hyperterminal? I tried setting it up with the matching baud rate and made some test calls with no result. I'm not sure the protocols using hyperterminal, I have vt100 set already.

Any info would be awesome.
 
Hi, in form 34 verify that you are indeed printing to the printer port, (serial port). It should look something like this:

>? Printer Port ? SMDR ? Autoprint ? NO ?<

And i suspect somewhere in form 4 there is a "type of report" option, check your manual on the cd or google for a mitel sx 200 guide.

Hope that helps!

 
There is a maintenance function to monitor SMDR
System - Monitor - SMDR

If your system is programmed correctly the SMDR will appear in the monitor window.

If the monitor does not work, correct your programming
- Form 3 COS Options
- Form 16 Trunk Grp Options
- Form 34 Directed IO Options

If the monitor works, check your terminal.
- Wrong speed
- Bad cable
- Flow Control Set Off with Ctrl-S (Ctrl-Q sets to ON)

**********************************************
What's most important is that you realise ... There is no spoon.
 
The programming was already there and working. The only difference was the trunks being changed from ground start to loop start.

Is there anything different in programming between the 2 types? I can't see any, it's just jumpers on the trunk card that should have nothing to do with smdr.

I did look into system - monitor - smdr and got nothing from it when I made a call out. I'll verify if there is something missing in programming but I think something else is wrong.
 
The monitor would show the traffic if the programming is correct.

Form 34 would not likely change
Form 3 COS might be different
Form 14 would assign COS
Form 16 might be different.

Another thought - In the trunk cct descriptor - Is Answer Supervision Expected set to YES?

Have you tried to see if Inbound is OK vs. Outbound

**********************************************
What's most important is that you realise ... There is no spoon.
 
Try sending a CTRL-Q into the printer port.

Alternatively, delete the printer option in form 34 and then reprogram it.

**********************************************
What's most important is that you realise ... There is no spoon.
 
I checked programming again and looks OK so I disabled and enabled the SMDR in form 16 and now I can see when I call into the system with SMDR monitor on it only shows the trunk, the time/date, and duration but no phone number.

I Tried deleting and building the printer port in form 34 but seems like a no go either.

Is it supposed to show the phone number when in SMDR monitor? Also when people are calling out it doesn't show anything.

I'll try the control Q when on site again.
 
The monitor should show everything you would normally see on the printer.

Not showing outbound digits is not usual. I'm not sure what if anything could cause that. I'm starting to think a reboot might be in order.

**********************************************
What's most important is that you realise ... There is no spoon.
 
The trunk start type changed. Change the trunk descriptors to reflect that. timers, disconnects, reversals, Refer to EL/ML Technician's Handbook.

NO GOOD DEED GOES UNPUNISHED!
 
Ended be the trunk circuit descriptor. I made a new one and it worked, but can't figure out why the original descriptor wouldn't have worked, it's the same. It's an old POS so I won't dwell on it. Lesson learned for next time.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top