[asterisk-users] T1, Rhino, & Nortel

[Gleim, Jason]

Steve,

Thanks for your input but please allow me to clarify that I'm not a
noob. I'm perfectly capable of looking up the definition of a protocol
error just the same as you... And I had already done that before I
posted the question. I think you misunderstood what I posted. The
switchtype in the Nortel is set to DMS100 and it is successfully
communicating with a real DMS100. Why would I turn around and change the
switchtype in Asterisk to National to see if it's going to work? I
already know it won't work unless I change the IFC type for my DCH in
the Option 11 as well. And that, if you have any Nortel Meridian
experience, is not a job for the faint of heart... especially on a live
system.

I'm also not convinced that setting localdialplan to unknown or
pridialplan to unknown is going to do much of anything either. The debug
trace showed the call made it all the way to CONNECT before the Option
11 dumped it. Dialplan format is dealt with much earlier during call
setup. The Option 11, in fact, would have rejected the call with a
numbering plan error if the dialplan format was wrong. However, I will
try these two settings because I'm not using them now and it won't hurt
to give them a shot.

I suspect though that the real reason is something is not implemented
correctly in libpri. Things go downhill in the call trace when the
Option 11 responds with a RELEASE message and a cause code of 100. That
code is 'Invalid Information Element' which usually means something is
not quite right with the last message. In this case, the previous packet
is the CONNECT message. This would lead me to believe libpri may not be
implementing everything the Option 11 is looking for from a DMS100.

There is a bug (see http://bugs.digium.com/view.php?id=9058) involving
something similar and I wonder if this isn't along the same lines. 

I originally asked if anyone else had come across this and if so, what
did they do to solve it. I'll ask it again and qualify that I would like
to get input from someone that has specific experience with this. I'm
trying to sort out if this is possibly a bug that needs reported or
something I've got configured wrong. If anyone has successfully
connected an Option 11 with Asterisk using a switchtype of DMS100,
please e-mail me off-list. I would like to compare notes.

Thanks!
Jason



>CLASS 1.6 (Protocol error; e.g. unknown message)Cause No. 96 -
>Mandatory Info missingThis cause indicates that the equipment sending
>this cause has received amessage which is missing an information
>element which must be present in themessage before that message can be
>processed.
>
>This is your first clue.  Don't mess with the part that works.  Start
>by trying different values on span 3 (or is it 2? you call it both).
>I would try switchtype=national first.  I would also try things like
>localdialplan=unknown pridialplan=unknown and other signalling related
>settings and flip the possible settings around until it works.  Look
>at the example files on your box for ideas.
>
>I bet you will have a "holy cow!  It worked" moment and nobody will
>have to spoon feed you the answer.
>
>Thanks,
>Steve Totaro
>
>_______________________________________________
>-- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
>asterisk-users mailing list
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users