The last post I saw regarding this was June 2003 (before my time with *, I started in September): http://lists.digium.com/pipermail/asterisk-users/2003-June/013324.html Is there any support for Q.SIG in * at all? The Norstar MICS uses a MCDN (Meridian Customer Defined Network) key to enable the "SL1" protocol which from everything I've been reading is just Q.SIG. This protocol should enable * to turn on/off the MWI for Norstar's phones and combined with some OLI magic be able to have * take over the voicemail "features" <cough> of the MICS. Is Q.SIG a well-defined standard? Patent/NDA-encumbered? Is it supposed to be an interop protocol or do companies like Nortel bastardize it for their own nefarious uses? -A.
Just a followup so this stuff stays in the archives: Cisco's documentation on q.sig: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t2/qsigfm.htm Basically q.sig is modelled after q.931. It might then be possible to get * to handle q.sig natively without too much effort. q.sig seems to be more or less open as well; it follows a number of ECMA standards (or at least the implementation of q.sig that Cisco uses does). Regards, Andrew
On Fri, Jul 23, 2004 at 09:44:38AM -0400, Andrew Kohlsmith wrote:> Is there any support for Q.SIG in * at all? The Norstar MICS uses a MCDNAsterisk can do basic things w/ Q.SIG. Q.SIG is a LOT like q.931 in basic call handling, etc. The part where Asterisk lacks is in a lot of the detailed nitty gritty stuff. I could not get Caller-name to pass through (it uses some strange facility message to pass it) and some other basic features on the line. -- Matthew Fredrickson IRC Cresl1n
Just to keep the list/archives up to date. MCDN is not Q.SIG. The Norstar systems can do Q.SIG but they need to be configured as NON North-American in order to get the option to show up (and possibly require the use of E1 signalling now instead of T1). None of this really matters with * talking on the other end since you can easily put an E1 link in North America between the system and * but this kind of assinine vendor lock-in is enough to make me want to reverse-engineer their trade secret of MCDN and post it for the world to use just out of sheer aggravation. I'm still curious to see how different MCDN is from Q.SIG... Probably only enough to make it inoperable. -A.