Ticket #4118 (closed Bugs: fixed)

Opened 3 years ago

Last modified 3 years ago

NVFaxDetect issue

Reported by: kopspa Assigned to: mbrevda
Priority: minor Milestone: 2.8
Component: Fax Version: 2.7-branch
Keywords: Cc:
Confirmation: Need testing Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description (Last modified by p_lindheimer)

in 2.7.0, when using NVFax Detection, if a fax is detected, the call goes to a 'talk' extension instead of the destination i choose (an iax extension, iaxmodem) here's the log

[Mar  9 10:23:03] VERBOSE[23893] pbx.c:     -- Executing [0112263583@from-trunk:6] Set("SIP/patton-000001c0", "FAX_DEST=from-did-direct^250^1") in new stack
[Mar  9 10:23:03] VERBOSE[23893] pbx.c:     -- Executing [0112263583@from-trunk:7] Answer("SIP/patton-000001c0", "") in new stack
[Mar  9 10:23:03] VERBOSE[23893] pbx.c:     -- Executing [0112263583@from-trunk:8] PlayTones("SIP/patton-000001c0", "ring") in new stack
[Mar  9 10:23:03] VERBOSE[23893] pbx.c:     -- Executing [0112263583@from-trunk:9] NVFaxDetect("SIP/patton-000001c0", "4,t") in new stack
[Mar  9 10:23:03] DEBUG[23893] app_nv_faxdetect.c: Preparing detect of fax (waitdur=4ms, sildur=1000ms, mindur=100ms, maxdur=-1ms)
[Mar  9 10:23:03] DEBUG[23893] app_nv_faxdetect.c: Start of voice token!
[Mar  9 10:23:04] DEBUG[23893] app_nv_faxdetect.c: Found qualified token of 217 ms
[Mar  9 10:23:04] NOTICE[23893] app_nv_faxdetect.c: Redirecting SIP/patton-000001c0 to talk extension
[Mar  9 10:23:04] VERBOSE[23893] pbx.c:     -- Executing [talk@from-trunk:1] Set("SIP/patton-000001c0", "__FROM_DID=talk") in new stack
[Mar  9 10:23:04] VERBOSE[23893] pbx.c:     -- Executing [talk@from-trunk:2] NoOp("SIP/patton-000001c0", "Received an unknown call with DID set to talk") in 
new stack
[Mar  9 10:23:04] VERBOSE[23893] pbx.c:     -- Executing [talk@from-trunk:3] Goto("SIP/patton-000001c0", "s,a2") in new stack
[Mar  9 10:23:04] VERBOSE[23893] pbx.c:     -- Goto (from-trunk,s,2)
[Mar  9 10:23:04] VERBOSE[23893] pbx.c:     -- Executing [s@from-trunk:2] Answer("SIP/patton-000001c0", "") in new stack
[Mar  9 10:23:04] VERBOSE[23893] pbx.c:     -- Executing [s@from-trunk:3] Wait("SIP/patton-000001c0", "2") in new stack
[Mar  9 10:23:06] VERBOSE[23893] pbx.c:     -- Executing [s@from-trunk:4] Playback("SIP/patton-000001c0", "ss-noservice") in new stack

if i use the sip detection method, it goes to the right extension (from-did-direct,250,1)

Change History

03/09/10 10:07:16 changed by p_lindheimer

  • confirmation changed from Unreviewed to Need testing.

can you try a fix similar to what was done in #3115. You can put it directly in the generated dialplan if it is easier.

Please let me know if this worked and the exact syntax (specifically if you put a , (comma) or a | (pipe) character as the separator. I seem to recall nvFax() being particular about wanting the | in some earlier versions even where , was the norm otherwise. Also let me know what Asterisk version this was once you provide the feedback of what you put in.

We can then update the generation to include the t option. (if it's not t anymore, please check what it is on your version and provide that also.) Thanks!

03/09/10 10:09:12 changed by p_lindheimer

btw - so there is no confusion, the referenced patch in #3115 will not apply to the current code, but the solution there is applicable to here.

03/10/10 14:14:18 changed by p_lindheimer

  • description changed.

any update on this?

03/11/10 04:10:48 changed by kopspa

i can confirm that the correct syntax is ",t" and not "|t"

but i've noticed that if the call is a fax, it is detected and goes to fax if the call is not a fax and i (the caller) say something, the call continue to the right destination

if the call is not a fax and i (the caller) says nothing, it goes to the talk extensions, so the call was dropped, here is the log

    -- Executing [talk@from-trunk:1] Set("SIP/patton-00000016", "__FROM_DID=talk") in new stack
    -- Executing [talk@from-trunk:2] NoOp("SIP/patton-00000016", "Received an unknown call with DID set to talk") in new stack
    -- Executing [talk@from-trunk:3] Goto("SIP/patton-00000016", "s,a2") in new stack
    -- Goto (from-trunk,s,2)
    -- Executing [s@from-trunk:2] Answer("SIP/patton-00000016", "") in new stack
    -- Executing [s@from-trunk:3] Wait("SIP/patton-00000016", "2") in new stack
    -- Executing [s@from-trunk:4] Playback("SIP/patton-00000016", "ss-noservice") in new stack
    -- <SIP/patton-00000016> Playing 'ss-noservice.gsm' (language 'en')

it is not a better idea to remove the ",t" option to nvfaxdetect? or to define a 'talk' extension in the dialplan?

thanks

03/16/10 21:45:29 changed by p_lindheimer

we should not put in a talk extension, that complicated things further. The "t" option is suppose to tell it to ignore talking. Are you saying that it is still not behaving when there is silence?

If that is the case, can you have a look at this page and determine what needs to be set to get it to stop intervening:

http://www.voip-info.org/wiki/view/NVFaxDetect

It looks like there are some other settings that may need to be set, for example set "d" to ignore DTMF or it sounds like it will try to interpret that as an extension and branch there (convenient for IVRs but not here). If that is not related, have a look a the "sildur" setting, maybe it needs to be cranked way up (just set it really really high like 100 seconds...)

Let me know what you find. NVFaxDetect has always been a pain on a minority of systems with the talk detect which I think varies by different versions. We just need to know how to make it ignore that and what version of Asterisk you are running on and then we can try to set the right parameters for it.

03/19/10 18:21:49 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to fixed.

(In [9291]) fixes #4118 I think, should be ',' not '|' before t option

03/19/10 18:24:51 changed by p_lindheimer

(In [9292]) Merged revisions 9290-9291 via svnmerge from http://svn.freepbx.org/modules/branches/2.7

........

r9291 | p_lindheimer | 2010-03-19 15:21:49 -0700 (Fri, 19 Mar 2010) | 1 line

fixes #4118 I think, should be ',' not '|' before t option

........