How does telco VM Message Waiting work on MICS 4.1?

[KrisBoutilier]

This is a two part question:
Using CLID capable analog trunk cartridges the MICS will support lighting MWI on specific stations using target line appearances and the 'Extl VMsg set' options. How exactly does it do this from the CO perspective? Is this just through the 'message waiting' bit in the CallerID burst being set and unset? Would this require the CO to do a 'one ring' call to deliver? Also, is this CallerID just coming in as normal 1200 baud FSK data?

Part two:
I assume this would work identically if you were using, say, E&M RBS trunks over T1. Now what about PRI? Can my CO still deliver the MWI bit through the Q.931 SETUP frame Display Information Element somehow? Obviously they're not going to be running MCDN... If it can be done over PRI (regardless of what flavor, DMS100, NI2, 5ESS etc.), can someone refer me to the right Bellcore Interface Document for telco driven MWI over PRI?

Thanks.

 

[jerryreeve]

There is not an attention ring sent before the data burst that contains the message bit. you could have that show up without a ring or without the customer pulling dial tone at all. (noted this while monitoring thru a butt set.)

As far as I know you need to use CID trunks only and only 1 CID per mailbox.

sorry I don't have the bellcore docs though.

If voting could really change things, it would be illegal.

JerryReeve
Communications Systems Int'l
com-sys.com

 

[rhowlett]

The old way was stutter dialtone. Not sure if that's true in your case. You could find out by picking up the line when you know you have a message. If the dialtone stutters instead of being steady, that's how it knows.

 

[KrisBoutilier]

Actually, I'm looking for the Visual Message Waiting Indication system, not Audiable Message Waiting (aka. stutter dialtone).

The FSK signalling method is documented in:

http://about.telus.com/publicpolicy/pdf/id-0001.pdf

And the VMWI for FSK in:

http://about.telus.com/publicpolicy/pdf/id-0008.pdf

It follows therefore that the same technique would work for RBS signalled T1 channels (don't know if the CLID cartridge is still needed in conjunction w/non-PRI T1 though).

I think what I'm looking for to document VMWI over PRI is specified in bellcore document GR-866-CORE (ISDN Message Service Generic Switching and Signaling Requirements). Shame about the cost though...

 

[jerryreeve]

I was told a few years ago that you can't get CID over a T1. I never found docs to back it up though.

one way to check it on Copper CO lines is to put a butt set in monitor and listen to the target line while someone else leaves a message for the target line. you will hear within a few seconds of the end of message the tone burst with no ringing.

If voting could really change things, it would be illegal.

JerryReeve
Communications Systems Int'l
com-sys.com

 

[BagsNYC]

I have heard the same Jerry. Need PRI for Caller ID services.

 

[senk1s]

technically callerID information can be sent on a T1 trunk using the ABCD bit signalling - it depends on the service provider as well.

in a PRI - all the signalling is over the D channel

 

[KrisBoutilier]

Senk1s: do you have a reference (bellcore or otherwise) for the CallerID bit twiddling protocol for non-PRI service? I'd like to have a read.

Thanks.

 

[hawks]

I know in the NORTEL docs they call it IN Band ANI (caller id over standard T1 service)