V5 and "silent voice mail" on internal calls

Discussion in '3CX Phone System - General' started by npiersma, Dec 9, 2007.

  1. npiersma

    Joined:
    Dec 30, 2006
    Messages:
    55
    Likes Received:
    0
    Hi all,

    Just updated to version 5 from version 3, not a very smooth transition. Had a lot of problems with the database. We did an inplace upgrade and none of the phones were working anymore. I figured, let's delete one extention and recreate it, no go....deletion went fine, re-adding gave a "database duplicate object"... I did a clean install and restored the database.... Same problem. So i thought, let's start over, a clean config. So I reconfigured my extentions and voip providers. Everything works fine now... But I've got one issue left. Voicemail doesn't seem to work anymore. (I did register my key).

    when I call internally to an ext that's forwared to a VM I get this message:

    19:31:11.755 MediaServerReporting::SetRemoteParty [MS210003] C:7.1:Answer provided. Connection(transcoding mode):82.95.255.231:1260(1261)
    19:31:11.755 CallCtrl::eek:nLegConnected [CM503007]: Call(7): Device joined: sip:127@10.0.3.1:5060
    19:31:10.787 CallCtrl::eek:nLegConnected [CM503007]: Call(7): Device joined: sip:
    19:31:10.787 CallCtrl::eek:nRerouteReq [CM503005]: Call(7): Forwarding: IVR:RecordMessage@[Dev]
    19:30:55.723 Extension::printEndpointInfo [CM505001]: Ext.125: Device info: Device Identified: [Man: GrandStream;Mod: GXP-2000;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [Grandstream GXP2000 1.1.4.18] Transport: [sip:10.0.1.71:5060]
    19:30:55.723 CallCtrl::eek:nAnsweredCall [CM503002]: Call(7): Alerting sip:125@10.0.9.2:5060;transport=udp
    19:30:55.661 MediaServerReporting::SetRemoteParty [MS210006] C:7.2:Offer provided. Connection(by pass mode): 10.0.3.1:16386(16387)
    19:30:55.457 MediaServerReporting::SetRemoteParty [MS210000] C:7.1:Offer received. RTP connection: 10.0.3.1:16386(16387)
    19:30:55.457 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(7): Calling: Ext:125@[Dev:sip:125@10.0.9.2:5060;transport=udp]
    19:30:55.457 Extension::printEndpointInfo [CM505001]: Ext.127: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA922-5.1.15(a)] Transport: [sip:10.0.1.71:5060]
    19:30:55.395 CallCtrl::eek:nIncomingCall [CM503001]: Call(7): Incoming call from Ext.127 to "125"[sip:125@pi31voip1.piersma.net]

    When I call from a cell to the same extention I get this log (and a working voicemail)
    19:38:39.129 LineCfg::getInboundTarget [CM503010]: Inbound out-of-office hours' rule for LN:10003 forwards to DN:801
    19:38:39.129 Call::Terminate [CM503008]: Call(8): Call is terminated
    19:38:39.129 Call::Terminate [CM503008]: Call(8): Call is terminated
    19:38:39.114 LineCfg::getInboundTarget [CM503010]: Inbound out-of-office hours' rule for LN:10003 forwards to DN:801
    19:38:39.098 LineCfg::getInboundTarget [CM503010]: Inbound out-of-office hours' rule for LN:10003 forwards to DN:801
    19:38:20.130 LineCfg::getInboundTarget [CM503010]: Inbound out-of-office hours' rule for LN:10003 forwards to DN:801
    19:38:20.114 MediaServerReporting::SetRemoteParty [MS210003] C:8.1:Answer provided. Connection(transcoding mode):82.95.255.231:1274(1275)
    19:38:20.114 CallCtrl::eek:nLegConnected [CM503007]: Call(8): Device joined: sip:0614248182@80.69.83.64
    19:38:18.974 CallCtrl::eek:nLegConnected [CM503007]: Call(8): Device joined: sip:
    19:38:18.974 LineCfg::getInboundTarget [CM503010]: Inbound out-of-office hours' rule for LN:10003 forwards to DN:801
    19:38:18.958 CallCtrl::eek:nRerouteReq [CM503005]: Call(8): Forwarding: IVR:RecordMessage@[Dev]
    19:37:48.850 CallCtrl::eek:nAnsweredCall [CM503002]: Call(8): Alerting sip:125@10.0.9.2:5060;transport=udp
    19:37:48.741 CallCtrl::eek:nAnsweredCall [CM503002]: Call(8): Alerting sip:108@10.2.16.5:5060;transport=udp
    19:37:48.741 MediaServerReporting::SetRemoteParty [MS210002] C:8.3:Offer provided. Connection(transcoding mode): 82.95.255.231:1278(1279)
    19:37:48.522 MediaServerReporting::SetRemoteParty [MS210002] C:8.2:Offer provided. Connection(transcoding mode): 82.95.255.231:1276(1277)
    19:37:48.319 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(8): Calling: RingAll:801@[Dev:sip:108@10.2.16.5:5060;transport=udp, Dev:sip:125@10.0.9.2:5060;transport=udp]
    19:37:48.303 MediaServerReporting::SetRemoteParty [MS210000] C:8.1:Offer received. RTP connection: 80.69.83.64:19534(19535)
    19:37:48.288 Line::printEndpointInfo [CM505003]: Provider:[AL 3319246] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Adaline_NL_PBX] Transport: [sip:10.0.1.71:5060]
    19:37:48.288 LineCfg::getInboundTarget [CM503010]: Inbound out-of-office hours' rule for LN:10003 forwards to DN:801
    19:37:48.257 CallCtrl::eek:nIncomingCall [CM503001]: Call(8): Incoming call from 0614248182@(Ln.10003@AL 3319246) to [sip:801@pi31voip1.piersma.net:5060]
    19:37:47.975 LineCfg::getInboundTarget [CM503010]: Inbound out-of-office hours' rule for LN:10003 forwards to DN:801
     
  2. npiersma

    Joined:
    Dec 30, 2006
    Messages:
    55
    Likes Received:
    0
    Well, just an update.

    I've managed to get vmail to email working, so we can do business. But leaving an internal vmail for an extention isn't working. Same goes for listening to voicemails via 999. The extention does get connected when dialing 999. but stays yellow in the status window.

    125 00:05:22
    Status: Connected: (127)

    I did play around with "pbx delivers audio" but that doesn't seem to matter.

    Anyway, at the moment not a very nice stable version, but we can manage.
     
  3. Pentangle

    Pentangle Member

    Joined:
    Dec 6, 2007
    Messages:
    261
    Likes Received:
    0
    You sure it's not a firewall issue?
     
  4. npiersma

    Joined:
    Dec 30, 2006
    Messages:
    55
    Likes Received:
    0
    Dear Pentangle,

    We're pritty sure it's not a firewall issue. Phones are connected in one VLAN (voice) 3CX server is installed in other VLAN (SeRVERS). There connected to Cisco 3700 series switches with l3 routing, but no filtering is done.

    Niels
     
  5. nateb

    Joined:
    Oct 19, 2007
    Messages:
    68
    Likes Received:
    0
    voice mail

    how did you fix the voice mail problem? i think i'm having the same problem.
     
  6. kwoodrin

    Joined:
    Sep 7, 2007
    Messages:
    4
    Likes Received:
    0
    I'm having the same issue. Removed v3 and did a clean install of v5, then restored the database. Everything worked fine except I have no access to check voicemail anymore for any extensions. When we dial the number to check voicemail, it says "Please enter extension" and then no matter what you enter it hangs up.

    Let me know if you find anything out on this--it is very disruptive. Thanks.
     
  7. kwoodrin

    Joined:
    Sep 7, 2007
    Messages:
    4
    Likes Received:
    0
    Update, this apparently has nothing to do with Voicemail but is part of a much bigger issue where apparently v5 doesn't recognize DTMF at all. I am using GXP-2000 and have DTMF set up to be delivered "in-audio"
     
  8. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    I am also having this problem. this needs to be addressed immediately. I had a working production product and now I do not.

    If I am to retain this customer with this prodcut this needs to be fixed.

    I also have a problem with the Auto Attendent after the upgrade. If you delete/add/change an extension it will not allow for modifiction of the attendent.
     
  9. Pentangle

    Pentangle Member

    Joined:
    Dec 6, 2007
    Messages:
    261
    Likes Received:
    0
    I have a working version of v5 with working voicemail on the LAN when using the 3CX VoIP Client. I can't hear the DTMF tones when I press the buttons, but the voicemail certainly does work.

    HTH.
     
  10. nateb

    Joined:
    Oct 19, 2007
    Messages:
    68
    Likes Received:
    0
    FIXED

    ok , to fix it, manage lines, edit gateway / provider properties, then edit Gateway capabilities , check supports re-invite , and supports replace header.

    That Fixed it for me!!
     

Share This Page