asterisk users - Sep 2004 - QSIG against a Nortel/Meridian PBX

[Reposting, as was bounced for non-member, sorry if this is a dupe]

Arrangement:

{ PSTN }--E1--[PBX]--E1--[*]--LAN--[SIP phones]
                \__[PBX system phones]

Normal calls between PBX system phones and SIP phones work, in both
directions. The call logs look like (ignore the no answer, it did ring):

"","7436","7902","e1-in","""^B^B^A""
<7436>","Zap/7-1","SIP/7902-5fb7",
"Dial","SIP/7902|20|t","2004-09-08 07:40:07",,
"2004-09-08 07:40:08",1,0,"NO
ANSWER","DOCUMENTATION"

There's a odd bit of data in the name portion of the callerid. I believe
that's being provided over QSIG from the PBX (and the people who
maintain the PBX confirmed QSIG is being sent..)

If a forced redirection is set on the PBX to a SIP extension, the PBX
sends quite a long QSIG message, and we end up with this in the call
logs (phone never rings):

"","","7902","e1-in","""^B^B^G^A^B^A^U0U^B^A^A
^A^A<80>^A^A<A1>^M<A0>^K<A5>    
^A^D^R^D7441<A2>^M<A0>^K<A5>    
^A^D^R^D7441<A3>^N<80>^LAaron Krivan<A4>^N<80>^LAaron
Kriv",
"Zap/31-1","SIP/7902-f8de","Dial","SIP/7902|20|t",
"2004-09-08 12:00:02",,"2004-09-08 12:00:14",12,0,
"NO ANSWER","DOCUMENTATION"

It passes all this over SIP to the phone, but the phone is dumb to it.
The From field contains that name string as it is above (as binary,
instead of ^A etc..), but does not contain a <number> section.

I had thought to just use SetCallerID to supress the name portion, but
there's no number portion in ${CALLERNUM}. It's like the name part is so
long it's overflowing the buffer for the caller id. 

Has anyone else successfully got such an arrangement to work, or is
there any plans to make the QSIG messages more parsable (maybe exposed
as variables in the dialplan)? Or at least not have the name overflow
the number? :)

Thanks.

-- 
David Zanetti <david.zanetti@catalyst.net.nz>
Team Leader, Systems Administration
+64-4-8032233 +64-21-402260
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20040907/9e8770ae/attachment.pgp

> Has anyone else successfully got such an arrangement to work, or is
> there any plans to make the QSIG messages more parsable (maybe exposed
> as variables in the dialplan)? Or at least not have the name overflow
> the number? :)
QSIG passes callername and other variables by a mechanism that asterisk
cannot interpret at the moment.  It sends them either in a information
element in the setup message for the call or in an additional facility
message after the fact.  Right now asterisk cannot interpret those facility
messages to get the data out of them, so that's probably the reason why
you are getting garbled data.

If anyone has any info on interpreting the FACILTIY message/IE we could
probably get something put together to interpret it.

Matthew Fredrickson