Merlin Legend and Caller ID 1

[compuveg]

We've got a legend system with merlin messaging. I'm not very familiar with the stuff, but there's a bunch of 012 boards, a 100D, and a few 012 boards.

Can I get caller ID to show on our mlx-10d handsets? We're running magix 2.1, winSPM 6, merlin messaging 2.5.... I would think it is all caller ID capable, yes, no?

Would the default config be to show caller ID info on the phone if it was available?

If I need a board like the 408 gs/ls-id-mlx instead of the 408 gs/ls-id-mlx I've got, would just one do the trick, or would they all have to be replaced? I thought the 408 board was for either internal or external lines, and they're all setup for internal I believe. Wouldn't the 100D be what picks up the ANI?

Thanks, in advance--

 

[Telecomboy]

If all calls are coming in through the 100D (No POTS lines), then you should get caller id on all digital phones. I could be wrong, but I do not think caller id is compatible with single-line telephones. Those are the phones plugged into the 012 boards.

 

[SYQUEST]

No, the 100D module does not "pick up" ANI, nor do the 408GLM-ID modules. CID and ANI are NOT the same thing! The Legend/Magix provides CID for analogue lines connected to 408GLM-ID modules and the CID number only when utilizing PRIMARY ISDN on the 100D module. When the incoming call rings, the CID is provided on the phone if it is sent from the CO between the first and second ring for analogue lines. On PRI it is part of the call setup message and is presented on the appropriate phone(s) at that time. No other type is supported. The Legend/Magix does NOT support any CID on analogue single line sets of any type.

....JIM....

 

[compuveg]

Well, that makes me wonder why we've got no caller ID. All the handsets are MLX-10Ds, which are digital handsets. All our phone lines are provided through the 100D board. There's little instruction on the internet regarding programming the system. What I've been able to find sounds like caller ID should show up by default.

I've been on Tek-Tips a long time, and didn't even know they had phone system message boards until Googling showed it to me.

Any pointers the right direction will, of course, be very appreciated.

 

[Telecomboy]

Do you have a PRI or do you have a T1 through your provider?

 

[Telecomboy]

There's no programming to do on the Legend to accept Caller ID. The provider sends it and the Legend passes it through. I would make sure your provider is sending it through. Caller ID is NOT always a default feature through your provider. It is an "extra".

 

[merlinman]

OK, Allow me to clarify a few things.

Yes, Caller ID must be provided by your Dial Tone Vendor.

No, Single line sets WILL NOT SHOW CALLER ID.

And Last, THERE REALLY IS some programming required to make Caller ID work (if you ARE getting it from your provider).

That programming is LS-ID Delay. It is done like this:

Sys Prog > Start/Exit > Lines & Trunks > More > LS-ID Delay > then touch the corresponding Button for the lines so equipped.

But FIRST, you must verify that your Dial Tone Vendor is providing it.

I hope this helps.

http://home.comcast.net/~merlinman

 

[compuveg]

I've double-checked, and here's the actual config... in the order it is in the mounting, as if that makes a difference.

Power
Processor w/CKE5
408 GS/LX-MLX
408 GS/LX-MLX
408 GS/LX-MLX
408 GS/LX-MLX
408 GS/LX-MLX
Power
408 GS/LX-MLX
012 W/Ring Gen
012 W/Ring Gen
100D
008 MLX
Merlin Messaging 617C49

This article I found though, which doesn't mention what the case is if you have a 100D/DS1 interface instead of analog lines, says that you've got to have 408 GS/LX-ID-MLX boards.

http://support.avaya.com/japple/css...eID=129534&temp.bucketID=108020&PAGE=Document

I've also found some manuals on Avaya's site, but WinSPM is pretty intimidating and the manuals are for someone with more familiarity with this stuff.

 

[compuveg]

We have a PRI as the vendor (Sprint) told me.

 

[merlinman]

Hmmm...

I thought you had ID modules for the 408 MLX cards you have.

Alas, you do not.

Therefore, if you are getting caller id sent to you over any of those loop start lines, then you would need the GS LS ID modules.

PRI service should provide NUMBER only with no additional programming.

So, are you using ONLY the PRI or what?

http://home.comcast.net/~merlinman

 

[compuveg]

Yes, we're only using the PRI. The 408 cards are only used for the MLX-10d handsets, and not to provide external lines, though I'm sure one is used to provide analog lines for fax, postage, etc.

BTW, thanks a ton for even reading my PBX newbie posts.

 

[compuveg]

I was able to get to the screen where you can program the LS-ID Delay. However, when I get there, the screen is rather confusing. Here's what it looks like.

-----------------------------
-LS-ID Delay: -
-ENTER TRUNKS W/LS-ID DELAY -
- -
-LINES 1-20 ENTRY MODE -
-LINES 21-40 -
-LINES 41-60 -
-LINES 61-80 -
-BACK -
-----------------------------

If I select any of the 'lines' options, it just turns red. Entry mode is pretty cryptic, looking something like this.

-----------------------------
-LS-ID Delay: -
-Enter trunk number for -
-alert delay -
- -
- Delete -
- -
-Backspace -
-BACK Enter -
-----------------------------

Is this asking for the extension, internally, that should get the caller ID info? Like, if my extention 203 is mapped to line 816, would I input 816?

 

[compuveg]

Actually my extension is 230, with logical id of 30, and its adjunct is 530.

Feeling daring I put in '530' on the enter trunk number' screen and there's no apparent change.

 

[merlinman]

You stated that you are ONLY USING PRI.

Therefore, the setting for LS ID DELAY does NOT APPLY in your case what so ever.

That setting WOULD ONLY APPLY if you were using LOOP START LINES with caller ID, and you are not.

If you were, the way you would program the lines to use the LS-ID Delay would be to illuminate the button that corresponds to the Line on the screen you were looking at.

But again, you are not getting caller id over LOOP START LINES.

If you are not getting caller ID over your PRI, there maybe something set wrong with your PRI, but NOT LS-ID DELAY.

http://home.comcast.net/~merlinman

 

[compuveg]

After a day's research, I'm beginning to think that this is what happenned...

Long ago our phone system had inbound LS or GS lines. My company was too cheap to pay extra for the boards that have caller ID on them. When they upgraded to a PRI for inbound lines, they thought they would have to pay for extra boards to handle the caller ID, so they didn't get the PRI with ANI info being piped in.

... That's just a theory. I'm checking with Sprint to see if it is possible that they just turn on the ANI signaling. From what I've read, we should get caller info if they do.

 

[SYQUEST]

I guess you missed my post, 3rd from the top? ANI is NOT CID.

....JIM....

 

[compuveg]

Well, your initial posting was a little comfusing to me, as you stated, "No, the 100D module does not "pick up" ANI, nor do the 408GLM-ID modules." As I understand, the 100D should understand ANI info being sent. That info should make it to the mlx-10d handsets even if they are connected to a 408 GS/LS-MLX board, as the 408 GS/LS-ID boards pickup the Caller ID info from GS/LS lines. provision of the calling number can be provided to MLX-10d handsets regardless of which of the 2 boards are in use.

I did understand when you said CID and ANI are NOT the same thing!

I presume that ANI is provided over the D channel of a T1. From what I understand Caller ID is signaled in the subaudible bandwidth of an analog line.

It makes about as much difference as calling your cable/dsl modem a cable/dsl router. It is technically correct, but who cares, as long as the end user's phone shows the number of who's calling it?

The bottom line is that I've got a PRI and Sprint's trying to charge me a $200 setup fee and $0.01/call for that information that should be provided as part of the service.

 

[SYQUEST]

I just want to clear up the confusion. ANI is NOT sent to any analogue lines. It is NOT part of any line side signaling format. There is only one or two ways ANI is sent to a customer's equipment, and that is on a Channelized DS1 using a two-stage DTMF or MF format. The type of service usually is INWATS TOLL FREE, and from an IXC Tandem switch. In SS7 (Signaling System 7) ANI (Automatic Number Identification) has a data field which is separate from the CID data field in the call record. In some cases the same data may be present in both fields, but not always.

It is NEVER part of PRIMARY ISDN or Basic Rate ISDN, and is not sent on the DCH. CID (Caller ID) is sent on analogue Loop-start lines in a data burst between the first and second rings only. For ISDN service the data is sent as part of the call setup message on the DCH.

The terms are not interchangeable.

Hope that helps!

....JIM....

 

[compuveg]

Well, despite your patience I don't understand the difference, unfortunately. It sounds like ANI isn't sent on a PRI, but I don't know exactly how we do get calling party information aside from ANI or CID.

I did get email from the Sprint rep, here's his response to my 'what do we have if it isn't T1 or ISDN' question...

"Your line is a dedicated T-1. Much like a PRI (provides 23B+D) or ISDN but the difference is the T-1 doesn’t have a D channel for signaling. "

Knowing this, I think I now know my question...

Is it possible to get the calling party's number displayed on MLX-10d handsets connected to 408 GS/LS boards when the inbound lines are provided via a dedicated T1 into a 100D board?

Should I post this on another thread? This one's amazingly long and hard to follow...

Thanks for all the info though.

 

[SYQUEST]

I just posted in your other thread. But to clear up some of the confusion, please post a print of the DS1 configuration on your Legend PBX showing all the lines/channels. Then we can speak more intelligently about what you may or may not be getting in terms of service, and clear up once and for all what you have: CAS or PRI.

....JIM....