Cant seem to record on a route that uses a password / Pin


(Jeremy Lizzotte) #1

I have an international outbound route and it has a pin. All calls are recorded that use the other outbound routes, just not that one. Is there a way to force calls to record even with pins present? The extension is already setup to force but it doesnt force on this particular route. Freepbx 13

Thanks


(Dave Burgess) #2

That sounds bug-like to me (it should work as-is) so in addition to the forum, I’d spin up a problem report on the Support Page. Include as much detail in the ticket as you can.


(Jeremy Lizzotte) #3

Thanks Dave. Much appreciated.


(Lorne Gaetz) #4

Reporting an issue of this severity will not get attention unless it can be reproduced in 14/15. Share a call trace via pastebin so we can see where it goes off the rails:
https://wiki.freepbx.org/display/SUP/Providing+Great+Debug#ProvidingGreatDebug-AsteriskLogs-PartII


(Jeremy Lizzotte) #5

Seems like the conversation is recorded.

/var/log/asterisk/full-20200813:[2020-08-12 15:33:59] VERBOSE[18159][C-000088e6] pbx.c: Executing [s@macro-user-callerid:1] Set(“SIP/1027-0000c4df”, “TOUCH_MONITOR=1597260839.51691”) in new stack
/var/log/asterisk/full-20200813:[2020-08-12 15:33:59] VERBOSE[18159][C-000088e6] pbx.c: Executing [recordcheck@sub-record-check:17] Set(“SIP/1027-0000c4df”, “__CALLFILENAME=out-011524432276261-1027-20200812-153359-1597260839.51691”) in new stack
/var/log/asterisk/full-20200813:[2020-08-12 15:33:59] VERBOSE[18159][C-000088e6] pbx.c: Executing [recordcheck@sub-record-check:18] MixMonitor(“SIP/1027-0000c4df”, “2020/08/12/out-011524432276261-1027-20200812-153359-1597260839.51691.wav,abi(LOCAL_MIXMON_ID),”) in new stack
/var/log/asterisk/full-20200813:[2020-08-12 15:33:59] VERBOSE[18159][C-000088e6] pbx.c: Executing [recordcheck@sub-record-check:22] Set(“SIP/1027-0000c4df”, “CDR(recordingfile)=out-011524432276261-1027-20200812-153359-1597260839.51691.wav”) in new stack

and I found it. But when I look at the call on the CDR, the calls deem to be originating from the DID as opposed to the Extension. Ill show you a comparison:

2020-08-12 16:28:36 Call recording Call recording 1597264116.51851 “Diana Carrillo” <1027> <207517XXXX> Dial 8474371111 ANSWERED 03:07

2020-08-12 15:34:02 1597260839.51691 207517XXXX <207517XXXX> Dial 01152443XXXXXX ANSWERED 01:26

Those are calls from the same person, the ONLY difference is the international has the pin to protect the calls.

And since it doesnt look like its originating from ext 1027, it doesnt associate itself with the recording, i would assume. Any help to get this resolved would be great. thanks!


(Jeremy Lizzotte) #6

anyone know why one call might show up as an extension and another from the same phone as the DID?


(Jeremy Lizzotte) #7

Can anyone possibly point me in any sort of direction here?


(Dave Burgess) #8

Not sure, but https://wiki.freepbx.org/display/SUP/Providing+Great+Debug#ProvidingGreatDebug-AsteriskLogs-PartII with a call trace would be a good place to start.

If I was a guessing man (and we all know I actually am), I’d start looking at the extension configurations and see if the outbound caller ID is set on the extensions in question. I’d also look to see if one or more of these was associated with an Inbound DID.

Short of that, logs are really going to be important.

Also, if there’s actually a problem on FreePBX 13, you’re not going to get a lot of support from Sangoma (as in, code fixes). Upgrading to FreePBX 14 or 15 would probably be a good start either way. The problem may already be fixed in the newer versions.