Lost voice mail messages

Discussion in '3CX Phone System - General' started by Jonners59, Nov 1, 2010.

Thread Status:
Not open for further replies.
  1. Jonners59

    Jonners59 New Member

    Joined:
    Apr 21, 2009
    Messages:
    129
    Likes Received:
    0
    I have been using 3CX on Vista for 2 years now. I recently upgraded my Server to run Ubuntu 10.4 (Linux). I installed Sun's VirtualBox and set up a virtual machine within which I run Windows 7. I then installed the latest version of 3CX in this virtual machine/Windows7 environment and used the back up config to setup the new 3CX system. It works great, but for one thing.... When voice mail messages are left by callers, it does not seem to exist. The message is not in the users account, and is not sent by eMail as a wav file as it used to.

    Where have they all gone?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. Jonners59

    Jonners59 New Member

    Joined:
    Apr 21, 2009
    Messages:
    129
    Likes Received:
    0
    Any help please???????
    Code:
    19:39:47.707 
     	
    Currently active calls - 1: [24] 
     	
    19:39:17.691 
     	
    Currently active calls - 1: [24] 
     	
    19:39:05.906 
     	
    Session 52115 of leg C:24.1 is confirmed 
     	
    19:39:05.617 
     	
    [CM503007]: Call(24): Device joined: sip:844231085@voiptalk.org:5060 
     	
    19:39:05.577 
     	
    [CM503007]: Call(24): Device joined: sip:100@192.168.1.91:5060 
     	
    19:39:05.568 
     	
    [MS210001] C:24.2:Answer received. RTP connection[unsecure]: 77.240.48.210:41008(41009) 
     	
    19:39:05.563 
     	
    Remote SDP is set for legC:24.2 
     	
    19:38:50.705 
     	
    [MS210003] C:24.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.1.51:7100(7101) 
     	
    19:38:50.700 
     	
    [MS210001] C:24.2:Answer received. RTP connection[unsecure]: 77.240.48.210:41008(41009) 
     	
    19:38:50.694 
     	
    Remote SDP is set for legC:24.2 
     	
    19:38:50.688 
     	
    [CM505003]: Provider:[VoIPTalk] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:844231085@93.97.190.219:5060] 
     	
    19:38:50.688 
     	
    [CM503002]: Call(24): Alerting sip:844231085@voiptalk.org:5060 
     	
    19:38:50.089 
     	
    [CM503025]: Call(24): Calling VoIPline:02086603837@(Ln.10005@VoIPTalk)@[Dev:sip:844231085@voiptalk.org:5060] 
     	
    19:38:50.073 
     	
    [MS210002] C:24.2:Offer provided. Connection(transcoding mode): 93.97.190.219:9016(9017) 
     	
    19:38:49.917 
     	
    [CM503004]: Call(24): Route 3: PSTNline:99102086603837@(Ln.10001@GWX 4104)@[Dev:sip:10001@192.168.1.95:5060;transport=udp,Dev:sip:10002@192.168.1.95:5062;transport=udp,Dev:sip:10003@192.168.1.95:5064;transport=udp,Dev:sip:10004@192.168.1.95:5066;transport=udp] 
     	
    19:38:49.915 
     	
    [CM503004]: Call(24): Route 2: VoIPline:02086603837@(Ln.10005@VoIPTalk)@[Dev:sip:844231085@voiptalk.org:5060] 
     	
    19:38:49.915 
     	
    [CM503004]: Call(24): Route 1: VoIPline:02086603837@(Ln.10005@VoIPTalk)@[Dev:sip:844231085@voiptalk.org:5060] 
     	
    19:38:49.912 
     	
    [CM503010]: Making route(s) to <sip:02086603837@192.168.1.51;user=phone> 
     	
    19:38:49.912 
     	
    [MS210000] C:24.1:Offer received. RTP connection: 192.168.1.91:5008(5009) 
     	
    19:38:49.906 
     	
    Remote SDP is set for legC:24.1 
     	
    19:38:49.905 
     	
    [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [S685IP022230000000] PBX contact: [sip:100@192.168.1.51:5060] 
     	
    19:38:49.833 
     	
    [CM503001]: Call(24): Incoming call from Ext.100 to <sip:02086603837@192.168.1.51;user=phone> 
     	
    19:38:49.809 
     	
    [CM500002]: Info on incoming INVITE: 
     	
     
     	
    INVITE sip:02086603837@192.168.1.51;user=phone SIP/2.0 
     	
     
     	
    Via: SIP/2.0/UDP 192.168.1.91:5060;branch=z9hG4bK3b80abae70d6bda82a8c8650573daf4a;rport=5060 
     	
     
     	
    Max-Forwards: 70 
     	
     
     	
    Contact: <sip:100@192.168.1.91:5060> 
     	
     
     	
    To: <sip:02086603837@192.168.1.51;user=phone> 
     	
     
     	
    From: "Office"<sip:100@192.168.1.51>;tag=602877018 
     	
     
     	
    Call-ID: 1852787869@192_168_1_91 
     	
     
     	
    CSeq: 3 INVITE 
     	
     
     	
    Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY 
     	
     
     	
    Proxy-Authorization: Digest username="100",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:02086603837@192.168.1.51;user=phone",nonce="414d535c02e24b4959:e52e848c8cefc07f76762b334dd416c7",response="1fd564b0b35f1a95ae5d718c0eb6ba98" 
     	
     
     	
    Supported: replaces 
     	
     
     	
    User-Agent: S685IP022230000000 
     	
     
     	
    Allow-Events: message-summary, refer, talk 
     	
     
     	
    Content-Length: 0 
     	
     
     	
     
     	
    19:38:47.613 
     	
    Currently active calls [none] 
     	
    19:38:17.373 
     	
    Currently active calls [none] 
     	
    19:37:47.306 
     	
    Currently active calls [none] 
     	
    19:37:17.221 
     	
    Currently active calls [none] 
     	
    19:36:47.120 
     	
    Currently active calls [none] 
     	
    19:36:16.958 
     	
    Currently active calls [none] 
     	
    19:36:09.354 
     	
    [CM503008]: Call(23): Call is terminated 
     	
    19:35:46.845 
     	
    Currently active calls - 1: [23] 
     	
    19:35:39.597 
     	
    [MS210005] C:23.5:Answer provided. Connection(proxy mode):127.0.0.1:7098(7099) 
     	
    19:35:39.588 
     	
    [MS210001] C:23.1:Answer received. RTP connection[unsecure]: 192.168.1.95:5020(5021) 
     	
    19:35:39.583 
     	
    Remote SDP is set for legC:23.1 
     	
    19:35:39.515 
     	
    [CM503007]: Call(23): Device joined: sip:900@127.0.0.1:40600;rinstance=9540f42d92b18ac3 
     	
    19:35:39.508 
     	
    [MS210004] C:23.1:Offer provided. Connection(proxy mode): 192.168.1.51:7092(7093) 
     	
    19:35:39.500 
     	
    [MS210000] C:23.5:Offer received. RTP connection: 127.0.0.1:40628(40629) 
     	
    19:35:39.495 
     	
    Remote SDP is set for legC:23.5 
     	
    19:35:39.492 
     	
    [CM505001]: Ext.900: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:900@127.0.0.1:5060] 
     	
    19:35:39.492 
     	
    [CM503002]: Call(23): Alerting sip:900@127.0.0.1:40600;rinstance=9540f42d92b18ac3 
     	
    19:35:39.298 
     	
    [CM503025]: Call(23): Calling Ext:Ext.900@[Dev:sip:900@127.0.0.1:40600;rinstance=9540f42d92b18ac3] 
     	
    19:35:39.211 
     	
    [CM503005]: Call(23): Forwarding: Ext:Ext.900@[Dev:sip:900@127.0.0.1:40600;rinstance=9540f42d92b18ac3] 
     	
    19:35:19.691 
     	
    [CM505003]: Provider:[VoIPTalk] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:844231085@93.97.190.219:5060] 
     	
    19:35:19.691 
     	
    [CM503002]: Call(23): Alerting sip:844231085@voiptalk.org:5060 
     	
    19:35:19.093 
     	
    [CM503025]: Call(23): Calling HuntGrp809:10607770740133@(Ln.10005@VoIPTalk)@[Dev:sip:844231085@voiptalk.org:5060] 
     	
    19:35:19.080 
     	
    [MS210002] C:23.4:Offer provided. Connection(transcoding mode): 93.97.190.219:9014(9015) 
     	
    19:35:18.906 
     	
    [CM503004]: Call(23): Route 1: HuntGrp809:10607770740133@(Ln.10005@VoIPTalk)@[Dev:sip:844231085@voiptalk.org:5060] 
     	
    19:35:18.874 
     	
    [CM503010]: Making route(s) to <sip:809@127.0.0.1:5060> 
     	
    19:35:18.865 
     	
    Refer: from=<sip:806@127.0.0.1:5060>;tag=770ca042; to=":Home"<sip:unknown@127.0.0.1:5060>;tag=4c49e96a; RefTo=<sip:809@127.0.0.1:5060> 
     	
    19:35:18.655 
     	
    [MS210003] C:23.3:Answer provided. Connection(transcoding mode[unsecure]):127.0.0.1:7096(7097) 
     	
    19:35:18.648 
     	
    [MS210001] C:23.1:Answer received. RTP connection[unsecure]: 192.168.1.95:5020(5021) 
     	
    19:35:18.641 
     	
    Remote SDP is set for legC:23.1 
     	
    19:35:18.534 
     	
    [MS210002] C:23.1:Offer provided. Connection(transcoding mode): 192.168.1.51:7092(7093) 
     	
    19:35:18.530 
     	
    [MS210000] C:23.3:Offer received. RTP connection: 127.0.0.1:40626(40627) 
     	
    19:35:18.515 
     	
    Remote SDP is set for legC:23.3 
     	
    19:35:16.804 
     	
    Currently active calls - 1: [23] 
     	
    19:34:50.687 
     	
    Session 52057 of leg C:23.1 is confirmed 
     	
    19:34:50.634 
     	
    [CM503007]: Call(23): Device joined: sip:806@127.0.0.1:40600;rinstance=cb269b8137a0818e 
     	
    19:34:50.601 
     	
    [CM503007]: Call(23): Device joined: sip:10003@192.168.1.95:5064;transport=udp 
     	
    19:34:50.595 
     	
    [MS210005] C:23.1:Answer provided. Connection(proxy mode):192.168.1.51:7092(7093) 
     	
    19:34:50.581 
     	
    [MS210001] C:23.3:Answer received. RTP connection[unsecure]: 127.0.0.1:40626(40627) 
     	
    19:34:50.574 
     	
    Remote SDP is set for legC:23.3 
     	
    19:34:50.572 
     	
    [CM505001]: Ext.806: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:806@127.0.0.1:5060] 
     	
    19:34:50.572 
     	
    [CM503002]: Call(23): Alerting sip:806@127.0.0.1:40600;rinstance=cb269b8137a0818e 
     	
    19:34:50.396 
     	
    [CM503003]: Call(23): Call to sip:110@192.168.1.51 has failed; Cause: 487 Request Cancelled; from IP:192.168.1.91:5060 
     	
    19:34:50.285 
     	
    [CM503025]: Call(23): Calling Ext:Ext.806@[Dev:sip:806@127.0.0.1:40600;rinstance=cb269b8137a0818e] 
     	
    19:34:50.281 
     	
    [MS210004] C:23.3:Offer provided. Connection(proxy mode): 127.0.0.1:7096(7097) 
     	
    19:34:50.188 
     	
    [CM503005]: Call(23): Forwarding: Ext:Ext.806@[Dev:sip:806@127.0.0.1:40600;rinstance=cb269b8137a0818e] 
     	
    19:34:46.748 
     	
    Currently active calls - 1: [23] 
     	
    19:34:31.828 
     	
    [CM505001]: Ext.110: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [S685IP022230000000] PBX contact: [sip:110@192.168.1.51:5060] 
     	
    19:34:31.828 
     	
    [CM503002]: Call(23): Alerting sip:110@192.168.1.91:5060 
     	
    19:34:30.136 
     	
    [CM503025]: Call(23): Calling RingAll801:110Ext.110105Ext.105111Ext.111101Ext.101@[Dev:sip:110@192.168.1.91:5060] 
     	
    19:34:30.131 
     	
    [MS210006] C:23.2:Offer provided. Connection(by pass mode): 192.168.1.95:5020(5021) 
     	
    19:34:30.103 
     	
    [CM503004]: Call(23): Route 1: RingAll801:110Ext.110105Ext.105111Ext.111101Ext.101@[Dev:sip:110@192.168.1.91:5060] 
     	
    19:34:30.044 
     	
    [CM503010]: Making route(s) to <sip:801@169.254.56.187:5060> 
     	
    19:34:30.042 
     	
    [MS210000] C:23.1:Offer received. RTP connection: 192.168.1.95:5020(5021) 
     	
    19:34:30.037 
     	
    Remote SDP is set for legC:23.1 
     	
    19:34:30.037 
     	
    [CM505002]: Gateway:[GWX 4104] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4104 (HW 1.1, Ch:4) 1.3.4.7] PBX contact: [sip:10003@192.168.1.51:5060] 
     	
    19:34:29.966 
     	
    [CM503001]: Call(23): Incoming call from unknown@(Ln.10003@GWX 4104) to <sip:801@169.254.56.187:5060> 
     	
    19:34:29.932 
     	
    [CM503012]: Inbound out-of-office hours rule (unnamed) for 10003 forwards to DN:801 
     	
    19:34:29.929 
     	
    Looking for inbound target: called=444; caller=unknown 
     	
    19:34:29.905 
     	
    [CM500002]: Info on incoming INVITE: 
     	
     
     	
    INVITE sip:444@192.168.1.51 SIP/2.0 
     	
     
     	
    Via: SIP/2.0/UDP 192.168.1.95:5064;branch=z9hG4bKa83417e34f95bcc1 
     	
     
     	
    Max-Forwards: 70 
     	
     
     	
    Contact: <sip:10003@192.168.1.95:5064;transport=udp> 
     	
     
     	
    To: <sip:444@192.168.1.51> 
     	
     
     	
    From: <sip:unknown@192.168.1.51>;tag=23763860202790c2 
     	
     
     	
    Call-ID: 57e47bb29a012b7165e574d179f43907@192.168.1.95 
     	
     
     	
    CSeq: 9025 INVITE 
     	
     
     	
    Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK 
     	
     
     	
    Proxy-Authorization: Digest username="10003",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:444@192.168.1.51",nonce="414d535c02e24a4514:c577d054386858fa9567009ef9e348f1",response="e29318577a22ebcaef3c45495585197c" 
     	
     
     	
    Supported: replaces, timer, path 
     	
     
     	
    User-Agent: Grandstream GXW4104 (HW 1.1, Ch:4) 1.3.4.7 
     	
     
     	
    Content-Length: 0
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,500
    Likes Received:
    98
    - Check whether you've actually enabled recording on your new installation on your extension's settings.
    - Check Settings > General > Global options > Recording Path and set it a location of your liking.
    - Check Settings > General > Mail Server and see whether the settings you have entered there are correct.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Jonners59

    Jonners59 New Member

    Joined:
    Apr 21, 2009
    Messages:
    129
    Likes Received:
    0
    LeonidasG

    Many thanks for this... I resolved the saving messages... It would seem that, and logically the path to save the files disappeared. The field was blank, and after so long since I set things up, I forgot it was there. And what was great, all the messages we had missed were there too!

    Sending via eMail. That was not so good though.

    I use gMail, So the server is smtp.gmail.com
    Username is the eMail address and corresponding password. However it uses TLS encryption.

    Therefore to make it work, I had to use the smtp of my ISP. Not as tidy, but it worked.

    Many thankshttp://www.3cx.com/forums/posting.php?mode=edit&f=1&p=89874#
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. abc123

    abc123 Active Member

    Joined:
    Nov 9, 2009
    Messages:
    712
    Likes Received:
    1
    I had put in a feature request about TLS mail.

    As 3cx are using .net to write the program and .net has an ssl/tls setting it should be fairly straightforward to add the feature but i suspect it is lower on the priority list.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.