The Faxing will not work when you enable T.38. When I diable it works.
why is that?
Hi rabbitman,
When you disable T.38, your fax attempt is likely using G711 instead. Many users have noted success with G711 -- more so than with T.38. For some reason, I have yet to hear of any OBi user successfully faxing via T.38. :o
If anyone out there has been successful with T.38 on the OBi202, please speak up. :) I'd like to get this working myself but have placed it on the back burner due to the unsuccessful feedback by others in the forum.
pc44
Quote from: pc44 on September 02, 2012, 06:32:24 AM
When you disable T.38, your fax attempt is likely using G711 instead. Many users have noted success with G711 -- more so than with T.38. For some reason, I have yet to hear of any OBi user successfully faxing via T.38. :o
I believe that the voice SP needs to support T.38.
Quote from: QBZappy on September 02, 2012, 06:42:00 AMI believe that the voice SP needs to support T.38.
You are correct, as usual. :) Callcentric and Anveo Direct support T.38, but have you heard of anyone that has been successful with T.38 on the OBi202 yet?
pc44,
I can't recall anyone reporting using T.38 with success.
T.38 is checked on my obi202 and faxes are working
What service provider are you using?
Just using GV
Ah, in that case GV transcodes everything into G711. That seems to be a false positive.
Soryy pc44, we are still looking for a winner. No cigar for you jjtricket this time. :D
Quote from: QBZappy on September 02, 2012, 12:20:10 PM
Ah, in that case GV transcodes everything into G711. That seems to be a false positive.
Soryy pc44, we are still looking for a winner. No cigar for you jjtricket this time. :D
Awwww :'(
Sorry to burst that bubble, but thanks for your help!
I'm using an obi202 with anveo for fax. I assume I'm using t.38.. I'm kinda a voip noob so i really have no idea. anyway, whatever I'm doing, it's BUGGY BUGGY BUGGY. it can take 2 or 3 tries before a fax successfully sends or receives..
Static,
I was getting all excited there for a minute, and then wham! you slammed the door on me. :) Anveo does support T.38, as QBZ referenced earlier; so I was hoping you would have some success to report. But "buggy buggy buggy" doesn't sound good at all. :(
Are you able to go to your Call Status in the OBi *during* the fax transmissions? I wonder what codec it is reporting to you during these fax attempts. I would assume T.38, but it would be nice to confirm whether that is actually in play during your 2 or 3 attempts.
Thanks for this feedback; it's valuable to me,
pc44
Correct me if I wrong, but T.38 is NOT a codec, but a fax protocol.
Quote from: pc44 on September 18, 2012, 06:15:52 PM
Static,
Are you able to go to your Call Status in the OBi *during* the fax transmissions? I wonder what codec it is reporting to you during these fax attempts. I would assume T.38, but it would be nice to confirm whether that is actually in play during your 2 or 3 attempts.
I have had a trouble ticket open with both OBI and Callcentric about issues with T.38 for over a month
Seems I can send faxes fine but receiving them is a huge issue. The line just disconnects when the fax answers and starts negotiating the connection. OBI techs told me that Callcentric was issuing a BYE and disconnecting the call. When T.38 is disabled Callcentric accepts the T.38 then switches to G711.
Seems Callcentric sees something going on when logging the calls, but only informs me that something is strange. I have not been told what that is. Though this week they are doing an internal port to a diffrent carrier.
I can only hope that it works. Also the setting that Callcentric provided at http://www.callcentric.com/support/device/obihai/obi202 worked better than the Obitalk default settings. Before changing them I was having issues with outbound faxes also
Quote from: Diana on September 19, 2012, 02:56:37 AM
Correct me if I wrong, but T.38 is NOT a codec, but a fax protocol.
Quote from: pc44 on September 18, 2012, 06:15:52 PM
Static,
Are you able to go to your Call Status in the OBi *during* the fax transmissions? I wonder what codec it is reporting to you during these fax attempts. I would assume T.38, but it would be nice to confirm whether that is actually in play during your 2 or 3 attempts.
I believe you are correct. I am trying to determine if T.38 is in play during a fax attempt by some of the users here. So far, it seems as though no one has reported success here with T.38.
Quote from: Billt928 on September 19, 2012, 04:23:40 AM
I have had a trouble ticket open with both OBI and Callcentric about issues with T.38 for over a month
Seems I can send faxes fine but receiving them is a huge issue. The line just disconnects when the fax answers and starts negotiating the connection. OBI techs told me that Callcentric was issuing a BYE and disconnecting the call. When T.38 is disabled Callcentric accepts the T.38 then switches to G711.
Seems Callcentric sees something going on when logging the calls, but only informs me that something is strange. I have not been told what that is. Though this week they are doing an internal port to a diffrent carrier.
I can only hope that it works. Also the setting that Callcentric provided at http://www.callcentric.com/support/device/obihai/obi202 worked better than the Obitalk default settings. Before changing them I was having issues with outbound faxes also
Do keep us posted on this. I do not know much about T.38, but hopefully you, Callcentric, or Obihai will find a solution. Callcentric and Anveo are the only two T.38 supported providers that come to mind, and so far, we aren't seeing success. My backup VoIP provider says they are "planning" to support T.38 "soon" (i.e. last month), but I am still waiting for them to roll this out. If they do, I will be doing extensive testing to try to get mine working.
pc44
Bump. :) If anyone has successfully used T.38 on the OBi202, please share!
it now seems to be working as expected using T38 for most faxes (PSTN lines, OBI202 to OBI202 and others that support T38) Google numbers, HP Test Fax, Magic Jack it will re-invite to use G711U
ITSP SIP
ProxyServer = callcentric.com
RegistrarServer = callcentric.com
UserAgentDomain = callcentric.com
OutboundProxy = srv.callcentric.com
X_ProxyServerRedundancy = unchecked
X_DnsSrvAutoPrefix = enabled
X_PublicIPAddress = your public ip
ITSP General
DigitMap = (*xx.|*123|**275*x.|[3469]11|1xxxxxxxxxx|<1Your Area Code>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.)
Voice Services > SPx Service
X_KeepAliveEnable = enabled
X_KeepAliveExpires = 120
Codec Profile A or B
G711U Codec
Priority = 1
G711A Codec
Priority = 2
All others disabled
You can tell your using T38 under call status (it does not show T38) but this line will change
Call Status
Audio Codec = tx=G711U; rx=G711U
Will change to when sending
Audio Codec = tx=; rx=G711U
After the re-invite to T38.
This is the result of many hours of testing with Obi and Callcentric senior support staff all working together to resolve the T38 issues I was having with the obi disconnecting the call when negotiating the T38 connection.
I hope this helps others with T38 issues
Billt928,
Thanks for sharing.
Thanks Billt928.
Applied most of your settings (used callcentric.com instead of srv.callcentric.com and left the original DigiMap).
As replied on another thread, T.38 now working for me via Brother MFC-395W fax machine to Obi 202 via Callcentric (their free outgoing pay per use service) to work (we use XMediusfax, T.38). Trial on 5pages 225sec fax.
Changing ReInviteExpires from 10 to 15 seems to have also helped alot
Excellent! Thanks for letting us know!
Thanks Billt928,
This is very helpful information!!
It's terrific to know that users are now successful with T.38 on the 202.
Thanks again,
pc44
Would this solution also work with Anveo?
Thanks.
The OBi202 works with Anveo T.38 services.
I also used Billt928 recommendations and got my fax to work with Obi and CC. Reps to Bill. However, I did not enter a Public IP address (not sure what that means. I use Comcast and my IP address can change - especially if I reboot the modem and my Fax machine IP address is non rout-able 192.168..... ) . I disabled all the codecs but the two in the config. I don't understand why I had to disable the T38 codec as per the instructions. I also carefully went through all the menu choices for my Brother MFC fax and made sure everything was set correctly (Brother has a FAQ on VOIP and Fax). I used the HP test number and was able to send a receive (1 page). I seldom receive a fax, but on occasions I still have to send one.
Quote from: DaveKaye on January 02, 2013, 06:27:03 PM
I also used Billt928 recommendations and got my fax to work with Obi and CC. Reps to Bill. However, I did not enter a Public IP address (not sure what that means. I use Comcast and my IP address can change - especially if I reboot the modem and my Fax machine IP address is non rout-able 192.168..... ) . I disabled all the codecs but the two in the config. I don't understand why I had to disable the T38 codec as per the instructions. I also carefully went through all the menu choices for my Brother MFC fax and made sure everything was set correctly (Brother has a FAQ on VOIP and Fax). I used the HP test number and was able to send a receive (1 page). I seldom receive a fax, but on occasions I still have to send one.
The brother test fax number only does G711
I have not had success with Anveo and OBI202 for the purpose of faxing. I am now trying Callcentric and will be using Billt928's "formula". Having said that, can someone "translate" this digitmap please (I am digitmaps "challenged"):
(*xx.|*123|**275*x.|[3469]11|1xxxxxxxxxx|<1Your Area Code>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.)
I ask this--if I have to do any slight adjustments, then I know what the above digitmap means and what changes I am making!!
Thanks in advance...
This probably beongs in a different thread, but here goes anyway:
*xx. Allow * followed by one digit, then by one or more digits. This gives access to all of CallCentric's Star Codes.
*123 Allow * followed by 123 (voicemail). The *xx. would also allow this!
**275*x. Allow any number of digits starting with **275* This gives access via the SIPBroker network.
[3469]11 Allow 311, 411, 611, 911 If you are not using this service provider for 911, then I would delete the "9" to avoid 911 calls routing this way by accident.
1xxxxxxxxxx Allow eleven digit numbers starting with "1".
<1 Your Area Code>[2-9]xxxxxx Allow any seven digit number starting with digits 2 throught to 9, then prepend "1" and your area code.
<1>[2-9]xxxxxxxxx Allow any ten digit number starting with digits 2 through to 9, then prepend "1".
011xx. Allow any number of digits starting with 011 (international calls).
xx. Allow any digit followed by any number of digits. This is a "catch-all" rule for any number that does not match any other rules.
(Mipd) User Defined DigitMap that allows SIP URI dialling from a telephone key pad. Does anyone ever use this?
[^*]@@. Allow any alphanumeric character except * followed by any number of any alphanumeric characters. Used for SIP URI dialling from speed dials etc. A better rule is [^*]@@.'@'@@.
I recommend deleting any rules that you will never use. Rules such as xx. and [^*]@@. accept any number as far as digits are concerned and can cause confusion.
FWIW, T.38 seems to be working out-of-the-box for me on most faxes with CallCentric.
I'm seeing the 'Audio Codec = tx=; rx=G711U' that Billt928 says means T.38 is enabled on MOST faxes I sent; oddly a few numbers have fallen back to G711U (but still went through).
I didn't do any of the configuration outlined by Billt928; I simply setup my OBi202 up with the default 'CallCentric' profile that Obi offers in the portal.
I'm on the latest firmware ( 3.0.1 (Build: 3741) ); my guess is that maybe the Obi people and the CallCentric people got together to get this working out of the box.
Needless to say I'm SUPER excited. Ten years of VOIP and I've never had reliable faxing until now (knock on wood).