search for: q931_alert

Is there a way to send DTMF's to a channel before the call is answered? For example, send DTMF's to a SIP channel after the 180 Ringing or 183 Session Progress have been received from it, but before the 200 OK, or in the E1 side, after the Q931_ALERTING is received, but before the Q931_CONNECT. If I use Dial(SIP/XXXX,D(my_dtmfs)), it will wait until SIP/XXXX have answered to send the tones, but I need to do it before that. Thanks a lot for your help. -- Attn. Alvaro Palma

...hone quite quickly, everything works. If I route out to a different SIP gateway that sends a 180 Ringing back, then this is OK - the call can ring for a long time and not cut off. After the 180 Ringing message comes back, the incoming E1 gets a state change to Call Received: logger.c: q931.c:2802 q931_alerting: call 16123 on channel 2 enters state 7 (Call Received) However when we only get a 183 back, this doesn't happen and is causing us a problem. I would prefer to solve the problem by changing a configuration option somewhere but I'm running out of ideas. I've had a look in chan_sip....

...100), class = Protocol Error (e.g. unknown message) (6) ] < Cause data 1: 18 (24) < [14 01 01]> < Call State (len= 3) [ Ext: 0 Coding: CCITT (ITU) standard (0) Call state: Call Initiated (1) -- Processing IE 8 (cs0, Cause) -- Processing IE 20 (cs0, Call State) q931.c:2844 q931_alerting: call 99 on channel 1 enters state 7 (Call Received) > Protocol Discriminator: Q.931 (8) len=9 > Call Ref: len= 2 (reference 99/0x63) (Terminator) > Message type: ALERTING (1) > [1e 02 81 88] > Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location...

...00, 18) exited non-zero on 'SIP/197-b6726980' Here's an example of the inbound failure: [Mar 17 17:04:46] VERBOSE[13006] logger.c: -- Executing [846092 at isdn_in:1] Ringing("Zap/20-1", "") in new stack [Mar 17 17:04:46] VERBOSE[13006] logger.c: q931.c:2844 q931_alerting: call 79 on channel 20 enters state 7 (Call Received) [Mar 17 17:04:46] VERBOSE[13006] logger.c: > Protocol Discriminator: Q.931 (8) len=9 [Mar 17 17:04:46] VERBOSE[13006] logger.c: > Call Ref: len= 2 (reference 79/0x4F) (Terminator) [Mar 17 17:04:46] VERBOSE[13006] logger.c: > Mess...

..."s|1") in new stack -- Goto (from-zaptel,s,1) -- Executing [s at from-zaptel:1] NoOp("Zap/45-1", "Entering from-zaptel with DID == xxxxxxx") in new stack -- Executing [s at from-zaptel:2] Ringing("Zap/45-1", "") in new stack q931.c:2599 q931_alerting: call 21 on channel 21 enters state 7 (Call Received) > Protocol Discriminator: Q.931 (8) len=9 > Call Ref: len= 2 (reference 21/0x15) (Terminator) > Message type: ALERTING (1) > [1e 02 81 88] > Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location...

...6] > Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Exclusive Dchan: 0 > ChanSel: As indicated in following octets > Ext: 1 Coding: 0 Number Specified Channel Type: 3 > Ext: 1 Channel: 6 ] q931.c:2838 q931_alerting: call 1 on channel 6 enters state 7 (Call Received) Delaying transmission of 76, window is 7/7 long Starting T_200 timer -- Restarting T200 timer > Protocol Discriminator: Q.931 (8) len=9 > Call Ref: len= 2 (reference 1/0x1) (Terminator) > Message type: ALERTING (1) > [1e 02 81 88]...