CDR / Call recordings not Working since Update to 2.3.1-2

VitalPBX Community Support General Discussion CDR / Call recordings not Working since Update to 2.3.1-2

  • Post
    TrustedbyU
    Participant

    Hi All. I have just updated to latest release and it seems that Call Recordings and CDR have broken (it also seems to think i have 4x ram and 2x the HDD space i had previously????).

    From what i understand is the updated version of vitalPBX now thinks that i am a tenant on my own system? but i have no idea how to fix? can someone possibly point me in the right direction? This is what Verbose gives out when i receive an incoming call….

    -- Executing [s@sub-call-recording:1] NoOp("SIP/7004-00000ece", "Check if call will be recorded") in new stack
    -- Executing [s@sub-call-recording:2] NoOp("SIP/7004-00000ece", "Call Type: 2 ") in new stack
    -- Executing [s@sub-call-recording:3] Set("SIP/7004-00000ece", "TENANT=1d823890bcc364e6") in new stack
    -- Executing [s@sub-call-recording:4] Set("SIP/7004-00000ece", "CALLER=<MYNOWASHERE>") in new stack
    == Extension Changed 7004[extension-hints] new state InUse for Notify User 7005
    == Extension Changed 7004[extension-hints] new state InUse for Notify User 7001
    -- Executing [s@sub-call-recording:5] Set("SIP/7004-00000ece", "CALLEE=7004") in new stack
    -- Executing [s@sub-call-recording:6] Set("SIP/7004-00000ece", "APP_FORCE=yes") in new stack
    == Extension Changed 7004[extension-hints] new state InUse for Notify User 7003
    == Extension Changed 7004[extension-hints] new state InUse for Notify User 7008
    -- Executing [s@sub-call-recording:7] GotoIf("SIP/7004-00000ece", "0?:rec_no_available") in new stack
    -- Goto (sub-call-recording,s,16)
    == Extension Changed 7004[extension-hints] new state InUse for Notify User 7006
    -- Executing [s@sub-call-recording:16] NoOp("SIP/7004-00000ece", "Recordins are not available for tenant ombutel") in new stack
    == Extension Changed 7004[extension-hints] new state InUse for Notify User 7009
    -- Executing [s@sub-call-recording:17] Return("SIP/7004-00000ece", "") in new stack
    == Extension Changed 7004[extension-hints] new state InUse for Notify User 7002
    == Spawn extension (cos-all, , 1) exited non-zero on 'SIP/7004-00000ece'
    -- SIP/7004-00000ece Internal Gosub(sub-call-recording,s,1(1d823890bcc364e6,07946250399,7004,yes)) complete GOSUB_RETVAL=
    == Extension Changed 7004[extension-hints] new state InUse for Notify User 7004
    == Extension Changed 7004[extension-hints] new state InUse for Notify User 7600
    == Extension Changed 7004[extension-hints] new state InUse for Notify User 7509

    Anybody Able to Give me a hint? Many thanks. Mike.

    0
Viewing 4 replies - 1 through 4 (of 4 total)
  • Replies
    Up
    0
    Down

    I can connect me to your system and check it, send me the info to my email: miguel@vitalpbx.com

    0
    TrustedbyU
    Participant
    Up
    0
    Down
    Posted by: mrivera

    I can connect me to your system and check it, send me the info to my email: miguel@vitalpbx.com

    Hi Miguel. I have replied…

    Thanks 🙂

    0
    Up
    0
    Down

    The steps to fix this issue were:

    1. vitalpbx –build-db (I ran this command to check if the database was fully populated)
    2. vitalpbx –dump-conf (I ran this command to delete all the configurations and re-build again)
    0
    TrustedbyU
    Participant
    Up
    0
    Down
    Posted by: mrivera

    The steps to fix this issue were:

    1. vitalpbx –build-db (I ran this command to check if the database was fully populated)
    2. vitalpbx –dump-conf (I ran this command to delete all the configurations and re-build again)

    I’m pleased to say that CDR reporting and call recording is working as intended now. 

    Many thanks 😀

    0
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.