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.

Solved Paging Intercom problem

Discussion in '3CX Phone System - General' started by jimbo59, Apr 14, 2018.

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

    jimbo59 Member

    Joined:
    Nov 17, 2017
    Messages:
    358
    Likes Received:
    77
    I setup a group page and paged all and it worked. After that initial page, intercom and paging don't work anymore. Before that group page I could intercom any phone and now I can't page or intercom any phone. I have rebooted the system and the phones.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. OCWI

    OCWI New Member

    Joined:
    Jan 17, 2017
    Messages:
    161
    Likes Received:
    46
    SBC or lan? We have ran into this before with yealink t46's where we had to rollback the firmware for it to work again. However, if we provisioned them via lan then they worked.
     
  3. jimbo59

    jimbo59 Member

    Joined:
    Nov 17, 2017
    Messages:
    358
    Likes Received:
    77
    Lan. Nothing changed. I paged a large group of T48 and Htek-863 and it worked fine. After that they just ring and no auto-answer.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. OCWI

    OCWI New Member

    Joined:
    Jan 17, 2017
    Messages:
    161
    Likes Received:
    46
    Default templates i assume? Take the HTEKS out of the page group any change?
     
  5. jimbo59

    jimbo59 Member

    Joined:
    Nov 17, 2017
    Messages:
    358
    Likes Received:
    77
    default templates. They all worked until the full group page, then no page and no intercom. Intercom worked flawlessly. Must be a dream.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. OCWI

    OCWI New Member

    Joined:
    Jan 17, 2017
    Messages:
    161
    Likes Received:
    46
    very odd indeed, may be worth a trace + ticket....i'm afraid to say :(
     
  7. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,083
    Likes Received:
    325
    So...if you *9XXX to a set, does it page that set? If it fails, what does the Activity Log show as the reason? What about when you try paging all, what does the log show for the call?
     
  8. jimbo59

    jimbo59 Member

    Joined:
    Nov 17, 2017
    Messages:
    358
    Likes Received:
    77
    It just rings and no answer. It's as though auto-answer is not enabled anymore on the phones. But they are enabled and the units are not on DND. I'm rebooting in verbose mode.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. jimbo59

    jimbo59 Member

    Joined:
    Nov 17, 2017
    Messages:
    358
    Likes Received:
    77
    04/14/2018 7:01:19 PM - L:3.3[Extn:205]: Terminating targets, reason: SIP ;cause=487 ;text="Request Terminated"
    04/14/2018 7:01:19 PM - Leg L:3.3[Extn:205] is terminated: Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
    04/14/2018 7:01:19 PM - Call(C:3), Extn:205 on exit: DlgInfo(3-5420/Terminated / R)
    04/14/2018 7:01:19 PM - Call(C:3), Extn:205 on entry: DlgInfo(3-5420/Early / R)
    04/14/2018 7:01:19 PM - Notify dialog-info: Extn:205: sip:205@127.0.0.1:5488;rinstance=5334b3787e541e4d, Call(C:3)
    04/14/2018 7:01:19 PM - L:3.3[Extn:205] got Terminated Recv 487/INVITE from 127.0.0.1:5488 tid=8c7d3e31bf29ce43 Call-ID=FCnHxFV3YSkJMwmYg04oFA..: SIP/2.0 487 Request Terminated Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-524287-1---8c7d3e31bf29ce43;rport=5060 To: <sip:205@pooltimepool.3cx.us>;tag=f6819243 From: "Jim"<sip:8000@127.0.0.1:5060;nf=b>;tag=55413d63 Call-ID: FCnHxFV3YSkJMwmYg04oFA.. CSeq: 1 INVITE User-Agent: 3CX Push Service Content-Length: 0
    04/14/2018 7:01:19 PM - Stop call record for leg L:3.3[Extn:205]
    04/14/2018 7:01:19 PM - Removing leg L:3.3[Extn:205]
    04/14/2018 7:01:19 PM - L:3.3[Extn:205] got Failure: Failure Recv 487/INVITE from 127.0.0.1:5488 tid=8c7d3e31bf29ce43 Call-ID=FCnHxFV3YSkJMwmYg04oFA..: SIP/2.0 487 Request Terminated Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-524287-1---8c7d3e31bf29ce43;rport=5060 To: <sip:205@pooltimepool.3cx.us>;tag=f6819243 From: "Jim"<sip:8000@127.0.0.1:5060;nf=b>;tag=55413d63 Call-ID: FCnHxFV3YSkJMwmYg04oFA.. CSeq: 1 INVITE User-Agent: 3CX Push Service Content-Length: 0
    04/14/2018 7:01:19 PM - Session 1147 has failed in leg L:3.3[Extn:205] ; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
    04/14/2018 7:01:19 PM - L:3.2[Extn:205]: Terminating targets, reason: SIP ;cause=487 ;text="Request Cancelled"
    04/14/2018 7:01:19 PM - Leg L:3.2[Extn:205] is terminated: Cause: 487 Request Cancelled/INVITE from 192.168.0.80:11610
    04/14/2018 7:01:19 PM - Call(C:3), Extn:205 on exit: DlgInfo(3-2041/Terminated / R)
    04/14/2018 7:01:19 PM - Call(C:3), Extn:205 on entry: DlgInfo(3-2041/Early / R)
    04/14/2018 7:01:19 PM - Notify dialog-info: Extn:205: sip:205@192.168.0.80:11610;transport=UDP, Call(C:3)
    04/14/2018 7:01:19 PM - L:3.2[Extn:205] got Terminated Recv 487/INVITE from 192.168.0.80:11610 tid=80c00943fec22759 Call-ID=wddnqIJ8Om59mWl1okl6ag..: SIP/2.0 487 Request Cancelled Via: SIP/2.0/UDP 192.168.0.35:5060;branch=z9hG4bK-524287-1---80c00943fec22759;rport=5060 To: <sip:205@192.168.0.35>;tag=89dd88dc766bf47 From: "Jim" <sip:8000@192.168.0.35:5060;nf=b>;tag=cea12b20 Call-ID: wddnqIJ8Om59mWl1okl6ag.. CSeq: 1 INVITE Allow: INVITE, ACK, UPDATE, INFO, CANCEL, BYE, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, PRACK User-Agent: Htek 001fc11be983 UC862 V2.0.4.4.35 Content-Length: 0
    04/14/2018 7:01:19 PM - Stop call record for leg L:3.2[Extn:205]
    04/14/2018 7:01:19 PM - Removing leg L:3.2[Extn:205]
    04/14/2018 7:01:19 PM - L:3.2[Extn:205] got Failure: Failure Recv 487/INVITE from 192.168.0.80:11610 tid=80c00943fec22759 Call-ID=wddnqIJ8Om59mWl1okl6ag..: SIP/2.0 487 Request Cancelled Via: SIP/2.0/UDP 192.168.0.35:5060;branch=z9hG4bK-524287-1---80c00943fec22759;rport=5060 To: <sip:205@192.168.0.35>;tag=89dd88dc766bf47 From: "Jim" <sip:8000@192.168.0.35:5060;nf=b>;tag=cea12b20 Call-ID: wddnqIJ8Om59mWl1okl6ag.. CSeq: 1 INVITE Allow: INVITE, ACK, UPDATE, INFO, CANCEL, BYE, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, PRACK User-Agent: Htek 001fc11be983 UC862 V2.0.4.4.35 Content-Length: 0
    04/14/2018 7:01:19 PM - Session 1145 has failed in leg L:3.2[Extn:205] ; Cause: 487 Request Cancelled/INVITE from 192.168.0.80:11610
    04/14/2018 7:01:19 PM - L:3.1[Line:10002<<+8000] failed to reach Extn:205, reason No Answer
    04/14/2018 7:01:12 PM - Endpoint Extn:205 has refreshed contact <sip:205@192.168.0.80:11610>

    It rings like a normal call, but no auto-answer like intercom that worked before my company wide group page. Since that group page no intercom works. Very strange.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,083
    Likes Received:
    325
    Did you compare to a log of the successful page?
    You are calling from...what, an extension, a trunk?

    Have you tried creating a new extension, and intercom just that one?
    Have you tried originating the page/intercom from various sources/devices?
     
  11. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    64
    As the phone is ringing, the INVITE is at least being seen. You may want to do a capture of a page and then see what is being sent in the alert-info field and then compare to what is in the phones. Most need to see this in order to know if the intent is for auto-answer to occur for a page/intercom. Perhaps one of the templates changed and the phones in the meantime have been re-provisioned and picked up the new settings. Just a guess, but a capture will show the details regardless.
     
  12. jimbo59

    jimbo59 Member

    Joined:
    Nov 17, 2017
    Messages:
    358
    Likes Received:
    77
    As I said, I did one massive group page yesterday. The page was successful and after that time page and intercom doesn't work. No phones were updated in that time and nothing else changed. I won't be working on it until tomorrow morning.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    7,341
    Likes Received:
    535
    If you are calling an ext. with *9xxx and it just rings it could be a permissions issue. Navigate to the callers extensions settings and check if the extension has the right to Intercom. Also check that the dial code you are using is the correct.
     
  14. jimbo59

    jimbo59 Member

    Joined:
    Nov 17, 2017
    Messages:
    358
    Likes Received:
    77
    As I said it worked and then I did a company wide page and after that nothing works. Nothing else changed.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. jimbo59

    jimbo59 Member

    Joined:
    Nov 17, 2017
    Messages:
    358
    Likes Received:
    77
    When I came in the office all the phones were saying "talking." I thought I had reboot them remotely but since they were "talking" apparently that didn't work. This was a loose nut behind the keyboard error. Close this case.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. samlouis55

    Joined:
    Mar 29, 2018
    Messages:
    25
    Likes Received:
    0
    Sorry I don't understand what you mean. What was the issue?
     
  17. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    7,341
    Likes Received:
    535
    Glad to see the issue has been resolved and thank you for updating the thread.
     
Thread Status:
Not open for further replies.