[Asterisk-Users] Weirdness with CALLERID / CALLERIDNAME from incoming PRI

[Adams, Gavin]

> -----Original Message-----
> From: Joe Kellman [mailto:jkellman at chutneytech.com]
> 
> i am not sure if somebody asked this question in relation to your
problem,
> what do you get when you do a pri debug span X.  i know with some
> providers
> (i am using xo) the messages are transmitted as a facility message
that
> doesn't get picked by * too well...jak

Hi Joe,

Thanks for the reply. Yup, sure enough it appears the calling party name
is in the facility message. I get the following, where the 'ATLANTA' and
'GA' sections are the calling party name.

< Protocol Discriminator: Q.931 (8)  len=32
< Call Ref: len= 2 (reference 527/0x20F) (Originator)
< Message type: FACILITY (98)
< Facility (len=25) [ < Facility (len=25) [ 0x9f, 0x8b, 0x01, 0x00,
0xa1, 0x13, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0b, 'ATLANTA',
0x2c, 0x20, 'GA'< Facility (len=25) [ 0x9f, 0x8b, 0x01, 0x00, 0xa1,
0x13, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0b, 'ATLANTA', 0x2c,
0x20, 'GA' ]
-- Processing IE 28 (Facility)

I don't have a good understanding for the Q.931 signaling process, but
is it possible the call is being presented and handled by the extension
logic prior the facility message coming through? Or is this just the way
the pri debug span X output is given?

I guess the next question is, are there any commands that could map the
facility message to the calling party name before sending the call to
the extension?

Thanks for the pointer, one step closer!

Regards,

--- Gavin