Always Busy here on IOS Client

Discussion in 'iOS' started by Roland Käser, Oct 4, 2017.

Thread Status:
Not open for further replies.
  1. Roland Käser

    Oct 4, 2017
    Likes Received:

    I've a strange problem with IOS Clients. Every time a call to an IOS Client is made, its rejected with busy here (see Log below)

    - The phone is on the local WLAN (checked and confirmed)
    - No calls are made at this time on the phone
    - The phone shows up as avialable
    - The 3CX Client also shows status available
    - I can make calls from that phone
    - Its only one phone registered to that extension
    - After the call shows busy, the 3CX Client shows up a new missed call

    The problem happens only on the IOS Clients. The Yealink Phones and Android Clients work without problems. All IOS Clients are affected.

    Is there any status on the iphone itself which possible cases this behavior?



    -- Log: Stripped of the authorization String --
    10/04/2017 12:02:23 PM - Terminated from "OFF01"<sip:250@>;tag=2574669257 to <sip:220@>;tag=1b62231a; reason: Rejected
    10/04/2017 12:02:23 PM - L:54.1[Extn:250] Sending: OnSendResp Send 486/INVITE from tid=2246245843 Call-ID=0_2401374380@ SIP/2.0 486 Busy Here Via: SIP/2.0/UDP;branch=z9hG4bK2246245843 To: <sip:220@>;tag=1b62231a From: "OFF01"<sip:250@>;tag=2574669257 Call-ID: 0_2401374380@ CSeq: 2 INVITE Warning: 499 vm-ebn-voip-01.dowa.local "Busy" Content-Length: 0
    10/04/2017 12:02:23 PM - SendMsg from <sip:220@>;tag=1b62231a to "OFF01"<sip:250@>;tag=2574669257
    10/04/2017 12:02:23 PM - Offer SDP arrived on Leg L:54.1[Extn:250]; OnOffer Recv Req INVITE from tid=2246245843 Call-ID=0_2401374380@ INVITE sip:220@ SIP/2.0 Via: SIP/2.0/UDP;branch=z9hG4bK2246245843 Max-Forwards: 70 Contact: <sip:250@> To: <sip:220@> From: "OFF01"<sip:250@>;tag=2574669257 Call-ID: 0_2401374380@ CSeq: 2 INVITE Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE Content-Type: application/sdp Supported: replaces User-Agent: Yealink SIP-T42S Allow-Events: talk, hold, conference, refer, check-sync Content-Length: 310 v=0 o=- 20029 20029 IN IP4 s=SDP data c=IN IP4 t=0 0 m=audio 11940 RTP/AVP 9 0 8 18 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=ptime:20 a=sendrecv a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15
    10/04/2017 12:02:23 PM - Call(C:54) is terminated
    10/04/2017 12:02:23 PM - [CM503020]: Call(C:54): Normal call termination. Call originator: Extn:250. Reason: Busy
    10/04/2017 12:02:23 PM - [CM503016]: Call(C:54): Attempt to reach <sip:220@> from Extn:250 has failed. Reason: Busy
    10/04/2017 12:02:23 PM - [Flow] Call(C:54): Forward on 'Busy' is disabled
    10/04/2017 12:02:23 PM - L:54.1[Extn:250] forwards call from Extn:220 to EndCall:EndCall based on rule Fwd[Available/Busy]
    10/04/2017 12:02:23 PM - [Flow] Endpoint Extn:220 forwarding rule Fwd[Available/Busy] on reason Busy is set to 'EndCall'
    10/04/2017 12:02:23 PM - [Flow] No office hours set, office hours assumed
    10/04/2017 12:02:23 PM - [Flow] Current call diversion path:[]
    10/04/2017 12:02:23 PM - L:54.1[Extn:250] failed to reach Extn:220, reason Busy
    10/04/2017 12:02:23 PM - RerouteReq
  2. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Dec 12, 2008
    Likes Received:
    Hi Roland
    Roland, so you have several iOS devices and all their clients has the behavior you described?
    It's good to know this; if you have many, then it's highly possible the problem be located on the server configuration - if is only one device, then the problem might be on either server/client side. Also, can you tell us the PBX/Client versions?
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.