asterisk users - May 2004 - * as pri_net?

If you have used * to support a pri as pri_net (as opposed to pri_cpe),
either to talk to another * system or a PBX of some sort, I would be very
interested in hearing about your experiences.  Imparticular, I would like
to know that it works before I invest in the extra hardware.

TIA

Bruce Komito
High Sierra Networks, Inc.
www.servers-r-us.com
(775) 284-5800 ext 115

> If you have used * to support a pri as pri_net (as opposed to pri_cpe),
> either to talk to another * system or a PBX of some sort, I would be very
> interested in hearing about your experiences.  Imparticular, I would like
> to know that it works before I invest in the extra hardware.
I too am interested in this -- I would like to use a T100P to talk to our 
Nortel Modular ICS as PRI rather than CAS T1.

Regards,
Andrew

Bruce Komito <brucek@bagel.com> wrote:
> If you have used * to support a pri as pri_net (as opposed to pri_cpe),
> either to talk to another * system or a PBX of some sort, I would be very
> interested in hearing about your experiences.
I've used pri_net on one end to talk between two Asterisk boxes with T100Ps 
and a T1 crossover cable.  It worked exactly as advertised - just make sure 
the span= statements in zaptel.conf are right (one span=1,1,0,esf,b8zs and 
the other span=1,0,0,esf,b8zs).

Mark

I've done this too.   Four E1's on one box, talking to four E1's on
another
asterisk box.  I just use it for load testing new Zap versions.

Note that you need a crossover E1 cable for this.

Cheers
Scott 

Scott M. Stingel
President,
Emerging Voice Technology, Inc.
Palo Alto California & London England
www.evtmedia.com 

-----Original Message-----
From: asterisk-users-admin@lists.digium.com
[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Bruce Komito
Sent: Friday, May 28, 2004 6:35 AM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] * as pri_net?

If you have used * to support a pri as pri_net (as opposed to pri_cpe),
either to talk to another * system or a PBX of some sort, I would be very
interested in hearing about your experiences.  Imparticular, I would like to
know that it works before I invest in the extra hardware.

TIA

Bruce Komito
High Sierra Networks, Inc.
www.servers-r-us.com
(775) 284-5800 ext 115


_______________________________________________
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

I've used it to connecto to 2 * boxes through Zaptel E1 cards. It works 
really fine, and was really easy to configure them.

Bruno

Bruce Komito wrote:
> If you have used * to support a pri as pri_net (as opposed to pri_cpe),
> either to talk to another * system or a PBX of some sort, I would be very
> interested in hearing about your experiences.  Imparticular, I would like
> to know that it works before I invest in the extra hardware.
> 
> TIA
> 
> Bruce Komito
> High Sierra Networks, Inc.
> www.servers-r-us.com
> (775) 284-5800 ext 115
> 
> 
> _______________________________________________
> 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

On Fri, 2004-05-28 at 08:34, Bruce Komito wrote:
> If you have used * to support a pri as pri_net (as opposed to pri_cpe),
> either to talk to another * system or a PBX of some sort, I would be very
> interested in hearing about your experiences.  Imparticular, I would like
> to know that it works before I invest in the extra hardware.
I'm glad to see all the success stories here, as I am so far the only
failure so far and it is explainable. According to JerJer, I will have
to upgrade the libpri on one of my machines to get it to work properly.
Once that is done, it will be fine.
-- 
Steven Critchfield  <critch@basesys.com>

Bruce Komito wrote:
> If you have used * to support a pri as pri_net (as opposed to pri_cpe),
> either to talk to another * system or a PBX of some sort, I would be very
> interested in hearing about your experiences.  Imparticular, I would like
> to know that it works before I invest in the extra hardware.
> 
> TIA
> 
> Bruce Komito
Here too....

asterisk/TE410P <ISDN-PRI> TN767E/Definity G3si v6

switchtype = 5ess
signalling = pri_net

inbound/outbound, ext/ext, DNIS/ANI all working well.
Very cool!

I have digium E1s as pri_net connected to nms based softswitch - no problems

Dave

-----Original Message-----
From: asterisk-users-admin@lists.digium.com
[mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Bruce Komito
Sent: Friday, May 28, 2004 3:35 PM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] * as pri_net?


If you have used * to support a pri as pri_net (as opposed to pri_cpe),
either to talk to another * system or a PBX of some sort, I would be very
interested in hearing about your experiences.  Imparticular, I would like
to know that it works before I invest in the extra hardware.

TIA

Bruce Komito
High Sierra Networks, Inc.
www.servers-r-us.com
(775) 284-5800 ext 115


_______________________________________________
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

I was having trouble getting zaptel to startup.  Thought I'd share my
experience since I saw others with the same issue and no solutions.  I'm
running Fedora FC2.  Symptoms were:


xtcfg -vv that says that it's "unable to open master device
/etc/dev/ctl"

modprobe zaptel was also failing

/var/log/messages had messages like:
Apr 12 18:48:45 asterisk kernel: zaptel: version magic '2.6.5-1.315custom
686 REGPARM 4KSTACKS gcc-3.3' should be '2.6.5-1.315 686 REGPARM
4KSTACKS
gcc-3.3'

The solution was to go into /usr/src/linux-2.6/include/linux/version.h and
change the UTS_RELEASE string from '2.6.5-1.315custom' to
'2.6.5-1.315'

Then rebuild zaptel, install and run again.

Obviously I chose the "custom" option when I setup the OS.  Is there
someway
to fix the zaptel code to not be so picky?

  -mike

On Sat, 2004-05-29 at 14:15 +0200, Brancaleoni Matteo wrote:
> sure, that happens because kernel-source package from fedora
> has the kernel version set to <blah>custom, as long as many
> other rh versions.
Mandrake does this as well. Great idea if you want to increase the noise
on a list.

-- 
Dave Cotton <dcotton@linuxautrement.com>