IVR Stopped Working

Discussion in '3CX Phone System - General' started by Jonners59, May 29, 2010.

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

    Jonners59 New Member

    Joined:
    Apr 21, 2009
    Messages:
    129
    Likes Received:
    0
    I have had my 3CX working for some time now. I changed the IVR message on one of the digital receptionists last week, but since then I am not getting any IVR message at all.

    I have tried reinstalling the message,I have tried moving it, I have tried reboots and have even tried uninstalling 3CX and re installing, but it makes no difference. It's really odd!

    The way I have things set up is 2 telephone lines on to a GWX, one for work and one for home. The Home one has the IVR. The call is routed such:
    Call comes in to vExtension 801 (Hunt Group) and calls 4 extensions symaltaniously. If the call is not picked up it then switches to DR v Extension 806... I note that in the System Extension Status 806 lights up, but then it jumps to voice mail - the correct vMail should nothing be selected.

    It is as if it can not find the message (WAV file) and just ignores the full process.

    Example log below:
    20:41:07.725 [CM503008]: Call(1): Call is terminated
    20:41:06.581 Active calls counted toward license limit: [1]
    20:40:55.895 [MS210005] C:1.4:Answer provided. Connection(proxy mode):127.0.0.1:7006(7007)
    20:40:55.892 [MS210001] C:1.1:Answer received. RTP connection[unsecure]: 192.168.1.95:5032(5033)
    20:40:55.885 Remote SDP is set for legC:1.1
    20:40:55.785 [CM503007]: Call(1): Device joined: sip:900@127.0.0.1:40600;rinstance=7046a5771872d83f
    20:40:55.779 [MS210004] C:1.1:Offer provided. Connection(proxy mode): 192.168.1.50:7000(7001)
    20:40:55.775 [MS210000] C:1.4:Offer received. RTP connection: 127.0.0.1:40612(40613)
    20:40:55.772 Remote SDP is set for legC:1.4
    20:40:55.769 [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]
    20:40:55.769 [CM503002]: Call(1): Alerting sip:900@127.0.0.1:40600;rinstance=7046a5771872d83f
    20:40:55.596 [CM503025]: Call(1): Calling Ext:Ext.900@[Dev:sip:900@127.0.0.1:40600;rinstance=7046a5771872d83f]
    20:40:55.540 [CM503004]: Call(1): Route 1: Ext:Ext.900@[Dev:sip:900@127.0.0.1:40600;rinstance=7046a5771872d83f]
    20:40:55.538 [CM503010]: Making route(s) to <sip:111@127.0.0.1:5060;user=vmail>
    20:40:55.532 Refer: from=<sip:806@127.0.0.1:5060>;tag=ae3a3d26; to=<sip:unknown@127.0.0.1:5060>;tag=8c676d20; RefTo=<sip:111@127.0.0.1:5060;user=vmail>
    20:40:55.312 [MS210003] C:1.3:Answer provided. Connection(transcoding mode[unsecure]):127.0.0.1:7004(7005)
    20:40:55.309 [MS210001] C:1.1:Answer received. RTP connection[unsecure]: 192.168.1.95:5032(5033)
    20:40:55.306 Remote SDP is set for legC:1.1
    20:40:55.195 [MS210002] C:1.1:Offer provided. Connection(transcoding mode): 192.168.1.50:7000(7001)
    20:40:55.193 [MS210000] C:1.3:Offer received. RTP connection: 127.0.0.1:40610(40611)
    20:40:55.189 Remote SDP is set for legC:1.3
    20:40:50.483 Session 139 of leg C:1.1 is confirmed
    20:40:50.403 [CM503007]: Call(1): Device joined: sip:806@127.0.0.1:40600;rinstance=fe2b0e0c670dded8
    20:40:50.397 [CM503007]: Call(1): Device joined: sip:10003@192.168.1.95:5064;transport=udp
    20:40:50.392 [MS210005] C:1.1:Answer provided. Connection(proxy mode):192.168.1.50:7000(7001)
    20:40:50.389 [MS210001] C:1.3:Answer received. RTP connection[unsecure]: 127.0.0.1:40610(40611)
    20:40:50.386 Remote SDP is set for legC:1.3
    20:40:50.381 [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]
    20:40:50.380 [CM503002]: Call(1): Alerting sip:806@127.0.0.1:40600;rinstance=fe2b0e0c670dded8
    20:40:50.298 [CM503003]: Call(1): Call to sip:110@192.168.1.50 has failed; Cause: 487 Request Cancelled; from IP:192.168.1.90:5060
    20:40:50.180 [CM503025]: Call(1): Calling Ext:Ext.806@[Dev:sip:806@127.0.0.1:40600;rinstance=fe2b0e0c670dded8]
    20:40:50.176 [MS210004] C:1.3:Offer provided. Connection(proxy mode): 127.0.0.1:7004(7005)
    20:40:50.115 [CM503005]: Call(1): Forwarding: Ext:Ext.806@[Dev:sip:806@127.0.0.1:40600;rinstance=fe2b0e0c670dded8]
    20:40:34.575 Active calls counted toward license limit: [1]
    20:40:30.992 [CM505001]: Ext.110: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [A580 IP022230000000] PBX contact: [sip:110@192.168.1.50:5060]
    20:40:30.992 [CM503002]: Call(1): Alerting sip:110@192.168.1.90:5060
    20:40:30.094 [CM503025]: Call(1): Calling RingAll801:110Ext.110105Ext.105111Ext.111101Ext.101@[Dev:sip:110@192.168.1.90:5060]
    20:40:30.090 [MS210006] C:1.2:Offer provided. Connection(by pass mode): 192.168.1.95:5032(5033)
    20:40:30.029 [CM503004]: Call(1): Route 1: RingAll801:110Ext.110105Ext.105111Ext.111101Ext.101@[Dev:sip:110@192.168.1.90:5060]
    20:40:29.950 [MS210000] C:1.1:Offer received. RTP connection: 192.168.1.95:5032(5033)
    20:40:29.948 [CM503010]: Making route(s) to <sip:801@192.168.1.50:5060>
    20:40:29.919 Remote SDP is set for legC:1.1
    20:40:29.914 [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:7) 0.3.2.3] PBX contact: [sip:10003@192.168.1.50:5060]
    20:40:29.909 [CM503001]: Call(1): Incoming call from unknown@(Ln.10003@GWX 4104) to <sip:801@192.168.1.50:5060>
    20:40:29.640 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10003 forwards to DN:801
    20:40:29.629 Looking for inbound target: called=444; caller=unknown
    20:40:29.623 [CM500002]: Info on incoming INVITE:
    INVITE sip:444@192.168.1.50 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.95:5064;branch=z9hG4bK3cb1c8273c50f015
    Max-Forwards: 70
    Contact: <sip:10003@192.168.1.95:5064;transport=udp>
    To: <sip:444@192.168.1.50>
    From: <sip:unknown@192.168.1.50>;tag=ed06d8975f26bb63
    Call-ID: ae434d52e0600855f3736a254f641513@192.168.1.95
    CSeq: 2377 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.50",nonce="414d535c0211fead47:deae618331f6987b1606c5b1894bf2a7",response="584407e46805d4c034a4de8f255ab2dd"
    Supported: replaces, timer, path
    User-Agent: Grandstream GXW4104 (HW 1.1, Ch:7) 0.3.2.3
    Content-Length: 0
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,375
    Likes Received:
    231
    It seems to take 12 seconds to realize that something is wrong. Does the same thing happen if you dial 900 directly?
    Did you try re-installing and then applying an older backup?
     
  3. Jonners59

    Jonners59 New Member

    Joined:
    Apr 21, 2009
    Messages:
    129
    Likes Received:
    0
    When I re installed I used the last upgrade. I'll try an older one. I'll try Thursday eve
     
    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
    Ok, did a restore from an earlier backup point and it worked. Tried the new wav file, it accepts it and I can even "play" it from within the extension setting, but when a call comes in, it does not work again. I have gone back to the old message until this is fixed.

    Why does it not pick up this wav file and play it when a call comes in?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Hi there,

    Why dont you try and use another wav file maybe the PBX for whatever reason does not like it
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.