[asterisk-bugs] [JIRA] (ASTERISK-22195) Faxdetect sets callerid to be uniqueid

[Michael L. Young (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-22195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208220#comment-208220 ] 

Michael L. Young commented on ASTERISK-22195:
---------------------------------------------

We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information


                
> Faxdetect sets callerid to be uniqueid
> --------------------------------------
>
>                 Key: ASTERISK-22195
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22195
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/General
>    Affects Versions: 11.3.0
>         Environment: CentOS release 6.3 64bit
>            Reporter: David Cunningham
>
> When faxdetect=yes in sip.conf and a CNG has been detected, the following AGI has a weird callerid - the uniqueid without the ".".  For example here it's set to "13746961381108832".
> {noformat}
> [Jul 24 16:02:24] DEBUG[9009][C-00024fee] dsp.c: 1100 Hz done detected
> [Jul 24 16:02:24] DEBUG[9009][C-00024fee] chan_sip.c: Fax CNG detected on SIP/1-69.42.xxx.xxx-00058d5c
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] chan_sip.c: == Redirecting 'SIP/1-69.42.xxx.xxx-00058d5c' to fax extension due to
> CNG detection
> ...
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] pbx.c: -- Executing [fax at from-external:1] AGI("SIP/1-69.42.xxx.xxx-00058d5c", "agi://127.0.0.1/product?stype=external") in new stack
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: AGI Tx >> agi_network: yes
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: AGI Tx >> agi_network_script: product?stype=external
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_request: agi://127.0.0.1/product?stype=external
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_channel: SIP/1-69.42.xxx.xxx-00058d5c
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_language: en
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_type: SIP
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_uniqueid: 1374696138.1108832
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_version: 11.3.0
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_callerid: 13746961381108832
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_calleridname: CONSULTING
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_callingpres: 0
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_callingani2: 0
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_callington: 0
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_callingtns: 0
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_dnid: 12121111111
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_rdnis: unknown
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_context: from-external
> [Jul 24 16:02:24] VERBOSE[9009][C-00024fee] res_agi.c: <SIP/1-69.42.xxx.xxx-00058d5c>AGI Tx >> agi_extension: fax
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira