{"type":"doc","content":[{"type":"extension","attrs":{"layout":"default","extensionType":"com.atlassian.confluence.macro.core","extensionKey":"toc","parameters":{"macroParams":{"minLevel":{"value":"1"},"maxLevel":{"value":"6"},"outline":{"value":"false"},"style":{"value":"none"},"type":{"value":"list"},"printable":{"value":"true"}},"macroMetadata":{"macroId":{"value":"dc24d380-4630-4f0d-96d8-a855279e43f1"},"schemaVersion":{"value":"1"},"title":"Table of Contents"}},"localId":"d3faaf89-108e-4f1f-9308-8534c7ae3158"}},{"type":"paragraph"},{"type":"heading","attrs":{"level":2},"content":[{"text":"Basic Troubleshooting Procedures","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"First, a few facts to know","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"It's not always the carrier's fault. Perform as much testing as you possibly can without having to involve the carrier unless you have very good reason to do so. You will save the customer time and money and help keep them out of a finger-pointing match.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Document everything!! If you perform a loopback test, even if you get no output, just write in the ticket something short and sweet like \"did loop test, came out clean\". If you checked the T1 status before & after an event, log the event & status change.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Be patient with the customer. T1 cards and PRI lines are expensive, and customers will get very angry when they go down during business hours. Remind them that you're on their side and you want to help them get to a resolution as quickly and effectively as possible.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Be systematic in your approach. If it's too hard to do a certain step at the time (such as a loopback test), try everything else that you can do first.","type":"text"}]}]}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"PRI ERROR CODES, CALL SETUP INFORMATION","type":"text"}]},{"type":"paragraph","content":[{"text":"See the following link for details on PRI cause codes, general call setup/teardown, and which side is responsible for certain errors:","type":"text"}]},{"type":"paragraph","content":[{"type":"inlineCard","attrs":{"url":"http://www.freesoft.org/CIE/Topics/126.htm"}},{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":"Brian Weber helpfully internalized the contents of that link should it ever go offline:","type":"text"}]},{"type":"paragraph","content":[{"text":"PRI Error Codes and Call Setup Information","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangomakb.atlassian.net/wiki/spaces/Fonality/pages/203554897/PRI+Error+Codes?search_id=68f10b58-5c37-4b7f-bec7-ba5ae615d484"}}]}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"T1 Circuits are very linear - start with one end","type":"text"}]},{"type":"paragraph","content":[{"text":"Always start your observations at one end and work your way outward. If you work from one end outward, you can easily isolate the source of an issue with a T1 card very quickly. Here's the best method to follow for troubleshooting:","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"PBXtra Core Application - basic","type":"text"}]},{"type":"paragraph","content":[{"text":"If it's a new setup, there are almost always going to be some quirks to iron out. Placing test calls in and out while observing a call trace will tell all. On the asterisk CLI, you should become familiar with ","type":"text"},{"text":"pri debug span 1","type":"text","marks":[{"type":"code"}]},{"text":". The most interesting part of the call is the initial frame that comes in or goes out. Many carriers want every call to have an outbound caller ID number or it won't connect (if you don't know how to set outbound caller ID, ","type":"text"},{"text":"click here","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangoma.atlassian.net/wiki/spaces/Fonality/pages/3811213355/Setting+Outbound+Caller+ID+Name+for+Connect?search_id=5190093b-7132-4d74-865b-8150e1716fb3"}}]},{"text":"). Does the outbound dial string (specifically when dialing out over a PRI) look something like this:","type":"text"}]},{"type":"codeBlock","content":[{"text":"Sep 26 16:35:24 VERBOSE[11807] logger.c: -- Called g2/w13105551212","type":"text"}]},{"type":"paragraph","content":[{"text":"if so, remove the \"w\" from globals.conf and link to & ping this QA ticket: ","type":"text"},{"text":"1137070","type":"text","marks":[{"type":"link","attrs":{"href":"http://ticket.fonality.com/Ticket/Display.html?id=1137070"}}]}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"PBXtra Core Application - severe","type":"text"}]},{"type":"paragraph","content":[{"text":"Do you see anything funny in the call trace? Call logs? What do you get from ","type":"text"},{"text":"pri show span X","type":"text","marks":[{"type":"code"}]},{"text":"? A few things you can try looking out for in just the normal trace - copy them into the ticket if you see them:","type":"text"}]},{"type":"codeBlock","content":[{"text":"Sep 26 00:01:19 WARNING[5025] chan_zap.c: No D-channels available! Using Primary channel 24 as D-channel anyway!\n","type":"text"}]},{"type":"codeBlock","content":[{"text":"Nov 23 21:08:45 NOTICE[2054]: PRI got event: No more alarm (5) on Primary D-channel of span 1\n","type":"text"}]},{"type":"codeBlock","content":[{"text":"Sep 26 23:13:52 NOTICE[3081] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1\n","type":"text"}]},{"type":"codeBlock","content":[{"text":"Sep 26 23:13:52 NOTICE[3081] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1\n","type":"text"}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Drivers, hardware, and firmware versions","type":"text"}]},{"type":"paragraph","content":[{"text":"Double-check against the latest and greatest on the ","type":"text"},{"text":"Version Compatibility","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangoma.atlassian.net/wiki/spaces/Fonality/pages/3815309387/Version+Compatibility?search_id=5190093b-7132-4d74-865b-8150e1716fb3"}}]},{"text":" wiki page, as Fonality will produce better software and Sangoma will produce better drivers as time goes on. If the customer is on faulty drivers or firmware, offer to upgrade after hours. Also, check for interrupt conflicts with","type":"text"}]},{"type":"codeBlock","content":[{"text":"cat /proc/interrupts","type":"text"}]},{"type":"codeBlock","content":[{"text":"lspci -vb | grep IRQ -B 3 ; look for the digium or sangoma device and check if it's got the same IRQ as another device","type":"text"}]},{"type":"paragraph","content":[{"text":"Sangoma cards can share the same IRQ with each other, but not with other devices. Troubleshoot accordingly.","type":"text"}]},{"type":"paragraph"},{"type":"heading","attrs":{"level":4},"content":[{"text":"zapata.conf/zaptel.conf","type":"text"}]},{"type":"paragraph","content":[{"text":"Below on this page are details on what these should be. If this is a new line, get a cutover sheet or a carrier confirmation of the ","type":"text"},{"text":"correct settings","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangoma.atlassian.net/wiki/spaces/Fonality/pages/3897065541?search_id=5190093b-7132-4d74-865b-8150e1716fb3"}}]},{"text":". Always do a sanity check here before proceeding.","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"wanpipe settings (wancfg)","type":"text"}]},{"type":"paragraph","content":[{"text":"Timing on a PRI line should be set by the carrier. There are exceptions, in such cases the carrier will let us know. T1 should use clock port 24. During troubleshooting, you may try turning off echo-cancellation. Details on what these settings should be are below on this page. Always do a sanity check here before proceeding. When in doubt, back up the existing /etc/wanpipeX.conf file and recreate using the wancfg utility.","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Hardware - the card itself","type":"text"}]},{"type":"paragraph","content":[{"text":"If everything software-wise is in check, then performing a loopback test is in order. Ping this suggestions ticket ","type":"text"},{"text":"678405","type":"text","marks":[{"type":"link","attrs":{"href":"http://ticket.fonality.com/Ticket/Display.html?id=678405"}}]},{"text":" and follow the instructions on how to do a loopback test here: ","type":"text"},{"text":"How to pattern loopback test a T1","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangoma.atlassian.net/wiki/spaces/Fonality/pages/3814359156/How+to+pattern+loopback+test+a+T1?search_id=5190093b-7132-4d74-865b-8150e1716fb3"}}]},{"text":". You may choose to postpone this test until later, as it can involve a length of downtime for the customer.","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Cabling","type":"text"}]},{"type":"paragraph","content":[{"text":"Your options here are simple: straight-thru or ","type":"text"},{"text":"crossover","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangomakb.atlassian.net/wiki/spaces/Fonality/pages/208633877/T1+Crossover+Cable%2C+Loopback+Plug?search_id=68f10b58-5c37-4b7f-bec7-ba5ae615d484"}}]},{"text":". Swapping cables around is much less effort than a loopback test, so even though it's out of systematic order, it's simple enough to try before doing a loopback test. You could be getting set up for the test while the customer is changing cables around.","type":"text"}]},{"type":"paragraph","content":[{"text":"If the card is a Sangoma card, use the wanpipemon tool to check for Short Circuit alerts. An active Short Circuit alarm means the cabling is incorrect.","type":"text"}]},{"type":"paragraph","content":[{"text":"wanpipemon T1/E1 line alarms - what they mean - Sangoma Support Wiki","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangomakb.atlassian.net/wiki/spaces/TC/pages/53706877?search_id=68f10b58-5c37-4b7f-bec7-ba5ae615d484"}}]}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Carrier","type":"text"}]},{"type":"paragraph","content":[{"text":"Any company that brings in a T1 line is only bound to connect up to the DMARC (point of demarcation - legal limit of carrier responsibility for the line). That could be the smart jack a few feet from the PBXtra, and it could be fourteen floors downstairs in the basement. We can only see up to the card. Carriers may want to do a loop test to the smart jack, but only for a few minutes. Suggest that the best method of testing is overnight with an intense or intrusive pattern. There are many variables along a T1 line, and unless a carrier has solid validation of any points of failure on their part, they will likely point back to us, resulting in more customer frustration. By the time the troubleshooting gets this far, at least we will have cleared every possible point of failure on the PBXtra.","type":"text"}]},{"type":"paragraph","content":[{"text":"With a clear procedure (above) and all the necessary tools (below and linked), you will have no problem coming to a direct and irrefutable resolution on a down PRI line.","type":"text"}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Dropped call error conditions","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Didn't receive frame","type":"text"}]},{"type":"paragraph","content":[{"text":"When you see something like the following:","type":"text"}]},{"type":"codeBlock","content":[{"text":"Oct 18 16:17:03 DEBUG[25099] channel.c: Didn't get a frame from channel: Zap/2-1","type":"text"}]},{"type":"paragraph","content":[{"text":"This indicates that the channel was closed abruptly due to Asterisk not receiving necessary data over the circuit.","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Frame Control","type":"text"}]},{"type":"paragraph","content":[{"text":"If you see something like the following in the Asterisk message log:","type":"text"}]},{"type":"codeBlock","content":[{"text":"Aug 6 14:13:08 DEBUG[22432] channel.c: Got a FRAME_CONTROL (5) frame on channel Zap/1-1","type":"text"}]},{"type":"paragraph","content":[{"text":"This means that the phone system received an indication on the circuit. These messages are somewhat hard to interpret without all the necessary information. Frame control 5? What?","type":"text"}]},{"type":"paragraph","content":[{"text":"These are the different codes you may find associated with ","type":"text"},{"text":"FRAME_CONTROL","type":"text","marks":[{"type":"code"}]}]},{"type":"table","attrs":{"layout":"default","width":760.0,"localId":"246af17a-f86c-4429-91f2-452b65636df2"},"content":[{"type":"tableRow","content":[{"type":"tableHeader","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Code","type":"text"}]}]},{"type":"tableHeader","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Description","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"1","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"The remote end has hung up","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"2","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Local ringing","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"3","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Remote end is ringing","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"4","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Remote end has answered","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"5","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Remote end is busy","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"7","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Line is off-hook","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"8","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Circuit congestion","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"9","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Flash hook","type":"text"}]}]}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Digium Cards","type":"text"}]},{"type":"paragraph","content":[{"text":"Tried all else on a Digium card and nothing's working? Powercycle the server - don't just restart, powercycle it. Still not working? Switch the cards between PCI ports. Especially useful after a power outage or other event.","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Sangoma Cards","type":"text"}]},{"type":"paragraph"},{"type":"heading","attrs":{"level":3},"content":[{"text":"What to look for in logs","type":"text"}]},{"type":"paragraph","content":[{"text":"In /var/log/messages a T1 dropping will look something like this:","type":"text"}]},{"type":"codeBlock","content":[{"text":"Nov 13 23:41:37 pbxtra0000 kernel: wanpipe1: OOF alarm is ON\nNov 13 23:41:37 pbxtra0000 kernel: wanpipe1: RED alarm is OFF\nNov 13 23:41:37 pbxtra0000 kernel: wanpipe1: T1 disconnected!\nNov 13 23:41:37 pbxtra0000 kernel: wanpipe1: AFT communications disabled!\nNov 13 23:41:37 pbxtra0000 kernel: wanpipe1: Starting TDMV 1ms Timer\nNov 13 23:41:48 pbxtra0000 kernel: wanpipe1: T1 connected!\nNov 13 23:41:48 pbxtra0000 kernel: wanpipe1: AFT communications enabled!\nNov 13 23:41:48 pbxtra0000 kernel: wanpipe1: AFT Global TDM Intr\nNov 13 23:41:49 pbxtra0000 kernel: wanpipe1: AIS alarm is OFF\nNov 13 23:41:49 pbxtra0000 kernel: wanpipe1: OOF alarm is OFF\nNov 13 23:41:49 pbxtra0000 kernel: wanpipe1: RED alarm is OFF\n","type":"text"}]},{"type":"paragraph","content":[{"text":"And in /var/log/asterisk/messages you will see something like this:","type":"text"}]},{"type":"codeBlock","content":[{"text":"Nov 13 23:41:37 NOTICE[5471] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 1\nNov 13 23:41:37 WARNING[5471] chan_zap.c: No D-channels available! Using Primary channel 24 as D-channel anyway!\nNov 13 23:41:37 WARNING[5472] chan_zap.c: Detected alarm on channel 1: Red Alarm\nNov 13 23:41:37 WARNING[5472] chan_zap.c: Detected alarm on channel 2: Red Alarm\nNov 13 23:41:37 WARNING[5472] chan_zap.c: Detected alarm on channel 3: Red Alarm\n...\n...\nNov 13 23:41:37 WARNING[5472] chan_zap.c: Detected alarm on channel 22: Red Alarm\nNov 13 23:41:37 WARNING[5472] chan_zap.c: Detected alarm on channel 23: Red Alarm\nNov 13 23:41:42 VERBOSE[5471] logger.c: == Primary D-Channel on span 1 down\nNov 13 23:41:42 WARNING[5471] chan_zap.c: No D-channels available! Using Primary channel 24 as D-channel anyway!\nNov 13 23:41:48 NOTICE[5471] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 1\nNov 13 23:41:48 NOTICE[5472] chan_zap.c: Alarm cleared on channel 1\nNov 13 23:41:48 NOTICE[5472] chan_zap.c: Alarm cleared on channel 2\nNov 13 23:41:48 NOTICE[5472] chan_zap.c: Alarm cleared on channel 3\n...\n...\nNov 13 23:41:48 NOTICE[5472] chan_zap.c: Alarm cleared on channel 22\nNov 13 23:41:48 NOTICE[5472] chan_zap.c: Alarm cleared on channel 23\nNov 13 23:47:19 NOTICE[5471] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 1\n","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"How to configure a Sangoma T1 Card","type":"text"}]},{"type":"paragraph","content":[{"text":"This information has been moved here: ","type":"text"},{"text":"Basic T1 Configuration","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangoma.atlassian.net/wiki/spaces/Fonality/pages/3897065541?search_id=5190093b-7132-4d74-865b-8150e1716fb3"}}]}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"What is installed on a customer's server?","type":"text"}]},{"type":"paragraph","content":[{"text":"To check hardware information use the command:","type":"text"}]},{"type":"codeBlock","content":[{"text":"/usr/sbin/wanrouter hwprobe","type":"text"}]},{"type":"paragraph","content":[{"text":"You can also use the optional \"hwprobe verbose\" argument to see which FXO and FXS modules are installed. Here is sample output:","type":"text"}]},{"type":"codeBlock","content":[{"text":"[root@pbxtra2575 ~]# wanrouter hwprobe\n\n-------------------------------\n| Wanpipe Hardware Probe Info |\n-------------------------------\n1 . AFT-A200-SH : SLOT=9 : BUS=0 : IRQ=121 : CPU=A : PORT=PRI : HWEC=0 : V=10\n2 . AFT-A102-SH : SLOT=11 : BUS=0 : IRQ=129 : CPU=A : PORT=1 : HWEC=64 : V=31\n3 . AFT-A102-SH : SLOT=11 : BUS=0 : IRQ=129 : CPU=A : PORT=2 : HWEC=64 : V=31\n\nCard Cnt: S508=0 S514X=0 S518=0 A101-2=1 A104=0 A300=0 A200=1 A108=0\n","type":"text"}]},{"type":"paragraph","content":[{"text":"What does this all mean? The columns from left to right are: Card type, PCI slot, PCI bus, CPU, PRI Port, Hardware Echo Canellation, and Firmware version.","type":"text"}]},{"type":"paragraph","content":[{"text":"The first card is an A200 (analog) card with Version 10 of the Sangoma firmware and a 0 indicates this card does not have HWEC. Any number other than a 0 indicates the card *does* have hardware echo cancellation.","type":"text"}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"How to check hardware statistics","type":"text"}]},{"type":"paragraph","content":[{"text":"A few good commands to belt out:","type":"text"}]},{"type":"codeBlock","content":[{"text":"[root@pbxtra0000 ~]# wanpipemon -i w1g1 -c Ta\n\n***** w1g1: T1 Alarms (Framer) *****\n\nALOS: OFF | LOS: OFF\nRED: OFF | AIS: OFF\nYEL: OFF | OOF: OFF\n\n***** w1g1: T1 Alarms (LIU) *****\n\nShort Circuit: OFF\nOpen Circuit: OFF\nLoss of Signal: OFF\n\n\n***** w1g1: T1 Performance Monitoring Counters *****\n\nLine Code Violation : 3070\nBit Errors (CRC6/Ft/Fs) : 19\nOut of Frame Errors : 274\n\n\n[root@pbxtra0000 ~]# wanpipemon -i w1g1 -c xru\n\n\n ----------------------------------\n w1g1: ROUTER UP TIME\n ----------------------------------\n\n Router UP Time: 218 hour(s), 37 minute(s), 22 seconds.\n\n\n[root@pbxtra0000 ~]#\n","type":"text"}]},{"type":"paragraph","content":[{"text":"The stats clear out when the wanpipe driver stops (e.g., by performing a ","type":"text"},{"text":"wanrouter stop","type":"text","marks":[{"type":"code"}]},{"text":"). If you check the Router uptime and see lots of errors, then there's a problem. An \"Out Of Frame\" (OOF) or \"Loss Of Service\" (LOS) is, by definition, a dropped T1 line. There's enough error correction on a T1 line where if three frames are lost within a span of five frames, that is considered an OOF.","type":"text"}]},{"type":"paragraph","content":[{"text":"Long story short... OOF's and LOS's are related to errors generated by the card or by the line. If you see this appearing on a system, do a loop test on the card and the line.","type":"text"}]},{"type":"paragraph","content":[{"text":"Important:","type":"text","marks":[{"type":"strong"}]},{"text":" ","type":"text"},{"text":"interpreting what wanpipemon T1/E1 line alarms mean - Sangoma","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangomakb.atlassian.net/wiki/spaces/TC/pages/53706877?search_id=68f10b58-5c37-4b7f-bec7-ba5ae615d484"}}]}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Known Software and Firmware Issues","type":"text"}]},{"type":"paragraph","content":[{"text":"A good firmware choice for A200 analog cards is V. 10.","type":"text"}]},{"type":"orderedList","attrs":{"order":1},"content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Analog Cards","type":"text"}]},{"type":"orderedList","attrs":{"order":1},"content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Firmware Version 6 is bad, can cause dropped calls","type":"text"}]}]}]}]}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"How to run a pattern loopback test on a Digium T1 card","type":"text"}]},{"type":"paragraph","content":[{"text":"To verify that a T1 PCI card is working properly, a loopback test can be run using a hardware loopback plug. If you ned to build a loopback plug, pin 1 connects to pin 4 and pin 2 connects to pin 5. Pins are numbered left to right when the hook is underneath, and the conductors are furthest away from you. Connect the loopback plug, and run the test as described below.","type":"text"}]},{"type":"paragraph","content":[{"text":"To start off, edit /etc/zaptel.conf. Comment out the span information using the ‘#’ character. Enter these two lines:","type":"text"}]},{"type":"codeBlock","content":[{"text":"span=1,0,0,esf,b8zs\n\nclear=1\nclear=2\nclear=3\nclear=4\nclear=5\nclear=6\nclear=7\nclear=8\nclear=9\nclear=10\nclear=11\nclear=12\nclear=13\nclear=14\nclear=15\nclear=16\nclear=17\nclear=18\nclear=19\nclear=20\nclear=21\nclear=22\nclear=23\nclear=24\n","type":"text"}]},{"type":"paragraph","content":[{"text":"Before continuing, take a look at the output of ","type":"text"},{"text":"lsmod","type":"text","marks":[{"type":"code"}]},{"text":". See below:","type":"text"}]},{"type":"codeBlock","content":[{"text":"[root@pbxtra1900 ~]# lsmod\nModule Size Used by\nwct4xxp 251456 96 \nzaptel 194564 293 wct4xxp\ncrc_ccitt 6081 1 zaptel\ntun 12737 3 \nmd5 8001 1 \nipv6 235105 19 \ndm_mod 56773 0 \nhw_random 9301 0 \ntg3 79045 0 \nfloppy 57297 0 \next3 117961 2 \njbd 59353 1 ext3\nraid1 19393 3 \nata_piix 12357 6 \nlibata 43077 1 ata_piix\nsd_mod 20289 8 \nscsi_mod 112136 2 libata,sd_mod\n","type":"text"}]},{"type":"paragraph","content":[{"text":"Looking specifically at the line:","type":"text"}]},{"type":"codeBlock","content":[{"text":"zaptel 194564 293 wct4xxp\n","type":"text"}]},{"type":"paragraph","content":[{"text":"Make a note of the module name in the fourth column, you will need to reload this module later.","type":"text"}]},{"type":"paragraph","content":[{"text":"Now, stop asterisk and astwatch.pl. You should be able to use ","type":"text"},{"text":"/etc/init.d/asterisk stop","type":"text","marks":[{"type":"code"}]},{"text":". Verify that zaptel has unloaded by doing another lsmod. If it hasn't, unload the module you made a note of earlier (wct4xxp in the above example). Reload the zaptel and card driver modules like so:","type":"text"}]},{"type":"codeBlock","content":[{"text":"# modprobe zaptel\n# modprobe wct4xxp # (replace wct4xxp with the module you noted earlier)\n","type":"text"}]},{"type":"paragraph","content":[{"text":"Verify with the customer that a green light shows on the card when the loopback plug is connected. Additionally, run ","type":"text"},{"text":"zttool","type":"text","marks":[{"type":"code"}]},{"text":" and verify that it is n \"OK\" state.","type":"text"}]},{"type":"paragraph","content":[{"text":"Run ","type":"text"},{"text":"/sbin/ztcfg -vvvvvv","type":"text","marks":[{"type":"code"}]},{"text":" and ensure there are no errors, and that all channels are in a cleared state.","type":"text"}]},{"type":"paragraph","content":[{"text":"Now we move on to running the actually loopback test.","type":"text"}]},{"type":"paragraph","content":[{"text":"If the system is running fon-o or greater, do the following:","type":"text"}]},{"type":"codeBlock","content":[{"text":"# nice -n -11 /usr/sbin/patlooptest /dev/zap/1 600\n","type":"text"}]},{"type":"paragraph","content":[{"text":"If the system is not running fon-o, you will need to first download the zaptel source, and build the test suite. Do the following on the server:","type":"text"}]},{"type":"codeBlock","content":[{"text":"# cd /usr/src\n# wget http://downloads.digium.com/pub/zaptel/releases/zaptel-1.2.16.tar.gz\n# tar -zxvf zaptel-1.2.16.tar.gz\n# cd zaptel-1.2.16\n# make tests\n","type":"text"}]},{"type":"paragraph","content":[{"text":"Now you can continue with loopback testing the card. Do the following:","type":"text"}]},{"type":"codeBlock","content":[{"text":"# cd /usr/src/zaptel-1.2.16\n# nice -n -11 ./patlooptest /dev/zap/1 600\n","type":"text"}]},{"type":"paragraph","content":[{"text":"Watch for the message \"going for it\". If you do not see the message, the test is not working. If you do see it, only errors will be displayed after that. The prompt will return when the test is complete. If you do see errors, then we should contact Digium for an RMA on the card.","type":"text"}]},{"type":"paragraph","content":[{"text":"When done, restore the /etc/zaptel.conf to its original configuration, and restart asterisk by doing ","type":"text"},{"text":"/etc/init.d/asterisk start","type":"text","marks":[{"type":"code"}]},{"text":".","type":"text"}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"How to debug a Sangoma T1 card configured for E&M - Wanpipe RBS","type":"text"}]},{"type":"paragraph","content":[{"text":"The wanpipemon utility provides the ability to debug RBS bits. The following command enables/disables WANPIPE RBS debugging and prints all debugging message into the /var/log/messages file. This feature is supported for all Sangoma digital AFT-series cards.","type":"text"}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":"To enable RBS debugging on receiver side (this command will print only changes to the RBS bit settings):","type":"text"}]},{"type":"codeBlock","content":[{"text":" wanpipemon -i -c derr ","type":"text"}]},{"type":"paragraph","content":[{"text":"To disable RBS debugging on receiver side:","type":"text"}]},{"type":"codeBlock","content":[{"text":" wanpipemon -i -c ddrr ","type":"text"}]},{"type":"paragraph","content":[{"text":"To enable RBS debugging on transmit side (this command will print only changes to the RBS bit settings):","type":"text"}]},{"type":"codeBlock","content":[{"text":" wanpipemon -i -c dert ","type":"text"}]},{"type":"paragraph","content":[{"text":"To disable RBS debugging on transmit side:","type":"text"}]},{"type":"codeBlock","content":[{"text":" wanpipemon -i -c ddrt ","type":"text"}]},{"type":"paragraph","content":[{"text":"Read the current RBS status bits from AFT-series cards:","type":"text"}]},{"type":"codeBlock","content":[{"text":" wanpipemon -i -c drr ","type":"text"}]},{"type":"paragraph","content":[{"text":"Read the current RBS status from the Wanpipe driver:","type":"text"}]},{"type":"codeBlock","content":[{"text":" wanpipemon -i -c dpr ","type":"text"}]},{"type":"paragraph","content":[{"text":"In order to verify the RBS operations, you can run ./zttool utility and enable Sangoma RBS debugging at the same time. Zttool shows what zaptel thinks is the RBS setting and the wanpipe utilities show what the sangoma driver thinks is the RBS setting. The two have to match at all times.","type":"text"}]},{"type":"paragraph","content":[{"text":"In one window run:","type":"text"}]},{"type":"codeBlock","content":[{"text":" zttool ","type":"text"}]},{"type":"paragraph","content":[{"text":"In another window run:","type":"text"}]},{"type":"codeBlock","content":[{"text":"tail -f /var/log/messages ","type":"text"}]},{"type":"paragraph","content":[{"text":"Enable RBS debugging as stated above:","type":"text"}]},{"type":"codeBlock","content":[{"text":" wanpipemon -i -c ddrr #Enable rx rbs debugging\n wanpipemon -i -c ddrt #Enable tx rbs debugging\n","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Place a call on Asterisk with reproducible bad behaviour","type":"text"}]}]}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Compare zttool output versus the /var/log/messages","type":"text"}]}]}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"If driver rbs changes are identical to zttool rbs changes problem is with the telco.","type":"text"}]}]}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"If driver rbs changes differ from zttool rbs changes there could be a problem with the drivers.","type":"text"}]}]}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"If zttool output doesn't match wanpipe rbs output please contact Sangoma Support.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"zttool","type":"text"}]},{"type":"paragraph","content":[{"text":"zttool is an application from the Digium suite of TDM card configuration and troubleshooting. ","type":"text"}]},{"type":"paragraph","content":[{"text":"You invoke the application simply by typing ","type":"text"},{"text":"zttool","type":"text","marks":[{"type":"strong"}]},{"text":". With this application, you can view the current trunk status of most PRI/E1 circuits as shown:","type":"text"}]},{"type":"paragraph","content":[{"text":"By selection one of the interfaces marked ","type":"text"},{"text":"RED","type":"text","marks":[{"type":"strong"}]},{"text":" we can learn more information about the circuit:","type":"text"}]},{"type":"paragraph","content":[{"text":"Any of the statistics above may contain information vital to resolving a problem with the carrier or the customer's own equipment. In the image above, the card simply does not have a circuit attached to port 3 of the Sangoma PRI card.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Asterisk PRI Span Debugging","type":"text"}]},{"type":"paragraph","content":[{"text":"Please follow these steps when faced with dead span. Record the stdout to file for each command.","type":"text"}]},{"type":"paragraph","content":[{"text":"Check that wanpipe status is Connected:","type":"text"}]},{"type":"codeBlock","content":[{"text":" wanrouter status ","type":"text"}]},{"type":"paragraph","content":[{"text":"Check the physical T1/E1 Alarms:","type":"text"}]},{"type":"codeBlock","content":[{"text":" wanpipemon -i w1g1 -c Ta ","type":"text"}]},{"type":"paragraph","content":[{"text":"Interpreting the alarms:","type":"text"},{"type":"hardBreak"},{"text":"https://sangomakb.atlassian.net/wiki/spaces/TC/pages/53706877?search_id=68f10b58-5c37-4b7f-bec7-ba5ae615d484","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangomakb.atlassian.net/wiki/spaces/TC/pages/53706877?search_id=68f10b58-5c37-4b7f-bec7-ba5ae615d484"}}]},{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":"Below is a description of each Alarm (excerpt from the Sangoma Wiki URL above)","type":"text","marks":[{"type":"underline"}]}]},{"type":"table","attrs":{"layout":"default","width":760.0,"localId":"d78bafe5-3f96-40bd-a23a-93a68e7c6b1a"},"content":[{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"RED","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":"Indicates the device is in alarm ","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"LOF","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":"(Loss of Framing). Raised after four consecutive frames with FAS error. If RAI and AIS alarms are not indicated, verify that you have selected the proper line framing (i.e T1: ESF, D4, E1:CRC4, NCRC4..etc) ","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"LOS","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":"(Loss Of frame Signal)","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"AIS","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":"(Alarm Indication Signal): typically known as a ","type":"text"},{"text":"BLUE Alarm.","type":"text","marks":[{"type":"em"}]},{"text":" all-ones signal transmission to the receiving equipment (the Sangoma card) to indicate that an upstream repeater (telco equipment) is in alarm, due to upstream transmission fault, either from another repeater or from the telco itself. If the only alarms indicating in the wanpipemon output is AIS:ON, then contact your telco with this information (RAI:ON can also be a possibility in this case as well) ","type":"text"},{"type":"hardBreak"},{"text":"Example call diagram of the scenario: Sangoma card <---------------repeater <--------------Telco","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"RAI","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":"(Remote Alarm Indication): Indicates that the Far end (typically the Telco) is in RED alarm state and sending that message over the line. If the only alarm in your wanpipemon output is ","type":"text"},{"text":"RAI:ON ","type":"text","marks":[{"type":"em"}]},{"text":"then contact your telco with this information.","type":"text"}]},{"type":"paragraph","content":[{"text":"You will also get this alarm, and only this alarm, if your framing is incorrect.This setting can be changed in the wanpipeX.conf file.","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"Short Circuit","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":" the wires in your cable connected to the port are crossed. If you see this alarm, check the pinouts for the cable you are using. You may also be plugging in the wrong form of cable (straight-through, or cross-over) ","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"Open Circuit","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":" No line plugged into the port. Make sure that your connector is plugged in and the wiring is making a good connection. If this alarm is on, you will also Rx Level='-36'->'-44'. ","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"Loss of Signal","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":" Cabling issue. Check the health of the cable plugged into the port, as well as its connection to the port it is plugged into. You will also see the Rx Level either very low, or in a disconnected state: -36 -> -44. It is typical to have this alarm triggers in combination with 'Open Circuit' if there is an issue with the physical connection ","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"YEL","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":"When the equipment enters a Red-Alarm state, it returns a Yellow-Alarm back up the line of the received OOF. A typical scenario would be mis-configuration during the Sangoma card configuration (i.e selected CRC4 vs NCRC4). In this type of scenario also LOF and RED alarms will be triggered.","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"Line Code Violation","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":" This occurs upon a bipolar violation","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"Far End Block Errors","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":"is reported by the upstream end of the PHY (the wire between you and the switch) on the out-of-band management channel. This means the other end of the line received bad data from you. Possible reason are: line noise, corroded wires..etc. Also, check line Framing (E1: CRC4 vs NCRC4)","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"CRC4 Errors","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":" This occurs when the CRC polynomial calculation performed before transmission does not match the CRC calculation done upon reception.","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"FAS Errors","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":" (Frame alignment signal error). One or more incorrect bits in the alignment word","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[182.0]},"content":[{"type":"paragraph","content":[{"text":"Rx Level","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[577.0]},"content":[{"type":"paragraph","content":[{"text":" Signal strength of the connection between the Sangoma card and the other end. Health connection will show -2.5db. If you notice your connection lower (i.e. -10db-->-12db, or -36fb, -44 db) Then check the cable or possibly replace it. If the Rx level is very low, it can trigger Loss of Signal Tx, or even Open Circuit tx.","type":"text"}]}]}]}]},{"type":"paragraph","content":[{"text":"As per: ","type":"text"},{"text":"https://sangomakb.atlassian.net/wiki/spaces/TC/pages/53706877?search_id=68f10b58-5c37-4b7f-bec7-ba5ae615d484","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangomakb.atlassian.net/wiki/spaces/TC/pages/53706877?search_id=68f10b58-5c37-4b7f-bec7-ba5ae615d484"}}]},{"text":" ","type":"text"}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":"Make sure that tx/rx counters are incrementing:","type":"text"}]},{"type":"codeBlock","content":[{"text":" ifconfig -s ","type":"text"}]},{"type":"paragraph","content":[{"text":"Check for any wanpipe errors in messages:","type":"text"}]},{"type":"codeBlock","content":[{"text":" tail -f -n 100 /var/log/messages ","type":"text"}]},{"type":"paragraph","content":[{"text":"Run a dchan trace and check that you are seeing incoming and outgoing traffic:","type":"text"}]},{"type":"codeBlock","content":[{"text":" wanpipemon -i w1g1 -c trd ","type":"text"}]},{"type":"paragraph","content":[{"text":"Check that spans are UP and Active. From asterisk CLI run:","type":"text"}]},{"type":"codeBlock","content":[{"text":" pri show span 1 ","type":"text"}]},{"type":"paragraph"},{"type":"heading","attrs":{"level":2},"content":[{"text":"T1 DTMF Troubleshooting","type":"text"}]},{"type":"paragraph","content":[{"text":"A T1/PRI passes DTMF through the b-channels and can be assessed as inband. This means that sound quality and echo issues can affect the systems ability to pick up on DTMF tones. Below are instructions for inbound DTMF recognition problems on a T1 PRI.","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"NOTE: zapata.conf settings require an PBXtra Core restart to take affect. THIS WILL DROP CALLS.","type":"text"}]}]}]},{"type":"orderedList","attrs":{"order":1},"content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"As with any Zap DTMF recognition problem, you can set relaxdtmf=yes in zapata.conf - this should be done via the web interface in the Options->settings page. Let the customer know you've made this change and also inquire about any quality issues they may be having (step 3 and 4.) TO check and make sure this setting has taken affect properly you can login to the server and run the command","type":"text"}]},{"type":"codeBlock","content":[{"text":"[root@pbxtra ~]# asterisk -rx 'zap show channel 1'","type":"text"}]},{"type":"paragraph","content":[{"text":"Note: Replace \"1\" with a channel from the T1 span you are concerned with (any channel will do.) Look for the string:","type":"text"}]},{"type":"codeBlock","content":[{"text":"Relax DTMF: yes","type":"text"}]},{"type":"paragraph","content":[{"text":"to see if Relax DTMF is set to yes or no. If it is set improperly check zapata.conf to make sure relaxdtmf=yes and run show uptime to see when the last restart was:","type":"text"}]},{"type":"codeBlock","content":[{"text":"[root@pbxtra ~]# asterisk -rx 'show uptime'","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"If the DTMF is still not being picked up increase the rxgain 3dB at a time and place a test call between each.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"If the customer has responded they have residual noise on the line you may need to troubleshoot the noise before you are able to resolve the DTMF issue.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"If the customer has echo you may need to troubleshoot the echo before you are able to resolve the DTMF issue.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"During your correspondence with the customer, request they also contact the carrier to see if they are sending DTMF appropriately. Have the carrier watch as they place an inbound call and send DTMF tones. Make sure the carrier verifies they are sending all the tones correctly. The carrier may also be able to increase the gain for when they are sending DTMF.","type":"text"}]}]}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"T1 Static Troubleshooting","type":"text"}]},{"type":"paragraph","content":[{"text":"Please see ","type":"text"},{"text":"Static - PRI/T1","type":"text","marks":[{"type":"link","attrs":{"href":"https://sangomakb.atlassian.net/wiki/spaces/Fonality/pages/205848687?search_id=68f10b58-5c37-4b7f-bec7-ba5ae615d484"}}]}]},{"type":"paragraph"},{"type":"heading","attrs":{"level":2},"content":[{"text":"General Info","type":"text"}]},{"type":"paragraph","content":[{"text":"Useful stuffs to know: ","type":"text"},{"type":"inlineCard","attrs":{"url":"http://www.techfest.com/networking/wan/t1.htm"}},{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":"^This has explanations of Alarm types.","type":"text"}]},{"type":"paragraph","content":[{"type":"inlineCard","attrs":{"url":"http://en.wikipedia.org/wiki/T-carrier"}},{"text":" ","type":"text"}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"DID with E&M","type":"text"}]},{"type":"paragraph","content":[{"type":"inlineCard","attrs":{"url":"http://www.voip-info.org/wiki/view/Asterisk+tips+did"}},{"text":" ","type":"text"}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"D4/AMI settings","type":"text"}]},{"type":"paragraph","content":[{"text":"How to set up a T1 with D4/AMI","type":"text"}]},{"type":"paragraph"},{"type":"heading","attrs":{"level":2},"content":[{"text":"T1 D channel not coming online","type":"text"}]},{"type":"paragraph","content":[{"text":"If you encounter a T1 circuit that is attached through an AdTran device (for splitting it up for voice/data), you may find that you must not do hardware HDLC on the D channel, or the circuit may not come up correctly. In these cases, ensure that","type":"text"}]},{"type":"codeBlock","content":[{"text":"TDMV_DCHAN = 0","type":"text"}]},{"type":"paragraph","content":[{"text":"is set in ","type":"text"},{"text":"/etc/wanpipe/wanpipeN.conf","type":"text","marks":[{"type":"code"}]},{"text":". This is occasionally necessary on standard T1's connected to a smart jack as well, but is quite rare.","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"E1 Troubleshooting","type":"text"}]},{"type":"paragraph","content":[{"text":"Puttings this info in the T1 page - will promote to unique page if it is warranted","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Basic E1 mechanics","type":"text"}]},{"type":"paragraph","content":[{"text":"E1 pipes have 30 b-channels + 1 d-channel. The d-chan exists on the sixteenth channel.","type":"text"}]},{"type":"paragraph","content":[{"text":"E1 PRI signalling is different from any traditional American T1:","type":"text"}]},{"type":"blockquote","content":[{"type":"paragraph","content":[{"text":"switchtype=euroisdn ; (as opposed to NI2 national) signalling=pri_cpe ; (this does not change) framing/encoding=ccs/hdb3","type":"text"}]},{"type":"paragraph"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"zapata/zaptel","type":"text"}]},{"type":"paragraph","content":[{"text":"Here's zaptel.conf from a Quad E1 (courtesy of ","type":"text"},{"text":"| voip-info","type":"text","marks":[{"type":"link","attrs":{"href":"http://www.voip-info.org/wiki-Asterisk+config+zaptel.conf"}}]},{"text":"):","type":"text"}]},{"type":"codeBlock","content":[{"text":" span=1,1,0,ccs,hdb3,crc4 \n bchan=1-15 \n dchan=16 \n bchan=17-31 \n span=2,1,0,ccs,hdb3,crc4 \n bchan=32-46 \n dchan=47 \n bchan=48-62 \n span=3,1,0,ccs,hdb3,crc4 \n bchan=63-77 \n dchan=78 \n bchan=79-93 \n span=4,1,0,ccs,hdb3,crc4 \n bchan=94-108 \n dchan=109 \n bchan=110-124 \n loadzone=nl \n defaultzone=nl\n","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":"If the PBX is the MASTER timing source on span 1, use span=1,0,0.","type":"text"}]},{"type":"paragraph","content":[{"text":"# span definition format:","type":"text"},{"type":"hardBreak"},{"text":"# span=(spannum),(timing),(LBO),(framing),(coding)","type":"text"}]},{"type":"paragraph","content":[{"text":"# timing= How to synchronise the timing devices.","type":"text"},{"type":"hardBreak"},{"text":"# 0: to not use this span as sync source; Send timing synchronisation to other end.","type":"text"},{"type":"hardBreak"},{"text":"# 1: to use as primary sync source","type":"text"},{"type":"hardBreak"},{"text":"# 2: to set as secondary and so forth","type":"text"}]},{"type":"paragraph","content":[{"text":"If no T1/PRI spans are hooked to a carrier (rare, but it does happen), any span set to use itself as a sync source can bring down the other spans as well.","type":"text"}]}],"version":1}

Browser not supported