Also T38 doesn't work over IAX as far as I know its only on SIP when pertaining to Asterisk or Callweaver.<br><br><div class="gmail_quote">On Dec 5, 2007 3:05 PM, Alex Pilosov <<a href="mailto:alex@pilosoft.com">alex@pilosoft.com
</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Wed, 5 Dec 2007, <a href="mailto:joakimsen@gmail.com">
joakimsen@gmail.com</a> wrote:<br><br>> David you've proven my point when I said your company promises anything<br>> the customer wants.<br></div>Teliax is a competitor but I feel compelled to defend him. Your<br>
expectations are entirely unreasonable and devolve from misinterpretation<br>of David's words.<br><div class="Ih2E3d"><br>> Your exact words were "current carrier cannot refuse a port based on<br>> billing disputes" ... we just got off the phone and I was told the LNP
<br>> was denied due to the BTN and that's entirely possible that Deltacom did<br>> so without our knowledge because the numbers on the account were<br>> assigned in two different batches... still doesnt explain why it took 8
<br>> weeks to get a response or why the numbers with the correct BTN could<br>> not be ported.<br></div>a) LNP is a *total pita*. It may take 1 day, it may take 8 weeks, it might<br>not happen at all. You are at a mercy of the current carrier. If they
<br>don't like you, they'll find a way to block it.<br><br>b) If LNP didn't happen, is not teliax's fault. They submit the LNP<br>request with BTNs provided by you. Current carrier may accept or reject<br>
it. If you don't know your BTNs and/or if you don't know what information<br>your current carrier needs to process the LNP request, it ain't teliax's<br>fault.<br><br>c) "denied due to BTN" does not mean denied due to billing dispute. It
<br>means BTNs did not match between the request and carrier's records.<br><br>You would be better served by educating yourself prior to posting to the<br>list again.<br><div class="Ih2E3d"><br><br>> About the T38 faxing you said "We would be happy to facility this.
T.38<br>> on inbound is not supported but itis on outbound." with no mention to<br>> anything about testing. I had no clue to what carriers you send your<br>> calls to until this moment but I can assure you L3 does support T38 so
<br>> there must be something on your end. Your gateways respond "488 not<br>> acceptable here" when we send a T38 re-invite. After I signed up for<br>> your service and tried to get support for the non-working T38 I was
<br>> informed that service was of an experimental nature. If your carriers<br>> support t.38 as you claim and it does seem that your gateways are t38<br>> aware I don't understand why none of the "traces" we performed showed
<br>> that there was a configuration issue in your gateway or why a ticket was<br>> never submitted to your carrier. I never asked for it but it does seem<br>> to make sense especially when you tout T38 faxing support to potential
<br>> customers.<br></div>Given the fact that Teliax supports t38, and given the fact that David<br>demonstrated his clue earlier, given the fact that you've just<br>demonstrated your lack of said clue, I have come to conclusion that "you
<br>is doing something wrong".<br><br>Given the nature of retail service, and complexity of T38 and different<br>implementations of such, it isn't really teliax's responsibility to<br>troubleshoot *what* you are doing wrong.
<br><font color="#888888"><br>-alex<br></font><div><div></div><div class="Wj3C7c"><br><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-biz mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-biz" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-biz
</a><br></div></div></blockquote></div><br>