Peter Svensson wrote:
What is c-ourcallstate set to at this time? Can you provide a debug log
(pri intense debug span xxx) of the call?
it's Q931_CALL_STATE_ACTIVE - that's what it should be after a call is
established.
Asterisk only expects INFORMATION elements when expecting overlap digits
On Thu, 17 Feb 2005, Deti Fliegl wrote:
Peter Svensson wrote:
Asterisk only expects INFORMATION elements when expecting overlap digits
(i.e. before CONNECT, PROCEEDING etc). After that it expects digits as
inline dtmf.
Yep - but ISDN phones normally do not encode inline DTMF. Therefor
Peter Svensson wrote:
Ok, then INFORMATION with keypad IE needs to be handled differently from
IE called number.
This is what it looks like with pri intense debug enabled:
Informational frame:
SAPI: 00 C/R: 1 EA: 0
TEI: 000EA: 1
N(S): 116 0: 0
N(R): 126 P: 0
8 bytes of data
--
On Thu, 17 Feb 2005, Deti Fliegl wrote:
Protocol Discriminator: Q.931 (8) len=8
Call Ref: len= 2 (reference 7/0x7) (Originator)
Message type: INFORMATION (123)
[2c 01 31]
Keypad Facility (len= 3) [ 1 ]
Feb 16 11:42:25 VERBOSE[2975]:
[ 02 01 e8 fc 08 02 00 07 7b 2c 01 31 ]
see
Hi there,
I tried to use Voicemail from a PRI interface but it didn't work because
pressing a key on the ISDN phone just caused Q931_IE_KEYPAD_FACILITY
messages which are normally handled by a bri-stuffed libpri.
Unfortunately a wrong if condition stops keypad messages from being
passed to
On Wed, 16 Feb 2005, Deti Fliegl wrote:
I tried to use Voicemail from a PRI interface but it didn't work because
pressing a key on the ISDN phone just caused Q931_IE_KEYPAD_FACILITY
messages which are normally handled by a bri-stuffed libpri.
Unfortunately a wrong if condition stops
