[asterisk-users] ISDN

[Steve Totaro]

The documentation is in my head, two solid days worth.

The issue is the SPID code that Marcin Pyco claimed he had the only code,
and way to make it work in the US..

You may need this "code" if you are using SPIDs to route calls.  In my
situation, they were just a hunt group, two BRIs, and I was tasked with
adding a quad port Sangoma analog card.  Absolutely NO difference in audio,
but talk about a mish mash of equipment.  Luckily  Sangoma drivers for
Zaptel 1.4 do not require Zaptel to be patched.

It absolutely refused to work with 1.2 so it became my first 1.4
installation out of necessity, I am sure 1.2 didn't work because of
conflicting patches (BRIStuff and Sangoma)

That is why Xorcom was so happy to help me with a US BRI, and I just thought
Tzafrir was a nice guy trying to help out...

Marcin Pyco claimed that BRI would not work without his code in the US and
went so far as to call me a liar.

I proved him wrong, but he is not very good at admitting he is wrong, he
blamed Verizon rather than apologizing.  He is very good at calling people
liars but not so good at apologizing and admitting he is wrong.

Whatever the rub, using BRIStuff, Zaptel 1.4.X and a Junghanns' card or
knock-off (and even Sangoma drivers), it will work with Verizon.

I have pages upon pages of all the emails and IRC chats where I am called a
liar, and where Tzafrir admits his true motives (to his credit).

And finally the revelation that you do not need any additional code for
SPIDs (at least with Verizon) in the US, and around here everyone resells
Verizon anyways.

One thing to note is that inbound calls work immediately when the spans come
up BUT it takes ten to fifteen minutes for outbound calls to work.

I am not sure if the time starts at loading qozap or Asterisk but it works
beyond a shadow of a doubt, so don't pay for "code" that makes it work.

I am convinced that the conversations you had with Xorcom and probably Pika
(since Marcin works or worked there (LinkedIN)) came as a direct result of
my work.

Anyways, in this area, everything is close to a CO and I BET that calling
from a regular phone, you could never guess which is ISDN and which is POTS,
unless you cheat somehow, but not by voice quality.  I am not sure why OP
thinks that two pair for voice is better than two unless he is afraid of
echo, which was absolutely no issue with the Sangoma cards with onboard EC.

-- 
Thanks,
Steve Totaro
+18887771888 (Toll Free)
+12409381212 (Cell)
+12024369784 (Skype)

On Mon, Oct 13, 2008 at 5:55 PM, Michael Graves <mgraves at mstvp.com> wrote:

> I had converations with both Pika and Xorcom wherein the thought that it
> should be possible using their interface hardware. There might be some
> software changes to be made in their drivers, but BRI should be usable in
> the US.
>
> I abandoned the idea for being more expensive when all costs are
> considered.
>
> Michael
>
> --Original Message Text---
> *From:* Steve Totaro
> *Date:* Mon, 13 Oct 2008 17:37:37 -0400
>
>
> I have done this. Why BRIs exist in the US is beyond me. If you can, don't
> go with BRI.
>
> Who is the carrier. There is someone on the list that will tell you it is
> impossible unless you use his code, which is not true.
>
> Thanks,
> Steve Totaro
>
> On Mon, Oct 13, 2008 at 4:57 PM, Michael Graves <*mgraves at mstvp.com*>
> wrote:
> I had considered something like this as well, but was convinced to go
> another direction.
>
> I wrote something up about it at the time.
>
> *http://www.smallnetbuilder.com/content/view/30444/84/*
>
> Michael
>
>
>
> --Original Message Text---
> *From:* Wilton Helm
> *Date:* Mon, 13 Oct 2008 14:44:26 -0600
>
>
> Hi,
>
> I'm in the process of setting up Asterisk in a SOHO environment using ISDN
> for trunking. More specifically a BRI 2B+D circuit where one SPID is used
> for the business and the other is used for personal. The circuit already
> exists, but is presently being interfaced to POTS phones via a TA.
>
> This configuration is not very common in the US, but we are fortunate that
> our LEC offers it price competitively with equivalent POTS services and it
> makes more sense, both in terms of voice quality (4 wire digital to the
> PABX) and flexibility.
>
> Ideally it would allow any combination of two calls, identified by SPID.
>
> If anyone has done anything similar, or has any experience with BRI ISDN, I
> would appreciate input and direction.
>
> If anyone knows where documentation exists on configuring ISDN, that
> information would also be greatly appreciated. Asterisk has a bit of a
> learning curve, and ISDN BRI isn't the most widely used or covered aspect of
> it. BTW, I have a strong telecom background, so the theory part of it will
> not be a problem, only the necessary documentation to apply it to Asterisk.
>
> Thanks,
> Wilton Helm
> Embedded System Resources
>
>
>
>
>
> --
> Michael Graves
> mgraves<at>*mstvp.com*
> *http://blog.mgraves.org*
> o713-861-4005
> c713-201-1262
> *sip:mjgraves at pixelpower.onsip.com <sip%3Amjgraves at pixelpower.onsip.com>*
> skype mjgraves
> fwd 54245
>
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by *http://www.api-digital.com* --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> *http://lists.digium.com/mailman/listinfo/asterisk-users*
>
>
>
>
>
> --
> Thanks,
> Steve Totaro
> +18887771888 (Toll Free)
> +12409381212 (Cell)
> +12024369784 (Skype)
>
>
>
>  --
> Michael Graves
> mgraves<at>mstvp.com
> http://blog.mgraves.org
> o713-861-4005
> c713-201-1262
> sip:mjgraves at pixelpower.onsip.com <sip%3Amjgraves at pixelpower.onsip.com>
> skype mjgraves
> fwd 54245
>
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20081013/1ddb1e76/attachment-0001.htm