Rebound not working - fails on forward to IVR

Discussion in '3CX Phone System - General' started by dannothemanno, Apr 30, 2012.

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

    Joined:
    Apr 30, 2012
    Messages:
    2
    Likes Received:
    0
    Hello!

    I'm having an issue with Rebound that i'm hoping you folks can help me with.

    When I forward a call to my mobile (internal or external) it works fine. If I activate rebound, the caller is disconnected before they hear the "Say your name" prompt.

    I think it's failing when attempting to forward to the IVR to get the callers name.

    In the test below, I am calling from 103 to 101. 101 rings for the correct time, then the call is disconnected. Oddly the errors show that 101 is unregistered, but that is not the case. It shows as registered in 3cx, and works correctly.

    Code:
    22:15:29.253  [CM503003]: Call(18): Call to sip:101@192.168.124.9 has failed; Cause: 487 Request Cancelled; from IP:192.168.124.153:49204
    22:15:29.175  [CM503020]: Normal call termination. Reason: Not available
    22:15:29.175  [CM503016]: Call(18): Attempt to reach <sip:101@192.168.124.9:5060> failed. Reason: Not Registered
    22:15:29.175  [CM503016]: Call(18): Attempt to reach <sip:101@192.168.124.9:5060> failed. Reason: Not Registered
    22:15:29.175  [CM503017]: Call(18): Target is not registered: <sip:IVRForward@192.168.124.9:5060>
    22:15:27.300  [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Cisco-CP7941G/8.3.0] PBX contact: [sip:101@192.168.124.9:5060]
    22:15:27.300  [CM503002]: Call(18): Alerting sip:101@192.168.124.153:5060;transport=udp
    22:15:27.128  [CM503025]: Call(18): Calling Ext:Ext.101@[Dev:sip:101@192.168.124.153:5060;transport=udp]
    22:15:27.081  [CM503004]: Call(18): Route 1: Ext:Ext.101@[Dev:sip:101@192.168.124.153:5060;transport=udp]
    22:15:27.081  [CM503010]: Making route(s) to <sip:101@192.168.124.9:5060>
    22:15:27.081  [CM505001]: Ext.103: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 6.0.20943.0] PBX contact: [sip:103@192.168.124.9:5060]
    22:15:27.081  [CM503001]: Call(18): Incoming call from Ext.103 to <sip:101@192.168.124.9:5060>
    
    Thanks!
    Danno
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,570
    Likes Received:
    247
    You probably need to figure out why 3CX seems to think that extension 101 at 192.168.124.9:5060 is not registered. Whether you feel that it is or not, is not what counts, it's how 3CX sees it's status. I seem to recall it coming up before ,where that the status showing in the Windows Management Console 3CX is not reflecting the actual state of the device.

    I'm assuming that there is only one appearance of extension 101?

    Re-connect (power cycle) extension 101, confirm in the 3CX log that you see a registration, then try your call.

    If extension 101 is not re-registering every 30 minutes, then 3CX will assume it is no longer available, you might need to investigate why this is happening.
     
  3. dannothemanno

    Joined:
    Apr 30, 2012
    Messages:
    2
    Likes Received:
    0
    There is only one line appearance of 101.

    I tried it with another phone (3cx softphone) and got the same result. The Softphone had registered no more then 2 minutes before the test. In both cases, There is an "extension registered" but no message showing loss of registration, in the "Sever Event Log".

    In case it matters, I've now tested this on Cisco 7941, 7960, an SPA303 and now 3cx softphone, all with the same result.

    Result of the Softphone Test: (the softphone is at ext 103) and I am calling from 101.

    Code:
    23:52:57.275  [CM503003]: Call(2): Call to sip:103@192.168.124.9:5060 has failed; Cause: 487 Request Terminated; from IP:192.168.124.42:63697
    23:52:57.135  [CM503020]: Normal call termination. Reason: Not available
    23:52:57.135  [CM503016]: Call(2): Attempt to reach <sip:103@192.168.124.9> failed. Reason: Not Registered
    23:52:57.135  [CM503016]: Call(2): Attempt to reach <sip:103@192.168.124.9> failed. Reason: Not Registered
    23:52:57.135  [CM503017]: Call(2): Target is not registered: <sip:IVRForward@192.168.124.9:5060>
    23:52:54.228  [CM505001]: Ext.103: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 6.0.20943.0] PBX contact: [sip:103@192.168.124.9:5060]
    23:52:54.228  [CM503002]: Call(2): Alerting sip:103@192.168.124.42:63697;rinstance=6585bbb4e9f969f0
    23:52:54.088  [CM503025]: Call(2): Calling Ext:Ext.103@[Dev:sip:103@192.168.124.42:63697;rinstance=6585bbb4e9f969f0]
    23:52:54.041  [CM503004]: Call(2): Route 1: Ext:Ext.103@[Dev:sip:103@192.168.124.42:63697;rinstance=6585bbb4e9f969f0]
    23:52:54.041  [CM503010]: Making route(s) to <sip:103@192.168.124.9>
    23:52:54.041  [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:101@192.168.124.9:5060]
    23:52:54.025  [CM503001]: Call(2): Incoming call from Ext.101 to <sip:103@192.168.124.9>
    
    Thanks!
    Danno
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,570
    Likes Received:
    247
    Sorry, I had listed IP 192.168.124.9, which appears to be that of your 3CX PC.

    It appears to be the IVR (or something associated with it) that is not registered. 3CX does not appear to be able to complete the call the way you currently have it set-up.
     
Thread Status:
Not open for further replies.