Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Patton M-ATA never completes transmission 2

Status
Not open for further replies.

sunshine999

Vendor
Apr 19, 2012
32
US
technician has worked with Patton. Patton says all is good. He also has Avaya documents. fax to fax will not complete .
***you can hear the modem tones then it gets garbled and never completes. I have listed everything he has tried below.
IP Office is Rls 10. with PRI trunks
Delete/Rebuild both IPO User& Base extension along with factory default of M-ATA
Upgrade M-ATA to latest firmware
Forced ATA & IPO to not use T.38, only G.711U
Forced T.38 settings in IPO down to 9600 baud rate
Disable/Enable Re invite
Tried Lockdown Codec
Set fax machine baud rate to 9600
Disable ECM on both fax machine and IPO
Modified codec selections in both IPO & ATA
Tried 3 different model fax machines- Faxes worked on old system via analog station ports
Can make current faxes work on IPO analog station port, but 2 locations won’t have this option so must use ATA
PRI trunking at this location
Voice calls work fine on ATA both in house and via trunks
Does anyone see what we are missing? Any help will be much appreciated.

thanks in advance
 
Different building than the IPO- However all connected via local WAN over fiber
 
in the Patton
Telephony - codecs
set Packetization to 20 ms
Jitter buffer to fixed.
try 80 ms

 
all connected via local WAN over fiber

if one network is gigabit, the link is 100 meg, then back to gigabit.
You'll need QoS
 
Do you have a suggestion on Codecs?
Patton suggested only using G711 u and a law.
Also, do you suggest using T.38 or G711? Also should I re set the codec lockdown or reinvite options?
 
10 gig backbones between building with the exception of 1 and it’s 1 gig. All desktop connections are 1 gig
 
I HIGHLY suspect that one of the ends IS trying to use T.38. If you watch the SIP transactions, you'll almost certainly see a re-invite that is not being handled properly.

Mike Forrence
 
Capture a transaction via Monitor - it will tell the tale. The magic in SIP is that it's fairly easy to follow. Easiest when there are few other calls.

Mike Forrence
 
Use T.38 both ends, it's the protocol specifically intended to handle the issues caused by trying to send fax over IP connections (to those who've got their fax solutions working on G711, bravo you, your network is probably very different from the OP's).



Stuck in a never ending cycle of file copying.
 
simplify and isolate the problem

Put the patton device on the same switch that the phone system is on
(eliminates the network)
Test using a Fax machine using a POTS line.
(eliminates IP to IP faxing)

Use wireshark to take a look at the network.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top