Ring group - On no answer will not fwd

Discussion in '3CX Phone System - General' started by pibarker, Oct 11, 2010.

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

    Joined:
    Dec 31, 2009
    Messages:
    4
    Likes Received:
    0
    Have simply 2 phones and 2 extensions. Both extensions are in a ring group (mode is prioritized). When pbx is called it answers. 1st phone rings allotted time (20 seconds) then 2nd phone rings. 2nd phone rings exactly 2 times; then message is heard "the number you have called xxx-xxx-xxxx is not available". This happens regardless of the destination chosen for the no answer situation. I have reversed the order of the phones and the same thing happens, so it is not a phone failure.
     
  2. RichardCrabb1

    RichardCrabb1 New Member

    Joined:
    Mar 7, 2009
    Messages:
    196
    Likes Received:
    0
    What if you try ring all to they both ring? Please post the log so that we can see what happens. What kind of phones are you using? Is one extension configured on each?

    Kind regards
    Richard Crabb
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. pibarker

    Joined:
    Dec 31, 2009
    Messages:
    4
    Likes Received:
    0
    Same for ring all. Thanks for your help. Log info below:

    21:09:58.750 [CM503003]: Call(14): Call to sip:100@192.168.1.151 has failed; Cause: 487 Request Cancelled; from IP:192.168.1.133:5060
    21:09:58.640 [CM503008]: Call(14): Call is terminated
    21:09:49.453 [CM503003]: Call(14): Call to sip:101@192.168.1.151 has failed; Cause: 487 Request Terminated; from IP:192.168.1.132:6024
    21:09:49.265 [CM503025]: Call(14): Calling HuntGrp801:100Ext.100@[Dev:sip:100@192.168.1.133:5060]
    21:09:39.750 Currently active calls - 1: [14]
    21:09:29.656 [CM505001]: Ext.101: Device info: Device Identified: [Man: Counterpath;Mod: X-Lite;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [X-Lite release 1002tx stamp 29712] PBX contact: [sip:101@192.168.1.151:5060]
    21:09:29.656 [CM503002]: Call(14): Alerting sip:101@192.168.1.132:6024;rinstance=20bc9017d40ad3af
    21:09:29.250 [CM503025]: Call(14): Calling HuntGrp801:101Ext.101@[Dev:sip:101@192.168.1.132:6024;rinstance=20bc9017d40ad3af]
    21:09:29.234 [CM503004]: Call(14): Route 2: HuntGrp801:100Ext.100@[Dev:sip:100@192.168.1.133:5060]
    21:09:29.234 [CM503004]: Call(14): Route 1: HuntGrp801:101Ext.101@[Dev:sip:101@192.168.1.132:6024;rinstance=20bc9017d40ad3af]
    21:09:29.234 [CM503010]: Making route(s) to <sip:801@192.168.1.151:5060>
    21:09:29.234 [CM505003]: Provider:[Generic VoIP Provider -] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [PAETEC] PBX contact: [sip:61549@99.104.36.51:5060]
    21:09:29.218 [CM503001]: Call(14): Incoming call from 7709720408@(Ln.10000@Generic VoIP Provider -) to <sip:801@192.168.1.151:5060>
    21:09:29.156 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:801
    21:07:37.656 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.1.151:5060
     
  4. RichardCrabb1

    RichardCrabb1 New Member

    Joined:
    Mar 7, 2009
    Messages:
    196
    Likes Received:
    0
    Hi
    The last part of the log says "request cancelled" rather than "request terminated". I have done some test calls and proved that it should say "request terminated" after the period of ring time - 20 seconds. Yours was only about 9 seconds. What type of phones are they? Could you re-test with the call logging set to medium or even verbose. You will need to restart 3CX for the call logging change to take effect. I suspect that the phone is terminating the call for some reason.

    Kind regards
    Richard Crabb
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. pibarker

    Joined:
    Dec 31, 2009
    Messages:
    4
    Likes Received:
    0
    Set logging to verbose and re-tried. I have an old Grandstream BT100 single channel phone and a XACT Technologies soft phone in this system. As I said before, I have reversed the priority of answer with the same results. One thing of inerest is that if I set these phones/extensions up in a Call Queue then forwarding on no answer works fine...I am still doubtful that it is a phone problem but could be...Thanks again for your interest and help.

    11:34:12.796 Currently active calls [none]
    11:33:40.796 Currently active calls [none]
    11:33:37.531 [CM503003]: Call(1): Call to sip:100@192.168.1.151 has failed; Cause: 487 Request Cancelled; from IP:192.168.1.133:5060
    11:33:37.421 [CM503008]: Call(1): Call is terminated
    11:33:28.453 [CM503003]: Call(1): Call to sip:101@192.168.1.151 has failed; Cause: 487 Request Terminated; from IP:192.168.1.132:2964
    11:33:28.296 [CM503025]: Call(1): Calling HuntGrp801:100Ext.100@[Dev:sip:100@192.168.1.133:5060]
    11:33:28.296 [MS210002] C:1.3:Offer provided. Connection(transcoding mode): 192.168.1.151:7002(7003)
    11:33:08.796 Currently active calls - 1: [1]
    11:33:08.453 [CM505001]: Ext.101: Device info: Device Identified: [Man: Counterpath;Mod: X-Lite;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [X-Lite release 1002tx stamp 29712] PBX contact: [sip:101@192.168.1.151:5060]
    11:33:08.453 [CM503002]: Call(1): Alerting sip:101@192.168.1.132:2964;rinstance=40e5af39e2a2b248
    11:33:08.281 [CM503025]: Call(1): Calling HuntGrp801:101Ext.101@[Dev:sip:101@192.168.1.132:2964;rinstance=40e5af39e2a2b248]
    11:33:08.281 [MS210002] C:1.2:Offer provided. Connection(transcoding mode): 192.168.1.151:7000(7001)
    11:33:08.234 [CM503004]: Call(1): Route 2: HuntGrp801:100Ext.100@[Dev:sip:100@192.168.1.133:5060]
    11:33:08.218 [CM503004]: Call(1): Route 1: HuntGrp801:101Ext.101@[Dev:sip:101@192.168.1.132:2964;rinstance=40e5af39e2a2b248]
    11:33:08.187 [MS210000] C:1.1:Offer received. RTP connection: 66.19.38.141:18848(18849)
    11:33:08.187 [CM503010]: Making route(s) to <sip:801@192.168.1.151:5060>
    11:33:08.187 Remote SDP is set for legC:1.1
    11:33:08.187 [CM505003]: Provider:[Generic VoIP Provider -] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [PAETEC] PBX contact: [sip:61549@99.104.36.51:5060]
    11:33:08.171 [CM503001]: Call(1): Incoming call from 7709720408@(Ln.10000@Generic VoIP Provider -) to <sip:801@192.168.1.151:5060>
    11:33:07.781 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:801
    11:33:07.765 Looking for inbound target: called=61549; caller=7709720408
    11:33:07.765 [CM500002]: Info on incoming INVITE:
    INVITE sip:61549@99.104.36.51:5060;rinstance=0b6b5788303021c3 SIP/2.0
    Via: SIP/2.0/UDP 64.24.35.208;branch=z9hG4bKe11a.cc370b72.0
    Via: SIP/2.0/UDP 66.19.38.141;rport=5060;branch=z9hG4bKprZg5aDX0UXyN
    Max-Forwards: 67
    Record-Route: <sip:64.24.35.208;lr=on;ftag=KKUr981XZKtjQ>
    Contact: <sip:mod_sofia@66.19.38.141:5060>
    To: <sip:61549@chi2-sr1-ha.starnetusa.net>
    From: "BARKER PAUL I"<sip:7709720408@66.19.38.141>;tag=KKUr981XZKtjQ
    Call-ID: 05a324b8-50b8-122e-56bc-003048c688e0
    CSeq: 3112551 INVITE
    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, NOTIFY
    Supported: timer, precondition, path, replaces
    User-Agent: PAETEC
    Allow-Events: talk, refer
    Content-Length: 0
    X-SNI-Received: 66.19.160.202
     
Thread Status:
Not open for further replies.