<div dir="ltr">The documentation is in my head, two solid days worth.<br><br>The issue is the SPID code that Marcin Pyco claimed he had the only code, and way to make it work in the US.. <br><br>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.<br>
<br>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)<br><br>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...<br>
<br>Marcin Pyco claimed that BRI would not work without his code in the US and went so far as to call me a liar. <br><br>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.<br>
<br>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. <br><br>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). <br>
<br>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.<br><br>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. <br>
<br>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.<br><br>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.<br>
<br>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.<br>
<br>-- <br>Thanks,<br>Steve Totaro <br>+18887771888 (Toll Free)<br>+12409381212 (Cell)<br>+12024369784 (Skype)<br><br><div class="gmail_quote">On Mon, Oct 13, 2008 at 5:55 PM, Michael Graves <span dir="ltr"><<a href="mailto:mgraves@mstvp.com">mgraves@mstvp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<font size="2">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.<br>
<br>
I abandoned the idea for being more expensive when all costs are considered.<br>
<br>
Michael<br>
<br>
--Original Message Text---<br>
<b>From:</b> Steve Totaro<br>
<b>Date:</b> Mon, 13 Oct 2008 17:37:37 -0400<div><div></div><div class="Wj3C7c"><br>
<br>
I have done this. Why BRIs exist in the US is beyond me. If you can, don't go with BRI.<br>
<br>
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.<br>
<br>
Thanks,<br>
Steve Totaro<br>
<br>
On Mon, Oct 13, 2008 at 4:57 PM, Michael Graves <<font color="#0000ff"><u><a href="mailto:mgraves@mstvp.com" target="_blank">mgraves@mstvp.com</a><font color="#000000"></font></u>> wrote:<br>
<font size="2">I had considered something like this as well, but was convinced to go another direction. <br>
<br>
I wrote something up about it at the time.<br>
<br>
<font color="#0000ff"><u><a href="http://www.smallnetbuilder.com/content/view/30444/84/" target="_blank">http://www.smallnetbuilder.com/content/view/30444/84/</a><font color="#000000"></font></u><br>
<br>
Michael<br>
<br>
<br>
<br>
--Original Message Text---<br>
<b>From:</b> Wilton Helm<br>
<b>Date:</b> Mon, 13 Oct 2008 14:44:26 -0600<br>
<br>
<br>
Hi, <br>
<br>
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. <br>
<br>
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. <br>
<br>
Ideally it would allow any combination of two calls, identified by SPID. <br>
<br>
If anyone has done anything similar, or has any experience with BRI ISDN, I would appreciate input and direction. <br>
<br>
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. <br>
<br>
Thanks, <br>
Wilton Helm <br>
Embedded System Resources <br>
<br>
<br>
<br>
<br>
<br>
--<br>
<font color="#888888">Michael Graves<br>
mgraves<at><font color="#0000ff"><u><a href="http://mstvp.com" target="_blank">mstvp.com</a><font color="#888888"></font></u><br>
<font color="#0000ff"><u><a href="http://blog.mgraves.org" target="_blank">http://blog.mgraves.org</a><font color="#888888"></font></u><br>
o713-861-4005<br>
c713-201-1262<br>
<font color="#0000ff"><u><a href="mailto:sip%3Amjgraves@pixelpower.onsip.com" target="_blank">sip:mjgraves@pixelpower.onsip.com</a><font color="#888888"></font></u><br>
skype mjgraves<br>
fwd 54245<br>
<br>
<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <font color="#0000ff"><u><a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a><font color="#888888"></font></u> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<font color="#0000ff"><u><a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><font color="#888888"></font></u><br>
<br>
<br>
<br>
<br>
<br>
-- <br>
Thanks,<br>
Steve Totaro <br>
+18887771888 (Toll Free)<br>
+12409381212 (Cell)<br>
+12024369784 (Skype)<br>
<br>
<br>
<br>
<font color="#000001" face="Arial" size="2">
--<br>
Michael Graves<br>
mgraves<at><a href="http://mstvp.com" target="_blank">mstvp.com</a><br>
<a href="http://blog.mgraves.org" target="_blank">http://blog.mgraves.org</a><br>
o713-861-4005<br>
c713-201-1262<br>
<a href="mailto:sip%3Amjgraves@pixelpower.onsip.com" target="_blank">sip:mjgraves@pixelpower.onsip.com</a><br>
skype mjgraves<br>
fwd 54245<br>
<br>
</font></font></font></font></font></font></font></font></font></font></div></div></font><br>_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote></div><br><br clear="all"><br><br>
</div>