search for: cs0

Displaying 20 results from an estimated 141 matches for "cs0".

Did you mean: cs
2005 Dec 21
4
[offtopic] Asterisk <-IP-> Siemens HiPath 4000
Hello! Is it possible to connect Siemens HiPath 4000 to Asterisk? What equipment required on Siemens side? I mean IP not E1. Sorry for asking here. Siemens-related websites use "salesperson language". There is no technical information.
2005 Sep 28
1
Asterisk does not send "Setup acknowledge" on euroISDN E1
...provided number (3) '012607892' ] < [70 08 81 32 37 37 37 37 37 37] < Called Number (len=10) [ Ext: 1 TON: Unknown Number Type (0) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '2677878' ] -- Making new call for cr 73 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 30 (cs0, Progress Indicator) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) -- Executing Macro("Zap/1-1", "dialddi|SIP/3101|3101") in new...
2006 Mar 12
1
interop problem: "Missing handling for mandatory IE 24 (cs0, Channel Identification)"
Hi everybody, I've connected Asterisk 1.2.5 (libpri 1.2.2, zaptel 1.2.4, Linux 2.6.13.2) to an Avaya-Tenovis PBX via a PRI/E1-line. Calls from SIP-phones via * to the PBX work fine. However, incoming calls to * only result in: -- XXX Missing handling for mandatory IE 24 (cs0, Channel Identification) XXX -- which seems to be an * problem, because a Windows-fax-machine works fine on a PRI line with the same configuration. I was able to get it to work somehow by commenting out the following block in libpri/q931.c, line 3194: -- /* JH for (x=0;x<MAX_MAND_IES...
2006 Jan 16
2
Problem with calls starting from a legacy PBX
...tation permitted, user number passed network screening (1) '220' ] < [70 05 80 30 39 38 34] < Called Number (len= 7) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) '0984' ] -- Making new call for cr 19387 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 30 (cs0, Progress Indicator) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) > Protocol Discriminator: Q.931 (8) len=14 > Call Ref: len= 2 (reference 19387/0x4BBB) (Terminator) > Message type: SETUP ACKN...
2014 Apr 29
1
Inbound DAHDI Error
...(2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '<dest_number>' ] PRI Span: 1 -- Making new call for cref 23832 PRI Span: 1 Received message for call 0x7f7a900012f0 on link 0x1a3cf70 TEI/SAPI 0/0 PRI Span: 1 -- Processing Q.931 Call Setup PRI Span: 1 -- Processing IE 4 (cs0, Bearer Capability) PRI Span: 1 -- Processing IE 24 (cs0, Channel ID) PRI Span: 1 -- Processing IE 28 (cs0, Facility) PRI Span: 1 -- Processing IE 108 (cs0, Calling Party Number) PRI Span: 1 -- Processing IE 112 (cs0, Called Party Number) PRI Span: 1 -- Delayed processing IE 28 (cs0, Facility)...
2005 Oct 03
1
Direct Dial In - second try
...ng (33) '' ] < [70 0e a1 30 37 32 30 30 30 33 34 35 36 37 38 39] < Called Number (len=16) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '07xxxxxx6789' ] -- Making new call for cr 1549 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) > Protocol Discriminator: Q.931 (8) len=10 Call Ref: len= 2 (reference > 1549/0x60D) (Terminator) Message type: CALL PROCEED...
2009 Mar 19
1
PRI QSIG Asterisk - Legacy PBX
...81] [Mar 19 08:04:21] ERROR[11756] chan_dahdi.c: !! < Unknown IE 50 (cs5, len = 3) [Mar 19 08:04:21] VERBOSE[11756] logger.c: -- Making new call for cr 20968 [Mar 19 08:04:21] VERBOSE[11756] logger.c: -- Processing Q.931 Call Setup [Mar 19 08:04:21] VERBOSE[11756] logger.c: -- Processing IE 161 (cs0, Sending Complete) [Mar 19 08:04:21] VERBOSE[11756] logger.c: -- Processing IE 4 (cs0, Bearer Capability) [Mar 19 08:04:21] VERBOSE[11756] logger.c: -- Processing IE 24 (cs0, Channel Identification) [Mar 19 08:04:21] VERBOSE[11756] logger.c: -- Processing IE 108 (cs0, Calling Party Number) [Mar 19...
2005 Jun 25
1
isdn channels busy
...an 2 D-Channel 0]< Called Number (len= 9) [ Ext: 1 TON: Unknown Number Type (0) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) 'yyyyyy' ] [Span 2 D-Channel 0]-- Making new call for cr 1 [Span 2 D-Channel 0]-- Processing Q.931 Call Setup [Span 2 D-Channel 0]-- Processing IE 161 (cs0, Sending Complete) [Span 2 D-Channel 0]-- Processing IE 4 (cs0, Bearer Capability) [Span 2 D-Channel 0]-- Processing IE 24 (cs0, Channel Identification) [Span 2 D-Channel 0]-- Processing IE 30 (cs0, Progress Indicator) [Span 2 D-Channel 0]-- Processing IE 108 (cs0, Calling Party Number) [Span 2 D-C...
2006 Jun 22
2
PRI Issue - Calls being rejected with unacceptable channel
...ng (1) '323801XXXX' ] < [70 0b a1 38 30 30 39 37 38 37 32 37 39] < Called Number (len=13) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '800978XXXX' ] -- Making new call for cr 15996 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 30 (cs0, Progress Indicator) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) > Protocol Discriminator: Q.931 (8) len=10 > Call Ref: len= 2 (reference 4876...
2008 Oct 20
2
ISDN PRI Caller ID problem
...lt; [70 08 c1 34 33 39 32 38 34 32] < Called Number (len=10) [ Ext: 1 TON: Subscriber Number (4) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '4392842' ] < [a1] < Sending Complete (len= 1) -- Making new call for cr 5377 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 112 (cs0, Called Party Number) -- Processing IE 161 (cs0, Sending Complete) q931.c:3509 q931_receive: call 5377 on channel 1 enters state 6 (Call Present) Sending Receiver Ready (12) ---------------------------...
2006 Mar 22
3
PRI DMS100 -> Nortel Meridian Option 81
...tion: Presentation permitted, user number not screened (0) '4224' ] < [70 05 e9 34 39 39 31] < Called Number (len= 7) [ Ext: 1 TON: Abbreviated number (6) NPI: Private Numbering Plan (9) '4991' ] -- Making new call for cr 20 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 40 (cs0, Display) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) > Protocol Discriminator: Q.931 (8) len=10 > Call Ref: len= 2 (reference 20/0x14) (Termina...
2010 Jun 09
0
CID name in Facility message for Q.SIG
...1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '208' ] -- Making new call for cref 256 Received message for call 0x2aaad0157d00 on 0x2aaad0045340 TEI/SAPI 0/0, call->pri is 0x2aaad0045340 TEI/SAPI 0/0 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 28 (cs0, Facility) -- Processing IE 30 (cs0, Progress Indicator) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) -- Delayed processing IE 28 (cs0, Facility) ASN.1...
2007 Jan 18
1
Passing video calls / bearer capability thru PRI
...4 34 35] < Called Number (len=10) [ Ext: 1 TON: Subscriber Number (4) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '5556445' ] < [7c 03 88 90 a6] < IE: Low-layer Compatibility (len = 5) -- Making new call for cr 25914 -- Processing Q.931 Call Setup -- Processing IE 161 (cs0, Sending Complete) -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) -- Processing IE 124 (cs0, Low-layer Compatibility) q931.c:3294 q931_receive: call 25914...
2006 Jan 14
1
Problem with just one number!
...tation permitted, user number passed network screening (1) '416' ] < [70 05 80 30 39 38 34] < Called Number (len= 7) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) '0984' ] -- Making new call for cr 18874 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 30 (cs0, Progress Indicator) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) > Protocol Discriminator: Q.931 (8) len=14 > Call Ref: len= 2 (reference 18874/0x49BA) (Terminator) > Message type: SETUP ACKN...
2007 Oct 31
4
PRI over T1 calls dropping, cause 100
I have a T1 link from asterisk 1.2.23 (also tried with 1.4.13) to a Meridian Option 61C. Calls either way drop with error "Channel 0/23, span 1 got hangup, cause 100". Can anyone offer insight into the cause and solution/workaround? (I tried upgrading to Ast 1.4.13, and upgrading matching zaptel & libpri, put the problem is identical). For testing, I tried a call from the
2006 Apr 08
1
ANI on a PRI
...rovided number (35) '' ] < [70 0b a1 38 30 30 35 36 34 30 38 31 39] < Called Number (len=13) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '8005640819' ] -- Making new call for cr 16 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) > Protocol Discriminator: Q.931 (8) len=11 > Call Ref: len= 2 (reference 16/0x10) (Terminator) > Message type: CALL PRO...
2005 Sep 22
0
priindication passthru TE410P EuroISDN?
...;01722270201' ] < [70 0e c1 30 34 31 30 39 30 30 30 30 30 30 30 37] < Called Number (len=16) [ Ext: 1 TON: Subscriber Number (4) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '0410900000007' ] -- Making new call for cr 31 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) > Protocol Discriminator: Q.931 (8) len=14 > Call Ref: len= 2 (reference 32799/0x801F) (Terminator) > Message type: SETUP...
2007 Jan 23
2
No D-channels available! Using Primary channel 16 as D-channel anyway!
...18 03 a9 83 81] < 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 (cs0, Channel Identification) -- Zap/1-1 is proceeding passing it to Zap/52-1 < Protocol Discriminator: Q.931 (8) len=17 < Call Ref: len= 2 (reference 3/0x3) (Terminator) < Message type: PROGRESS (3) < [08 02 82 81] < Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0...
2004 Sep 05
0
DTMF with HFC-S, not supported yet?
...05 81 39 39 39 39] < Called Number (len= 7) [ Ext: 1 TON: Unknown Number Type (0) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '9999' ] < [7d 02 91 81] < IE: High-layer Compatibility (len = 4) -- Making new call for cr 1 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) -- Processing IE 125 (cs0, High-layer Compatibility) > Protocol Discriminator: Q.931 (8) len=11 > Call Ref: len= 1 (reference 129/0x81) (Terminator) > Message type: SETU...
2007 Jun 08
1
Not getting CID Name from PRI
...one is ringing. Here is the relevant info from my PRI debug output. Line 4 is a NoOp showing me trying to echo Name and Number. Line 6 dials the extension, and you can see callerid name get presented on line 29. Again, there is a Wait(4) before the NoOp on line 3. 1 -- Processing IE 30 (cs0, Progress Indicator) 2 -- Processing IE 108 (cs0, Calling Party Number) 3 -- Processing IE 112 (cs0, Called Party Number) 4 -- Executing NoOp("Zap/1-1", "Name: Num: 9515551212") in new stack 5 -- Executing Macro("Zap/1-1", "stdext...