I have problems to solve my SPA112 issues with incoming fax (Brother FAX-2820). Firstly, the fax starts ringing three times until hook off. At the same moment when it hooks off, I can see on the syslog that the SPA112 stops continuing sending syslog messages for some seconds. Next, it tries to get the incoming fax somehow but fails in different ways. Sometimes I get a off hook warning in the web config utility (Voice > Information > Line 1 Status > Call 1 Tone) and no data transfer inbound on the counters. Another issue: the SPA connects properly, recognizes the data as FAX (Voice > Information > Line 1 Status > Call 1 FAX = yes) but the fax device stops receiving data with an error.
When I study the syslog I am wondering that I never get an hook off event. I don't know why that happens, but when I test it manually on the fax (dial a number, press start and then stop) I get these hook off messages properly on syslog.
When I call my fax with a normal telephone, the fax hooks off physically (clicking noise from the fax hardware) but the ringing tone stays for about 10 more seconds until I hear the beeping fax-tones on the telephone. Sometimes, the ringing tone sounds for a long time (fax hooked off and on again physically) until the connection drops.
I have reduced the baud rate of my fax to 9600 and disabled ECM. Sending of fax works quite good, I am more concerned about the reception issue at the moment.
Please find my SPA112 config attached as a PDF. I have made that config according to instructions of my VoIP provider. I have also added two syslog files of tests I have made.
Any ideas what to try?
(please ask me if something is not clear, English is not my primary language)
It seems that log 1 and log 2 have no relationship. Log 1 is taken from device with 1.3.3 firmware, call is comming from peer called VoIPProvider and it is using T.38 protocol for fax. Log 2 is taken from device with 1.3.1 firmware, call is comming from peer called Netstream and it is NOT trying to utilize T.38 protocol.
Lets start to analyze the log 1 (VoIPProvider->Cisco/SPA112-1.3.3)
2014-01-08 05:08:17 INVITE, aLaw codec preferred
2014-01-08 05:08:17 CallerID send to line, (CAS, before first ring, FSK mode)
2014-01-08 05:08:19 first ring
2014-01-08 05:08:24 second ring
2014-01-08 05:08:29 third ring
2014-01-08 05:08:34 fourth ring
2014-01-08 05:08:39 fax CNG detected, it mean the line is on-hook a while
2014-01-08 05:08:42 line considered connected, bidirectional voice, aLaw
2014-01-08 05:08:42 incomming T.38 re-INVITE
2014-01-08 05:08:44 transition to T.38 completed
-05:09:16 fax keep trying CNG, nothing seen from caller's side
2014-01-08 05:09:18 timeout, line on-hook, call cleanup started
Lets start to analyze the log 2 (Netstream->Cisco/SPA112-1.3.1)
2014-01-08 19:25:17 INVITE, aLaw codec preferred
2014-01-08 19:25:18 CallerID send to line, (CAS, before first ring, FSK mode)
2014-01-08 19:25:19 first ring
2014-01-08 19:25:24 second ring
2014-01-08 19:25:29 third ring
2014-01-08 19:25:34 fourth ring
2014-01-08 19:25:40 fax CNG detected, it mean the line is on-hook a while
2014-01-08 19:25:43 line considered connected, bidirectional voice, aLaw
-19:26:13 fax keep trying CNG, nothing seen from caller's side
2014-01-08 19:26:18 call cleanup initiated from caller's side
2014-01-08 19:26:20 CPC procedure on analog line, ignored by fax device, line remain on-hook
2014-01-08 19:26:21 hook-flash from fax detected
2014-01-08 19:26:26 line on hook
but fails in different ways
Not surprising. Calls are arriving from different equipment (VoIPProvider using T.38 versus Netstream not using T.38), to different devices (firmware 1.3.1 versus 1.3.3). Caller is patient enougth in first case, so call is cancelled from called side versus call is cancelled from caller side in second case. There is little common in the both cases, so different behavior observed, different log content.
Well, in both cases there seems to be no attempt to send fax from caller side. It either didn't hear the CNG of called fax or it is caused by other reason.
When I call my fax with a normal telephone, the fax hooks off physically (clicking noise from the fax hardware) but the ringing tone stays for about 10 more seconds
It seems to be wrong conclusion. Ringback-tone is turned of by "line answered" event. If you hear a noise during ring-back tone, then it didn't come from fax. At the first, line is not on-hook, at the second, audio channel to ISP is one way unless line answered. If you hear a noise before call is picked up by fax, then it's noise generated elsewhere on path.
It may explay all the problems. Clicking noise may mean problems on the path like so high jitter or packets lost. Such condition will remain even after the line is picked up. Poor call path quality may cause the CNG tone is so distorted to be recognized by caller ...
You have a Cisco Unified Communications Manager (CUCM) system and want
to configure a SPA112 analog telephone adaptor (ATA) to register to the
CUCM so that you can use up to two analog phones or similar FXS devices
with the CUCM.In this application note, ...
This document is a must-read for all SPA232D installers, administrators,
and users. The document takes you from unboxing the SPA232D ATA and
SPA302D DECT handsets, through DECT handset registration, and connecting
to the PSTN and ITSP.The document describ...