SM_PAGE_TITLE

PBXware 2.x
Administration Manual
End User Guide
Install Guide
FAQs
How To Guides
Troubleshooting
  Voicemail
  System Error Messages
  Trunks
  Dial Plans
  Sangoma
  Email
  MOH (Music On Hold)
  ES (Enhanced Services)
  Appliances
  Setup Wizard
  Greetings
  Phones
  Queues
Line Trace using hardware d-channel HDLC (2.3.3 drivers or later)

1. Performing a trace on your sangoma card. (Assuming you have already passed steps 1-3 of Line Debugging)
Type:

#>wanpipemon -i <interface name> -c trd

If you see nothing:
Check if you are using hardware d-channel HDLC. The TDMV_DCHAN parameter should be set to 24 (T1) or 16 (E1).

If you see only outgoing packets:
Contact your telco, your line is not provisioned yet.

If you see incoming and outgoing packets:
Your card is configured properly, start a trace on Asterisk.

2. Performing a trace on Asterisk
In the Asterisk CLI, type:

#>pri show span <span number>


if it says:
pri command not found, then you did not install/configure libpri properly.

if it says:
no pri running on span <span number>
then your zaptel.conf and/or zapata.conf are not configured properly.

if it says:
provisioned, down, active
and you had incoming and outgoing packets when using wanpipemon trace, then your packets are not reaching Asterisk, recompile/reinstall zaptel (make sure zaptel modules are not loaded while doing this).

 


 
End User Pricing
Unlimited stock
Please register

Store
PBXware
gloCOM
Bicom Systems
Software
Press Releases
TELCOware
Telephony Billing
Solutions
Appliances
SERVERware
Support Categories
  Search
  PBXware 3.x
  PBXware 2.x
  SERVERware
  outCALL
  Sound Converter Wizard
  PWmobile
  Appliances
  TELCOware
  Site manager
  gloCOM
  Call Centre Applications
  Customer Help Desk
  Presence Panel
  sipMON
  Troubleshooting
  Need Help With Support
  NEW!!! Bicom Systems documentation on Wiki
Hardware
SIP Security
SIP Monitoring
Softphones
Work Preview
Financing Options
Content
Working at Bicom Systems
Invoicing
Trade Shows
Cool Feature #3
Multi-Site Networking
Case studies
Click here - SALES Click here - SUPPORT
Privacy Policy Copyright Bicom Systems 2003 - 2024


Bicom Systems at Twitter       Bicom Systems at Facebook   Bicom Systems at Flickr   Bicom Systems at Voip-Info   Bicom Systems at FierceVoIP