RE: [Asterisk-Users] Panasonic TDA200 E1 - E100P negotiation issues
Is the E1 card an isdn card or something else? There are a several signalling systems that can run over an E1. When running cas you do not have a D channel for the signalling. Instead each voice channel has a few dedicated bits in channel 16 (hence Channel Associated Signalling). This is used for EM, loopstart etc and is incompatible with the ISDN signalling that you tried. You need to tell us more about what card you have in the Panasonic PBX. Ok not exactly sure what info to give you, I ordered an E1 card from panasonic for the phone system and its what they sent me, it has an RJ45 interface and coax TX/RX connectors as well, I also have full access with the techs version of the panasonic control/programming software and know my way around if there is something specific I could get out of the settings on the card for you to allow you to know which card it is. I would assume (I know that's bad) that it is an ISDN card as it should be the card that is used to connect to a telco directly. I know that it is using hdb3, it only shows up with 30 channels on the card in the E1 slot setup. What happens to channel 16 which is usually set as the d-channel, or should I be including channel 16 in with the rest and not using port 31 in the channels? James ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Panasonic TDA200 E1 - E100P negotiation issues
On Fri, 11 Mar 2005, James Bean wrote: You need to tell us more about what card you have in the Panasonic PBX. Ok not exactly sure what info to give you, I ordered an E1 card from panasonic for the phone system and its what they sent me, it has an RJ45 interface and coax TX/RX connectors as well, I also have full access with the techs version of the panasonic control/programming software and know my way around if there is something specific I could get out of the settings on the card for you to allow you to know which card it is. I would assume (I know that's bad) that it is an ISDN card as it should be the card that is used to connect to a telco directly. Well, you can connect to the telco using non-isdn signalling as well. In Europe isdn is by far the most common signalling form used on an E1. Can you find the model number for the E1 card? I know that it is using hdb3, it only shows up with 30 channels on the card in the E1 slot setup. An E1 always has 30 voice channels, one signalling channel (running CAS or CCS) and one timing channel. (Well, you _can_ run voice over channel 16, but then you would not have any signalling as RBS is not normally used on an E1). What happens to channel 16 which is usually set as the d-channel, or should I be including channel 16 in with the rest and not using port 31 in the channels? Channles 16 on an E1 is always reserved for signalling. There are several signalling mechanisms which can be transported in that slot. Isdn uses CCS, but there are other non-isdn signalling systems that instead use a few bits per channel each frame, CAS. Can you send me the result of a pri intense debug span X from asterisk? Have asterisk set to be the clock source (the timing set to 0 in the span line) and configured as pri_net. Peter ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Panasonic TDA200 E1 - E100P negotiation issues
Well, you can connect to the telco using non-isdn signalling as well. In Europe isdn is by far the most common signalling form used on an E1. Can you find the model number for the E1 card? An E1 always has 30 voice channels, one signalling channel (running CAS or CCS) and one timing channel. (Well, you _can_ run voice over channel 16, but then you would not have any signalling as RBS is not normally used on an E1). Channles 16 on an E1 is always reserved for signalling. There are several signalling mechanisms which can be transported in that slot. Isdn uses CCS, but there are other non-isdn signalling systems that instead use a few bits per channel each frame, CAS. Can you send me the result of a pri intense debug span X from asterisk? Have asterisk set to be the clock source (the timing set to 0 in the span line) and configured as pri_net. Attached is the pri dump from asterisk just bringing the E1 into service with the settings you suggested. James *CLI pri intense debug span 1 Enabled EXTENSIVE debugging on span 1 *CLI Sending Set Asynchronous Balanced Mode Extended [ 00 01 7f ] Unnumbered frame: SAPI: 00 C/R: 0 EA: 0 TEI: 000EA: 1 M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] 0 bytes of data Sending Set Asynchronous Balanced Mode Extended [ 00 01 7f ] Unnumbered frame: SAPI: 00 C/R: 0 EA: 0 TEI: 000EA: 1 M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] 0 bytes of data Sending Set Asynchronous Balanced Mode Extended [ 00 01 7f ] Unnumbered frame: SAPI: 00 C/R: 0 EA: 0 TEI: 000EA: 1 M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] 0 bytes of data Sending Set Asynchronous Balanced Mode Extended [ 00 01 7f ] Unnumbered frame: SAPI: 00 C/R: 0 EA: 0 TEI: 000EA: 1 M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] 0 bytes of data Sending Set Asynchronous Balanced Mode Extended [ 00 01 7f ] Unnumbered frame: SAPI: 00 C/R: 0 EA: 0 TEI: 000EA: 1 M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] 0 bytes of data Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 1: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 1 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 2: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 2 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 3: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 3 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 4: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 4 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 5: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 5 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 6: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 6 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 7: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 7 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 8: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 8 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 9: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 9 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 10: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 10 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 11: Red Alarm Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 11 Mar 11 19:50:19 NOTICE[7051]: chan_zap.c:7395 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 1 Mar 11 19:50:19 WARNING[7051]: chan_zap.c:1931 pri_find_dchan: No D-channels available! Using Primary on channel anyway 16! Mar 11 19:50:19 WARNING[7051]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 12: Red Alarm Mar 11 19:50:19 WARNING[7051]:
RE: [Asterisk-Users] Panasonic TDA200 E1 - E100P negotiation issues
Whooppss had pri_cpe set, redid the debug as attached. They seem the same but just in case. James Enabled EXTENSIVE debugging on span 1 *CLI Sending Set Asynchronous Balanced Mode Extended [ 02 01 7f ] Unnumbered frame: SAPI: 00 C/R: 1 EA: 0 TEI: 000EA: 1 M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] 0 bytes of data Sending Set Asynchronous Balanced Mode Extended [ 02 01 7f ] Unnumbered frame: SAPI: 00 C/R: 1 EA: 0 TEI: 000EA: 1 M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] 0 bytes of data Sending Set Asynchronous Balanced Mode Extended [ 02 01 7f ] Unnumbered frame: SAPI: 00 C/R: 1 EA: 0 TEI: 000EA: 1 M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] 0 bytes of data Sending Set Asynchronous Balanced Mode Extended [ 02 01 7f ] Unnumbered frame: SAPI: 00 C/R: 1 EA: 0 TEI: 000EA: 1 M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] 0 bytes of data Sending Set Asynchronous Balanced Mode Extended [ 02 01 7f ] Unnumbered frame: SAPI: 00 C/R: 1 EA: 0 TEI: 000EA: 1 M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] 0 bytes of data Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 1: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 1 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 2: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 2 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 3: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 3 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 4: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 4 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 5: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 5 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 6: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 6 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 7: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 7 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 8: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 8 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 9: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 9 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 10: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 10 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 11: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 11 Mar 11 19:58:13 NOTICE[7151]: chan_zap.c:7395 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 1 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1931 pri_find_dchan: No D-channels available! Using Primary on channel anyway 16! Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 12: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 12 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 13: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 13 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 14: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 14 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 15: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254 zt_disable_ec: Unable to disable echo cancellation on channel 15 Mar 11 19:58:13 WARNING[7151]: chan_zap.c:5653 handle_init_event: Detected alarm on channel 17: Red Alarm Mar 11 19:58:13 WARNING[7151]: chan_zap.c:1254
RE: [Asterisk-Users] Panasonic TDA200 E1 - E100P negotiation issues
On Fri, 11 Mar 2005, James Bean wrote: Whooppss had pri_cpe set, redid the debug as attached. They seem the same but just in case. Asterisk does not see anything coming in on the D channel. What does zttool say about the state of the link? As I said before, if the card is an isdn card you need to use ccs signalling. Cas signalling is unusual, but possible, over an E1. Can you find out the model number of the E1 card in the Panasonic pbx? Peter ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Panasonic TDA200 E1 - E100P negotiation issues
Asterisk does not see anything coming in on the D channel. What does zttool say about the state of the link? zttool shows the card exists, the following information shows when select the card Main Screen - Alarms Ok / Span Digium Wildcard E100P E1/PRA Card 0 Current Alarms: No Alarms Sync Source: Internally clocked IRQ Misses: 48 Bipolar Viol: 0 Tx/Rx Levels: 0/0 Total/Conf/ActL 31/31/0 Then a whole lot of numbers in a row with columns of TxA TxB etc with dashes covering all lines. [EMAIL PROTECTED] root]# cat /proc/interrupts CPU0 0: 101341836 XT-PIC timer 1:526 XT-PIC i8042 2: 0 XT-PIC cascade 3: 15425613 XT-PIC eth0 5: 101742446 XT-PIC t1xxp 7: 18724522 XT-PIC eth1 8: 1 XT-PIC rtc 9: 0 XT-PIC acpi 11: 393426 XT-PIC 3ware Storage Controller, ohci1394 12: 85 XT-PIC i8042 NMI: 0 ERR: 0 As I said before, if the card is an isdn card you need to use ccs signalling. Cas signalling is unusual, but possible, over an E1. Can you find out the model number of the E1 card in the Panasonic pbx? When I use cas signalling on the * server the E1 card on the TDA shows a green sync light, when on ccs it show sync error. Ok there was a long string of numbers on the E1 card starting right to left at the top of the card E1 PRI23 PRI30 PSUP1431ZB KX-TDA0187/0188/0290/0290CE I believe the model number is a KX-TDA0290 or the 0290CE, as the 0187 is a T1 Trunk card but we don't have T1 in australia it is E1. I hope this is the answer to your questions sir, or did I create more? James ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Panasonic TDA200 E1 - E100P negotiation issues
On Fri, 11 Mar 2005, James Bean wrote: Hi, I hope someone can help me with this Asterisk 1.0.6 Zaptel 1.0.6 Libpri 1.0.6, 1 Digium E100P card installed Panasonic TDA200 firmware v2.0.6 E1 Card Firmware 1.0.2 System is located in Australia, so as technologies go, I believe it is twist on the euro standard for the E1 signalling. Is the E1 card an isdn card or something else? There are a several signalling systems that can run over an E1. If I use span=1,x,0,ccs,hdb3 where x =0,1,2 the sync light appears on the E100P card but when i bring the TDA E1 card in service i get a sync error and a crap load of Red Alerts for every channel and a Mar 11 14:40:35 NOTICE[3910]: chan_zap.c:7395 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 1 Mar 11 14:40:35 WARNING[3910]: chan_zap.c:1931 pri_find_dchan: No D-channels available! Using Primary on channel anyway 16! At this stage I was pulling hair thinking what the but since murphy's law rules supreme i started thinking about other signalling types, esf,b8zs is definitely not going to work so I tried. span=1,x,0,cas,hdb3 and suddenly i get across the board green lights on the E100P and the TDA E1, but once the sync actually completes I then get the same red alert's on every channel including the above d-channel error. When running cas you do not have a D channel for the signalling. Instead each voice channel has a few dedicated bits in channel 16 (hence Channel Associated Signalling). This is used for EM, loopstart etc and is incompatible with the ISDN signalling that you tried. cas,hdb3 seems to be the way to go, although not generally used by what i have read on the net, but after sync it bombs out in asterisk, does anyone have any clues of what I could try next. I tried all instances swapping between pri_net and pri_cpe in the zapata.conf You need to tell us more about what card you have in the Panasonic PBX. Peter ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
