(Please forward this to Martin Pycko in Digium) Martin, this is all about mail that I have sent to you regarding data call setup.
Hi Thomas, Thanks for your hint. I have tried it but it doesn't work. Here are few lines from my config... ; ;RAS ; exten => 290,1,GotoIf,"$[${CALLTYPE} = DIGITAL]?50:100" exten => 290,50,Dial(Zap/g2d/${EXTEN}) exten => 290,100,Dial(Zap/g2/${EXTEN}) I have captured some PRI messages from both interfaces. Here they are, first two are captured in the moment of setup, an down are two captured in the moment of release. If I am right, I think the outgoing call to PBX is voice instead of data. INCOMING E1 PORT FROM PSTN IN THE MOMENT OF ISDN DATA CALL SETUP < Protocol Discriminator: Q.931 (8) len=32 < Call Ref: len= 2 (reference 94/0x5E) (Originator) < Message type: SETUP (5) < Sending Complete (len= 4) < Bearer Capability (len= 2) [ Ext: 1 Q.931 Std: 0 Info transfer capability: Unrestricted digital information (8) < Ext: 1 Trans mode/rate: 64kbps, circuit-mode (16) < Ext: 0 User information layer 1: Unknown (24) < Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Preferred Dchan: 0 < ChanSel: Reserved < Ext: 1 Coding: 0 Number Specified Channel Type: 3 < Ext: 1 Channel: 1 ] < Calling Number (len=11) [ Ext: 0 TON: Subscriber Number (4) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) < Presentation: Presentation permitted, user number passed network screening (1) '6658218' ] < Called Number (len= 6) [ Ext: 1 TON: Unknown Number Type (0) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '290' ] -- Making new call for cr 94 -- Processing Q.931 Call Setup -- Processing IE 33 (Sending Complete) -- Processing IE 4 (Bearer Capability) -- Processing IE 24 (Channel Identification) -- Processing IE 108 (Calling Party Number) -- Processing IE 112 (Called Party Number) > Protocol Discriminator: Q.931 (8) len=10 > Call Ref: len= 2 (reference 32862/0x805E) (Terminator) > Message type: CALL PROCEEDING (2) > Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Exclusive Dchan: 0 > ChanSel: Reserved > Ext: 1 Coding: 0 Number Specified Channel Type: 3 > Ext: 1 Channel: 1 ] > Protocol Discriminator: Q.931 (8) len=14 > Call Ref: len= 2 (reference 32862/0x805E) (Terminator) > Message type: ALERTING (1) > Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Exclusive Dchan: 0 > ChanSel: Reserved > Ext: 1 Coding: 0 Number Specified Channel Type: 3 > Ext: 1 Channel: 1 ] > Progress Indicator (len= 2) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1) > Ext: 1 Progress Description: Inband information or appropriate pattern now available. (8) ] > Protocol Discriminator: Q.931 (8) len=14 > Call Ref: len= 2 (reference 32862/0x805E) (Terminator) > Message type: ALERTING (1) > Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Exclusive Dchan: 0 > ChanSel: Reserved > Ext: 1 Coding: 0 Number Specified Channel Type: 3 > Ext: 1 Channel: 1 ] > Progress Indicator (len= 2) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1) > Ext: 1 Progress Description: Inband information or appropriate pattern now available. (8) ] < Protocol Discriminator: Q.931 (8) len=13 < Call Ref: len= 2 (reference 94/0x5E) (Originator) < Message type: STATUS (125) < Cause (len= 3) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Public network serving the local user (2) < Ext: 1 Cause: Message not compatible with call state (101), class = Protocol Error (6) ] < Cause data 0: 01 (1) < Call State (len= 1) [ Ext: 0 Coding: CCITT (ITU) standard (0) Call state: Call Received (7) -- Processing IE 8 (Cause) -- Processing IE 20 (Call State) > Protocol Discriminator: Q.931 (8) len=14 > Call Ref: len= 2 (reference 32862/0x805E) (Terminator) > Message type: CONNECT (7) > Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Exclusive Dchan: 0 > ChanSel: Reserved > Ext: 1 Coding: 0 Number Specified Channel Type: 3 > Ext: 1 Channel: 1 ] > Progress Indicator (len= 2) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1) > Ext: 1 Progress Description: Called equipment is non-ISDN. (2) ] < Protocol Discriminator: Q.931 (8) len=5 < Call Ref: len= 2 (reference 94/0x5E) (Originator) < Message type: CONNECT ACKNOWLEDGE (15) OUTGOING PORT TO PBX IN THE MOMENT OF ISDN DATA CALL SETUP > Protocol Discriminator: Q.931 (8) len=32 > Call Ref: len= 2 (reference 10/0xA) (Originator) > Message type: SETUP (5) > Bearer Capability (len= 3) [ Ext: 1 Q.931 Std: 0 Info transfer capability: Unrestricted digital information (8) > Ext: 1 Trans mode/rate: 64kbps, circuit-mode (16) > Ext: 1 User information layer 1: A-Law (35) > Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Preferred Dchan: 0 > ChanSel: Reserved > Ext: 1 Coding: 0 Number Specified Channel Type: 3 > Ext: 1 Channel: 1 ] > Calling Number (len=11) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) > Presentation: Presentation permitted, user number passed network screening (1) '6658218' ] > Called Number (len= 6) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '290' ] < Protocol Discriminator: Q.931 (8) len=10 < Call Ref: len= 2 (reference 32778/0x800A) (Terminator) < Message type: SETUP ACKNOWLEDGE (13) < Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Exclusive Dchan: 0 < ChanSel: Reserved < Ext: 1 Coding: 0 Number Specified Channel Type: 3 < Ext: 1 Channel: 1 ] -- Processing IE 24 (Channel Identification) < Protocol Discriminator: Q.931 (8) len=5 < Call Ref: len= 2 (reference 32778/0x800A) (Terminator) < Message type: CALL PROCEEDING (2) < Protocol Discriminator: Q.931 (8) len=5 < Call Ref: len= 2 (reference 32778/0x800A) (Terminator) < Message type: ALERTING (1) < Protocol Discriminator: Q.931 (8) len=16 < Call Ref: len= 2 (reference 32778/0x800A) (Terminator) < Message type: CONNECT (7) > Protocol Discriminator: Q.931 (8) len=5 > Call Ref: len= 2 (reference 10/0xA) (Originator) > Message type: CONNECT ACKNOWLEDGE (15) HERE RAS CLIENT STOPS AND WAITS FOR A LONG TIME AND THEN FAILS. IN THAT MOMENT THIS IS CAPTURED: E1 PORT FROM PBX (where RAS is) NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Active, peerstate Connect Request > Protocol Discriminator: Q.931 (8) len=9 > Call Ref: len= 2 (reference 10/0xA) (Originator) > Message type: DISCONNECT (69) > Cause (len= 2) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1) > Ext: 1 Cause: Normal Clearing (16), class = Normal Event (1) ] < Protocol Discriminator: Q.931 (8) len=5 < Call Ref: len= 2 (reference 32778/0x800A) (Terminator) < Message type: RELEASE (77) NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Release Request > Protocol Discriminator: Q.931 (8) len=9 > Call Ref: len= 2 (reference 10/0xA) (Originator) > Message type: RELEASE COMPLETE (90) > Cause (len= 2) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1) > Ext: 1 Cause: Normal Clearing (16), class = Normal Event (1) ] NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null E1 PORT BACK TO PSTN < Protocol Discriminator: Q.931 (8) len=9 < Call Ref: len= 2 (reference 94/0x5E) (Originator) < Message type: DISCONNECT (69) < Cause (len= 2) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: User (0) < Ext: 1 Cause: Normal Clearing (16), class = Normal Event (1) ] -- Processing IE 8 (Cause) NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Disconnect Indication, peerstate Disconnect Request > Protocol Discriminator: Q.931 (8) len=9 > Call Ref: len= 2 (reference 32862/0x805E) (Terminator) > Message type: RELEASE (77) > Cause (len= 2) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1) > Ext: 1 Cause: Normal Clearing (16), class = Normal Event (1) ] < Protocol Discriminator: Q.931 (8) len=5 < Call Ref: len= 2 (reference 94/0x5E) (Originator) < Message type: RELEASE COMPLETE (90) NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Haeger Sent: Thursday, February 05, 2004 10:37 AM To: [EMAIL PROTECTED] Subject: AW: [Asterisk-Users] Data call transfer Hi Tomica, i had the same problem and here is the solution from Maik Schmitt: exten => _X.,1,GotoIf,"$[${CALLTYPE} = DIGITAL]?50:100" exten => _X.,50,Dial(Zap/g3d/${EXTEN}) exten => _X.,100,Dial(Zap/g3/${EXTEN}) But maybe the dataendpoint would never be reached, and so can try out this: go to bugs.digium.com and look at bug number "0000960" at "libpri" project Regards, Thomas. -----Ursprungliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Tomica Crnek Gesendet: Donnerstag, 5. Februar 2004 10:05 An: [EMAIL PROTECTED] Betreff: [Asterisk-Users] Data call transfer Hi everyone I have TE410P with one E1 link connected to telecom PSTN, and another E1 to my internal legacy PBX. On this PBX I have one extension where my RAS server for both ISDN and analogue calls is located. Can anyone tell me what has to be done to transfer voice call from one E1 to another as voice, and if Asterisk detects that the call is a data call to transfer it further as data? Tomica _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users