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.

1 extension voicemail or foward stop working after update

Discussion in '3CX Phone System - General' started by 805tech, Dec 6, 2013.

Thread Status:
Not open for further replies.
  1. 805tech

    Joined:
    Aug 30, 2013
    Messages:
    39
    Likes Received:
    0
    So far we found 1 remote extension voicemail and forwarding rule stopped working. I call the extension and it rings there but after 4 rings the phone says Not Acceptable and beeps 3 times and hangs up. I have even tried deleting the extension and recreating it. I looked at the log and this is what is says
    Leg L:1007.1[Extn] is terminated: Cause: BYE from PBX
    06-Dec-2013 11:20:33.845 Leg L:1007.2[Extn] is terminated: Cause: 302 Moved Temporarily/INVITE from 162.XXX.XXX.XXX:5065
    06-Dec-2013 11:20:33.845 [CM503003]: Call(C:1007): Call to <sip:360@68.XXX.XXX.XXX:5060> has failed; Cause: 302 Moved Temporarily/INVITE from 162.XXX.XXXX.XXX:5065
    06-Dec-2013 11:20:33.845 [CM503020]: Call(C:1007): Normal call termination. Call originator: Extn:358. Reason: Terminated
    06-Dec-2013 11:20:33.845 L:1007.1[Extn] failed to reach Extn:360, reason Redirected
    06-Dec-2013 11:20:33.845 [CM503014]: Call(C:1007): No known route from Extn:358 to target: <sip:805XXXXXXX@68.XXX.XXX.XXX:5060>
    06-Dec-2013 11:20:33.845 [Flow] Target endpoint for 805XXXXXXX can not be built!
    06-Dec-2013 11:20:33.845 [CM503006]: Call(C:1007): Diverted to: <sip:805XXXXXXX@68.XXX.XXX.XXX:5060>
    06-Dec-2013 11:20:33.844 Call to T:Extn:360@[Dev:sip:360@162.XXX.XXX.XXX:5065] from L:1007.1[Extn] failed, cause: Cause: 302 Moved Temporarily/INVITE from 162.XXX.XXX.XXX:5065
    06-Dec-2013 11:20:21.165 [CM503025]: Call(C:1007): Calling T:Extn:360@[Dev:sip:360@162.XXX.XXX.XXX:5065] for L:1007.1[Extn]
    06-Dec-2013 11:20:21.116 [CM503027]: Call(C:1007): From: Extn:358 ("Ceasar Martinez" <sip:358@192.168.XXX.XXX:5060>) to T:Extn:360@[Dev:sip:360@162.XXX.XXX.XXX:5065]
    06-Dec-2013 11:20:21.116 [CM503004]: Call(C:1007): Route 1: from L:1007.1[Extn] to T:Extn:360@[Dev:sip:360@162.XXX.XXX.XXX:5065]
    06-Dec-2013 11:20:21.115 [CM503001]: Call(C:1007): Incoming call from Extn:358 to <sip:360@192.168.XXX.XXX:5060>
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,116
    Likes Received:
    329
    Re: 1 extension voicemail or foward stop working after updat

    Are you certain that our outbound rules allow a call from this extension to 805XXXXXXX, the log says NO.

    You fail to mention exactly what "update" you did? Operating System, 3CX version, etc....
     
  3. 805tech

    Joined:
    Aug 30, 2013
    Messages:
    39
    Likes Received:
    0
    Re: 1 extension voicemail or foward stop working after updat

    We have Server 2008 R2 and 3CX V12 and went from SP2 to SP3 on the update. And we have other setups that are exactly the same as this one and they work.
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,116
    Likes Received:
    329
    Re: 1 extension voicemail or foward stop working after updat

    And does an outbound call dialled from extension 358 to 805XXXXXXX work?
     
  5. 805tech

    Joined:
    Aug 30, 2013
    Messages:
    39
    Likes Received:
    0
    Re: 1 extension voicemail or foward stop working after updat

    yes it does
     
Thread Status:
Not open for further replies.