Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Hangup on voicemail or digital recep.

Discussion in '3CX Phone System - General' started by robconley, Oct 22, 2009.

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

    Joined:
    Oct 21, 2009
    Messages:
    4
    Likes Received:
    0
    Running into a issue that I can seem to resolve for days.

    I am sure once we roll this out that we will need to upgade to the paid version but need to show a true working demo first.

    Everytime a digital recording, for example voice mail or a digital recpection, it just hangs up on the caller. This happens from all locations. We are using a mix of SNOM 360 phones, Grandstreem and the 3CX Voip phone,, all have the same effect. Dialing 999 for example will result in a hangup, fowarding to voice mail will hang up, fowarding to a digital recption will hang up, All other functions seem to be working.

    3CX is installed on a new Windows 2008 R2 64bit Server in a datacenter located in NYC.

    Below is an example of a 3cx voip phone calling 999

    08:55:00.651 [CM503008]: Call(2): Call is terminated
    08:54:58.250 Session 63 of leg C:2.1 is confirmed
    08:54:57.919 [CM503007]: Call(2): Device joined: sip:999@127.0.0.1:40600;rinstance=49afb596ce8177a0
    08:54:57.917 [CM503007]: Call(2): Device joined: sip:101@127.0.0.1:58192;rinstance=9a1d523d50e66dda
    08:54:57.916 [MS210003] C:2.1:Answer provided. Connection(transcoding mode[unsecure]):69.90.156.18:7004(7005)
    08:54:57.915 [MS210001] C:2.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40612(40613)
    08:54:57.914 Remote SDP is set for legC:2.2
    08:54:57.911 [CM505001]: Ext.999: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:999@127.0.0.1:5060]
    08:54:57.911 [CM503002]: Call(2): Alerting sip:999@127.0.0.1:40600;rinstance=49afb596ce8177a0
    08:54:57.772 [CM503025]: Call(2): Calling Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=49afb596ce8177a0]
    08:54:57.771 [MS210002] C:2.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7006(7007)
    08:54:57.736 [CM503004]: Call(2): Route 1: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=49afb596ce8177a0]
    08:54:57.735 [CM503010]: Making route(s) to <sip:999@69.90.123.36:5060>
    08:54:57.735 [MS210000] C:2.1:Offer received. RTP connection: 69.90.123.34:10006(10007)
    08:54:57.734 Remote SDP is set for legC:2.1
    08:54:57.734 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9530.0] PBX contact: [sip:101@69.90.123.34:5060]
    08:54:57.729 [CM503001]: Call(2): Incoming call from Ext.101 to <sip:999@69.90.123.36:5060>
    08:54:57.697 [CM500002]: Info on incoming INVITE:
    INVITE sip:999@69.90.123.36:5060 SIP/2.0
    Via: SIP/2.0/UDP 69.90.123.34:5080;branch=z9hG4bK-d8754z-c6058812c75cec69-1---d8754z-;rport=5080;received=69.90.123.36
    Via: SIP/2.0/UDP 173.63.206.213:60036;branch=z9hG4bK-d8754z-tunneltid-1---d8754z-;rport
    Via: SIP/2.0/UDP 127.0.0.1:58192;branch=z9hG4bK-d8754z-465be609793cb238-1---d8754z-;rport=58192
    Max-Forwards: 68
    Record-Route: <sip:3cxBridge@69.90.123.34:5080;user=proxy;uri="173.63.206.213:60036">
    Contact: <sip:101@127.0.0.1:58192;rinstance=9a1d523d50e66dda>
    To: <sip:999@69.90.123.36:5060>
    From: "3CXPhone"<sip:101@69.90.123.36:5060>;tag=8e39f77e
    Call-ID: NzdkZTI0OGE1ZjQ1ZmVkODUyMjQzNzhhYjBlYzA0ZWQ.
    CSeq: 2 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    Proxy-Authorization: Digest username="101",realm="3CXPhoneSystem",nonce="414d535c00f0e72130:02eeba93c11e3d8fcc304db02ef20150",uri="sip:999@69.90.123.36:5060",response="fc97ede7d0206232bff88fbe16a27aa5",algorithm=MD5
    Supported: replaces
    User-Agent: 3CXVoipPhone 4.0.9530.0
    Content-Length: 0

    08:54:26.027 [CM503008]: Call(1): Call is terminated
    08:54:23.201 Session 53 of leg C:1.1 is confirmed
    08:54:22.916 [CM503007]: Call(1): Device joined: sip:999@127.0.0.1:40600;rinstance=49afb596ce8177a0
    08:54:22.914 [CM503007]: Call(1): Device joined: sip:101@127.0.0.1:58192;rinstance=9a1d523d50e66dda
    08:54:22.912 [MS210003] C:1.1:Answer provided. Connection(transcoding mode[unsecure]):69.90.156.18:7000(7001)
    08:54:22.911 [MS210001] C:1.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40610(40611)
    08:54:22.910 Remote SDP is set for legC:1.2
    08:54:22.907 [CM505001]: Ext.999: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:999@127.0.0.1:5060]
    08:54:22.907 [CM503002]: Call(1): Alerting sip:999@127.0.0.1:40600;rinstance=49afb596ce8177a0
    08:54:22.720 [CM503025]: Call(1): Calling Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=49afb596ce8177a0]
    08:54:22.719 [MS210002] C:1.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7002(7003)
    08:54:22.669 [CM503004]: Call(1): Route 1: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=49afb596ce8177a0]
    08:54:22.669 [CM503010]: Making route(s) to <sip:999@69.90.123.36:5060>
    08:54:22.668 [MS210000] C:1.1:Offer received. RTP connection: 69.90.123.34:10002(10003)
    08:54:22.667 Remote SDP is set for legC:1.1
    08:54:22.667 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9530.0] PBX contact: [sip:101@69.90.123.34:5060]
    08:54:22.659 [CM503001]: Call(1): Incoming call from Ext.101 to <sip:999@69.90.123.36:5060>
    08:54:22.500 [CM500002]: Info on incoming INVITE:
    INVITE sip:999@69.90.123.36:5060 SIP/2.0
    Via: SIP/2.0/UDP 69.90.123.34:5080;branch=z9hG4bK-d8754z-b50d87257d079d22-1---d8754z-;rport=5080;received=69.90.123.36
    Via: SIP/2.0/UDP 173.63.206.213:60036;branch=z9hG4bK-d8754z-tunneltid-1---d8754z-;rport
    Via: SIP/2.0/UDP 127.0.0.1:58192;branch=z9hG4bK-d8754z-f805c751e638946f-1---d8754z-;rport=58192
    Max-Forwards: 68
    Record-Route: <sip:3cxBridge@69.90.123.34:5080;user=proxy;uri="173.63.206.213:60036">
    Contact: <sip:101@127.0.0.1:58192;rinstance=9a1d523d50e66dda>
    To: <sip:999@69.90.123.36:5060>
    From: "3CXPhone"<sip:101@69.90.123.36:5060>;tag=814a5b7a
    Call-ID: NThjZmU1Yjg5ZmRjMDQ5MDUyYmRkMWI3MjBkYjgxOTg.
    CSeq: 2 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    Proxy-Authorization: Digest username="101",realm="3CXPhoneSystem",nonce="414d535c00f0e6fe96:68be242b056f03faac95da7de9227941",uri="sip:999@69.90.123.36:5060",response="274c5a003a5f32199b648eb85ae903d7",algorithm=MD5
    Supported: replaces
    User-Agent: 3CXVoipPhone 4.0.9530.0
     
  2. robconley

    Joined:
    Oct 21, 2009
    Messages:
    4
    Likes Received:
    0
    Version is: 8.0.9532.46468
     
  3. robconley

    Joined:
    Oct 21, 2009
    Messages:
    4
    Likes Received:
    0
    I will try to reinstall again, If not, well back to asterisk or trixbox...
     
  4. KerryG

    KerryG Active Member

    Joined:
    Jun 19, 2009
    Messages:
    960
    Likes Received:
    0
    This is very odd behavior as obviously most people aren't having the problem. I believe the issue is Server 2008 R2 64bit. Have you tried it on something else like Windows XP Pro. My system I could install Server 2008 R2 64bit on is out on loan at the moment so I can't test it myself but I have seen a few other strange issues with that particular variant of the server OS.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. robconley

    Joined:
    Oct 21, 2009
    Messages:
    4
    Likes Received:
    0
    A full uninstall and reinstall fixed the issue, only thing I have not done yet is the Skype gateway. Starting to wonder if that did it, we will find out.
     
Thread Status:
Not open for further replies.