Page Contents

Zaptel PRI cards (T100P, E100P, T400P, TE405P, TE410P) can be configured for data (HDLC "family") communication (WAN router), as well as hybrid configurating where some T1/E1 timeslots will be used for data and others for voice communication.

This page is designed to help all people to share experience.

You should use the channel keyword nethdlc in zaptel.conf. After running ztcfg, a new network interface will be created. sethdlc (or rather: sethdlc-new) will allow you to control it.

October 6, 2004

I have HDLC/Zaptel working on a Nuvox data/voice PRI with a T100P on Slackware 10using the 2.4.26 kernel. I believe my configuration is different enough from the aboveinstructions to warrant this addition to the Wiki.

Like above, these settings are required in your kernel compilation.CONFIG_WAN=yCONFIG_HDLC=yCONFIG_HDLC_RAW=yCONFIG_HDLC_RAW_ETH=yCONFIG_HDLC_CISCO=y

I used zaptel version 1.0.0, and uncommented these sections in zconfig.hafter recompiling the kernel:

if defined(CONFIG_HDLC) || defined(CONFIG_HDLC_MODULE)

/* #define CONFIG_ZAPATA_NET */to

if defined(CONFIG_HDLC) || defined(CONFIG_HDLC_MODULE)

define CONFIG_ZAPATA_NET

/* #define CONFIG_ZAPATA_NET */to

define CONFIG_ZAPATA_NET

/* #define CONFIG_ZAPATA_PPP */to

define CONFIG_ZAPATA_PPP

/* #define CONFIG_ZAPTEL_WATCHDOG */to

define CONFIG_ZAPTEL_WATCHDOG

edit your zapata.conf file, and be sure youinclude nethdlc=(dso data channels).Here's mine for an example, which isconfigured for a T100P & TDM400P with a single FXS module.

I placed these commands in rc.local (don't forget to add the paths)and set:GATEWAY=""in rc.inet1.conf if you are using slackware like myself.

Not sure if this is the right or best way to do this, but it worked great for me.Your milage may vary.

=========

Nov. 2, 2005

Additional settings example using kernel 2.4.28

This worked with a cisco router connected to the T1(PRI) from the provider. Even though their router was a cisco we could not getit to work using cisco hdlc. We were told by the provider that the system was a cisco un-numbered interface. The followingsettings worked great however.

See also

Page Contents

Zaptel PRI cards (T100P, E100P, T400P, TE405P, TE410P) can be configured for data (HDLC "family") communication (WAN router), as well as hybrid configurating where some T1/E1 timeslots will be used for data and others for voice communication.

This page is designed to help all people to share experience.

You should use the channel keyword nethdlc in zaptel.conf. After running ztcfg, a new network interface will be created. sethdlc (or rather: sethdlc-new) will allow you to control it.

October 6, 2004

I have HDLC/Zaptel working on a Nuvox data/voice PRI with a T100P on Slackware 10using the 2.4.26 kernel. I believe my configuration is different enough from the aboveinstructions to warrant this addition to the Wiki.

Like above, these settings are required in your kernel compilation.CONFIG_WAN=yCONFIG_HDLC=yCONFIG_HDLC_RAW=yCONFIG_HDLC_RAW_ETH=yCONFIG_HDLC_CISCO=y

I used zaptel version 1.0.0, and uncommented these sections in zconfig.hafter recompiling the kernel:

if defined(CONFIG_HDLC) || defined(CONFIG_HDLC_MODULE)

/* #define CONFIG_ZAPATA_NET */to

if defined(CONFIG_HDLC) || defined(CONFIG_HDLC_MODULE)

define CONFIG_ZAPATA_NET

/* #define CONFIG_ZAPATA_NET */to

define CONFIG_ZAPATA_NET

/* #define CONFIG_ZAPATA_PPP */to

define CONFIG_ZAPATA_PPP

/* #define CONFIG_ZAPTEL_WATCHDOG */to

define CONFIG_ZAPTEL_WATCHDOG

edit your zapata.conf file, and be sure youinclude nethdlc=(dso data channels).Here's mine for an example, which isconfigured for a T100P & TDM400P with a single FXS module.

I placed these commands in rc.local (don't forget to add the paths)and set:GATEWAY=""in rc.inet1.conf if you are using slackware like myself.

Not sure if this is the right or best way to do this, but it worked great for me.Your milage may vary.

=========

Nov. 2, 2005

Additional settings example using kernel 2.4.28

This worked with a cisco router connected to the T1(PRI) from the provider. Even though their router was a cisco we could not getit to work using cisco hdlc. We were told by the provider that the system was a cisco un-numbered interface. The followingsettings worked great however.