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.

Rebound from external number not working

Discussion in '3CX Phone System - General' started by Novastorm, Nov 30, 2010.

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

    Joined:
    Nov 30, 2010
    Messages:
    6
    Likes Received:
    0
    Hello, first post on this forum, and pretty new to 3CX, i have a question about rebound.

    When i have the call set to forward to external number or skype ID and have rebound on, it works fine when i call from an INTERNAL number, i get "please wait while we locate 556" and the mobile number rings, etc.
    However when i call from an EXTERNAL number to test it, i get "please BRR! record your message and press pound"
    So the line gets picked up, and i hear the start of "please wait while we locate" but after please i hear a buzzing sound and then i get connected to voicemail (happens within half a second)

    I have it set up like this: incoming call goes to ringgroup 802, ringgroup on no answer goes to extention 556, extention 556 on no answer goes to mobile and has rebound turned on.

    Log for the succesfull call looks like this:

    15:20:22.322 [MS105000] C:86.1: No RTP packets were received:remoteAddr=127.0.0.1:40692,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7314
    15:20:21.353 [CM503008]: Call(86): Call is terminated
    15:20:21.135 [CM503008]: Call(85): Call is terminated
    15:20:15.416 [CM505003]: Provider:[Belcentrale -338] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Belcentrale PBX] PBX contact: [sip:0563*002@10.255.0.230:5060]
    15:20:15.416 [CM503002]: Call(86): Alerting sip:0563*002@pbx7.belcentrale.nl:5060
    15:20:08.541 [CM503025]: Call(86): Calling VoIPline:0613xxx923@(Ln.10002@Belcentrale -338)@[Dev:sip:0563*002@pbx7.belcentrale.nl:5060]
    15:20:08.260 [CM503004]: Call(86): Route 1: VoIPline:0613xxx923@(Ln.10002@Belcentrale -338)@[Dev:sip:0563*002@pbx7.belcentrale.nl:5060]
    15:20:08.260 [CM503010]: Making route(s) to <sip:80613xxx923@127.0.0.1:5060>
    15:20:08.244 [CM505001]: Ext.IVRForward: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVRForward helper;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVRForward helper] PBX contact: [sip:IVRForward@127.0.0.1:5060]
    15:20:08.244 [CM503001]: Call(86): Incoming call from Ext.IVRForward to <sip:80613xxx923@127.0.0.1:5060>
    15:20:06.307 [CM503007]: Call(85): Device joined: sip:IVRForward@127.0.0.1:40600;rinstance=230dc7f89837515b
    15:20:06.291 [CM503007]: Call(85): Device joined: sip:101@192.168.1.10:60183;rinstance=80d315f2202c771c
    15:20:06.275 [CM505001]: Ext.IVRForward: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVRForward helper;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVRForward helper] PBX contact: [sip:IVRForward@127.0.0.1:5060]
    15:20:06.275 [CM503002]: Call(85): Alerting sip:IVRForward@127.0.0.1:40600;rinstance=230dc7f89837515b
    15:20:06.182 [CM503003]: Call(85): Call to sip:102@10.255.1.100 has failed; Cause: 487 Request Terminated; from IP:192.168.10.101:5061
    15:20:06.088 [CM503025]: Call(85): Calling Ext:Ext.IVRForward@[Dev:sip:IVRForward@127.0.0.1:40600;rinstance=230dc7f89837515b]
    15:20:06.041 [CM503005]: Call(85): Forwarding: Ext:Ext.IVRForward@[Dev:sip:IVRForward@127.0.0.1:40600;rinstance=230dc7f89837515b]
    15:20:06.041 [CM503016]: Call(85): Attempt to reach <sip:802@10.255.1.100:5060> failed. Reason: Not Registered
    15:20:05.885 [CM503017]: Call(85): Target is not registered: Ext:Ext.556
    15:20:05.400 Currently active calls - 1: [85]
    15:20:05.072 [CM505001]: Ext.102: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Nortel IP Phone 11xx (SIP1120e.03.02.16.00)] PBX contact: [sip:102@10.255.1.100:5060;transport=TCP]
    15:20:05.072 [CM503002]: Call(85): Alerting sip:102@192.168.10.101:5061;transport=tcp
    15:20:04.838 [CM503025]: Call(85): Calling RingAll802:102Ext.102101103Ext.103@[Dev:sip:102@192.168.10.101:5061;transport=tcp]
    15:20:04.807 [CM503004]: Call(85): Route 1: RingAll802:102Ext.102101103Ext.103@[Dev:sip:102@192.168.10.101:5061;transport=tcp]
    15:20:04.807 [CM503010]: Making route(s) to <sip:802@10.255.1.100:5060>
    15:20:04.791 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 5.0.14900.0] PBX contact: [sip:101@10.255.1.100:5060]
    15:20:04.775 [CM503001]: Call(85): Incoming call from Ext.101 to <sip:802@10.255.1.100:5060>

    Log for the unsuccesful call looks like this:

    15:20:48.900 [CM503008]: Call(87): Call is terminated
    15:20:41.728 [CM503007]: Call(87): Device joined: sip:999@127.0.0.1:40600;rinstance=68c9509cc276e74c
    15:20:41.713 [CM505001]: Ext.999: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:999@127.0.0.1:5060]
    15:20:41.713 [CM503002]: Call(87): Alerting sip:999@127.0.0.1:40600;rinstance=68c9509cc276e74c
    15:20:41.541 [CM503025]: Call(87): Calling Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=68c9509cc276e74c]
    15:20:41.478 [CM503004]: Call(87): Route 1: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=68c9509cc276e74c]
    15:20:41.478 [CM503010]: Making route(s) to <sip:556@127.0.0.1:5060;user=vmail>
    15:20:41.478 [CM505003]: Provider:[Belcentrale -338] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Belcentrale PBX] PBX contact: [sip:0563*002@10.255.0.230:5060]
    15:20:41.072 [CM503020]: Normal call termination. Reason: Not found
    15:20:41.072 [CM503016]: Call(88): Attempt to reach <sip:80613xxx923@127.0.0.1:5060> failed. Reason: Not Found
    15:20:41.072 [CM503014]: Call(88): No known route to target: <sip:80613xxx923@127.0.0.1:5060>
    15:20:41.057 [CM503010]: Making route(s) to <sip:80613xxx923@127.0.0.1:5060>
    15:20:41.057 [CM505001]: Ext.IVRForward: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVRForward helper;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVRForward helper] PBX contact: [sip:IVRForward@127.0.0.1:5060]
    15:20:41.057 [CM503001]: Call(88): Incoming call from Ext.IVRForward to <sip:80613xxx923@127.0.0.1:5060>
    15:20:39.041 [CM503007]: Call(87): Device joined: sip:IVRForward@127.0.0.1:40600;rinstance=230dc7f89837515b
    15:20:39.025 [CM503007]: Call(87): Device joined: sip:0563*002@pbx7.belcentrale.nl:5060
    15:20:39.010 [CM505001]: Ext.IVRForward: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVRForward helper;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVRForward helper] PBX contact: [sip:IVRForward@127.0.0.1:5060]
    15:20:39.010 [CM503002]: Call(87): Alerting sip:IVRForward@127.0.0.1:40600;rinstance=230dc7f89837515b
    15:20:38.994 [CM503003]: Call(87): Call to sip:102@10.255.1.100 has failed; Cause: 487 Request Terminated; from IP:192.168.10.101:5061
    15:20:38.885 [CM503003]: Call(87): Call to sip:101@10.255.1.100:5060 has failed; Cause: 487 Request Terminated; from IP:192.168.1.10:60183
    15:20:38.791 [CM503025]: Call(87): Calling Ext:Ext.IVRForward@[Dev:sip:IVRForward@127.0.0.1:40600;rinstance=230dc7f89837515b]
    15:20:38.760 [CM503005]: Call(87): Forwarding: Ext:Ext.IVRForward@[Dev:sip:IVRForward@127.0.0.1:40600;rinstance=230dc7f89837515b]
    15:20:38.744 [CM503016]: Call(87): Attempt to reach <sip:802@10.255.1.100:5060> failed. Reason: Not Registered
    15:20:38.744 [CM503017]: Call(87): Target is not registered: Ext:Ext.556
    15:20:37.807 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 5.0.14900.0] PBX contact: [sip:101@10.255.1.100:5060]
    15:20:37.807 [CM503002]: Call(87): Alerting sip:101@192.168.1.10:60183;rinstance=80d315f2202c771c
    15:20:37.775 [CM505001]: Ext.102: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Nortel IP Phone 11xx (SIP1120e.03.02.16.00)] PBX contact: [sip:102@10.255.1.100:5060;transport=TCP]
    15:20:37.775 [CM503002]: Call(87): Alerting sip:102@192.168.10.101:5061;transport=tcp
    15:20:37.666 [CM503025]: Call(87): Calling RingAll802:102Ext.102101Ext.101103Ext.103@[Dev:sip:101@192.168.1.10:60183;rinstance=80d315f2202c771c]
    15:20:37.650 [CM503025]: Call(87): Calling RingAll802:102Ext.102101Ext.101103Ext.103@[Dev:sip:102@192.168.10.101:5061;transport=tcp]
    15:20:37.635 [CM503004]: Call(87): Route 1: RingAll802:102Ext.102101Ext.101103Ext.103@[Dev:sip:102@192.168.10.101:5061;transport=tcp,Dev:sip:101@192.168.1.10:60183;rinstance=80d315f2202c771c]
    15:20:37.635 [CM503010]: Making route(s) to <sip:802@10.255.1.100:5060>
    15:20:37.635 [CM505003]: Provider:[Belcentrale -338] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Belcentrale PBX] PBX contact: [sip:0563*002@10.255.0.230:5060]
    15:20:37.619 [CM503001]: Call(87): Incoming call from 062xxx1601@(Ln.10002@Belcentrale -338) to <sip:802@10.255.1.100:5060>

    Any help would be greatly appreciated!
     
  2. mfm

    mfm Active Member

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

    It seems like it is getting stuck whilst trying to find a path to your outbound rule. Its not matching any outobund rules. Can you kindly take a screenshot of your outbound rules. And advise which version of 3cx your are using (build number).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Novastorm

    Joined:
    Nov 30, 2010
    Messages:
    6
    Likes Received:
    0
    Sorry i forgot to include the build, it is version 9 with SP4: 9.14901
    I also think it has something to do with outbound rules, but it uses the same outbound rule (or at least it should be) and the start of the process is the same in both the successful call:
    15:20:08.260 [CM503004]: Call(86): Route 1: VoIPline:0613xxx923@(Ln.10002@Belcentrale -338)@[Dev:sip:0563*002@pbx7.belcentrale.nl:5060]
    15:20:08.260 [CM503010]: Making route(s) to <sip:80613xxx923@127.0.0.1:5060>

    and the unsuccessful call:
    15:20:41.072 [CM503014]: Call(88): No known route to target: <sip:80613xxx923@127.0.0.1:5060>
    15:20:41.057 [CM503010]: Making route(s) to <sip:80613xxx923@127.0.0.1:5060>

    Only with the successul call it actually finds the route, and in the unsuccessful call it says "no known route to target"

    Anyway here is a screenshot of my outbound rules:
    [​IMG]
     
  4. mfm

    mfm Active Member

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

    So what is happening here is that on 802 there is a forwarding rule set to go to mobile. The problem is that the call is origianting for 802 but there is no outbound rule that allows 802 thus blocking the call, please fix your outbound rules accordingly.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Novastorm

    Joined:
    Nov 30, 2010
    Messages:
    6
    Likes Received:
    0
    Actually that is not what is happening, the 802 is the ring group so that all phones on this floor ring at the same time for 20 seconds, if there is no answer the forwarding rule is to go to extention 556 and that one has the forwarding rule to go to external number after 10 seconds with rebound option turned on.

    As you can see 556 is in the outbond rule for -338.
     
  6. Wanderer

    Joined:
    Nov 9, 2010
    Messages:
    19
    Likes Received:
    0
    Hi
    Is ext 556 a dummy ext ? if so I would remove and forward to mobile from ring group, also add ring group number to outbound rule.

    This worked for me.

    Tim
     
  7. Novastorm

    Joined:
    Nov 30, 2010
    Messages:
    6
    Likes Received:
    0
    It is a dummy extention right now, but in the future it will be a phone downstairs to be rang only when noone picks up in the upstairs ringgroup, so i will try your solution but it would be preferable to get this working now so that when the downstairs phone is needed i will not run into this problem again.

    Ofcourse the fact that no actual phone is connected right now might be what is causing the trouble in the first place? I will test this out ASAP.

    Thank you for your reply!
     
Thread Status:
Not open for further replies.