Galaxy S3 - No incoming or outgoing external calls

Discussion in 'Android' started by gbschulz, Nov 4, 2013.

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

    Joined:
    Nov 4, 2013
    Messages:
    7
    Likes Received:
    0
    We are running 3CX Ver 12 with the latest 3CXPhone for Android. We cannot receive or place external calls via the Android. Same results if "in office" or "out of office" using 3CX tunnel. All outgoing external calls terminate on the client with the message "Call Failed, Not Acceptable". Internal (extension) calls received or initiated by the Android work fine whether in or out of office.

    By viewing the server log, it appears as if the Android requested the call termination.

    Any ideas?
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    If internal (extension to extension) calls go through just fine, then I would suspect something to do with your outbound rules. You don't have the rules limited to certain extensions, the Android not being one of them, do you?
     
  3. gbschulz

    Joined:
    Nov 4, 2013
    Messages:
    7
    Likes Received:
    0
    We have no inbound or outbound rules that are extension specific. In fact, we only have two outbound rules to route calls to the local POTS or to a foreign line. Neither outbound condition works for the Android but the rules work fine for in-house extensions. Thanks for the thought. Any other ideas?
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    Have a look at the 3CX logs just after trying a call that fails, compare it to a working call from another extension. That should show what the problem is. If you aren't sure what it's telling you, then post the failed call log here in the forum.
     
  5. gbschulz

    Joined:
    Nov 4, 2013
    Messages:
    7
    Likes Received:
    0
    Here is the server log when dialing from the Android app (extension 21). The Android IP is 192.168.10.102. The 3CX server IP is 192.168.10.50. The Grandstream gateway is on 192.168.10.51. I have obscured the user name, dialed telephone number, and company name to "ME", "2625551212", and "ABC" respectively. The number dialed matched our outbound rule of a "USA" call.

    When I look at the log, it appears to me that the Android app is terminating the call (3rd line down). I welcome your interpretation and advice.

    07-Nov-2013 10:25:56.039 Leg L:18.2[Line:10000>>9922625551212] is terminated: Cause: BYE from PBX
    07-Nov-2013 10:25:56.039 [CM503008]: Call(C:18): Call is terminated
    07-Nov-2013 10:25:56.036 Leg L:18.1[Extn] is terminated: Cause: BYE from 192.168.10.102:39234
    07-Nov-2013 10:25:56.026 [CM503007]: Call(C:18): Line:10000>>9922625551212 has joined, contact <sip:10000@192.168.10.51:5060>
    07-Nov-2013 10:25:56.021 [CM503007]: Call(C:18): Extn:21 has joined, contact <sip:21@192.168.10.102:39234>
    07-Nov-2013 10:25:56.016 L:18.2[Line:10000>>9922625551212] has joined to L:18.1[Extn]
    07-Nov-2013 10:25:56.016 NAT/ALG check:L:18.2[Line:10000>>9922625551212] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    07-Nov-2013 10:25:56.008 [CM505002]: Gateway:[Grandstream FXO] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4104 (HW 2.0, Ch:8) 1.3.4.13] PBX contact: [sip:10000@192.168.10.50:5060]
    07-Nov-2013 10:25:53.045 [CM503025]: Call(C:18): Calling T:Line:10000>>9922625551212@[Dev:sip:10000@192.168.10.51:5060;transport=udp;user=phone,Dev:sip:10001@192.168.10.51:5062;transport=udp;user=phone] for L:18.1[Extn]
    07-Nov-2013 10:25:53.010 [CM503027]: Call(C:18): From: Extn:21 ("ABC" <sip:21@192.168.10.50:5060>) to T:Line:10000>>9922625551212@[Dev:sip:10000@192.168.10.51:5060;transport=udp;user=phone,Dev:sip:10001@192.168.10.51:5062;transport=udp;user=phone]
    07-Nov-2013 10:25:53.010 [CM503004]: Call(C:18): Route 1: from L:18.1[Extn] to T:Line:10000>>9922625551212@[Dev:sip:10000@192.168.10.51:5060;transport=udp;user=phone,Dev:sip:10001@192.168.10.51:5062;transport=udp;user=phone]
    07-Nov-2013 10:25:53.010 Line limit check: Current # of calls for line Lc:10003(@Grandstream FXO[<sip:10003@192.168.10.51:5066>]) is 0; limit is 1
    07-Nov-2013 10:25:53.010 Line limit check: Current # of calls for line Lc:10002(@Grandstream FXO[<sip:10002@192.168.10.51:5064>]) is 0; limit is 1
    07-Nov-2013 10:25:53.010 Line limit check: Current # of calls for line Lc:10001(@Grandstream FXO[<sip:10001@192.168.10.51:5062>]) is 0; limit is 1
    07-Nov-2013 10:25:53.010 Line limit check: Current # of calls for line Lc:10000(@Grandstream FXO[<sip:10000@192.168.10.51:5060>]) is 0; limit is 1
    07-Nov-2013 10:25:53.010 Call(C:18): Call from Extn:21 to 12625551212 matches outbound rule 'USA'
    07-Nov-2013 10:25:53.005 [CM503001]: Call(C:18): Incoming call from Extn:21 to <sip:12625551212@192.168.10.50:5060>
    07-Nov-2013 10:25:52.999 NAT/ALG check:L:18.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks
     
  6. gbschulz

    Joined:
    Nov 4, 2013
    Messages:
    7
    Likes Received:
    0
    I realize it might be helpful to have the verbose version of the log just before the 10:25:56.036 termination entry. Here is the verbose snippet:

    07-Nov-2013 10:25:56.036 Leg L:18.1[Extn] is terminated: Cause: BYE from 192.168.10.102:39234
    07-Nov-2013 10:25:56.032 L:18.1[Extn] got Terminated Recv Req BYE from 192.168.10.102:39234 tid=Pj5Jb.UWgTYM041kj3FE2SWkk1W9SDF3td Call-ID=Z9Y2ZFWwnKMZ41sLnHNVKF8yvQNhRszT:
    BYE sip:12625551212@192.168.10.50:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.10.102:39234;rport=39234;branch=z9hG4bKPj5Jb.UWgTYM041kj3FE2SWkk1W9SDF3td
    Max-Forwards: 70
    To: <sip:12625551212@192.168.10.50>;tag=023fc949
    From: "ABC"<sip:21@192.168.10.50>;tag=5MPih4VA69ay6MZYFmK.w.XWHCf9upQK
    Call-ID: Z9Y2ZFWwnKMZ41sLnHNVKF8yvQNhRszT
    CSeq: 2840 BYE
    Content-Length: 0
    07-Nov-2013 10:25:56.032 Terminated from "ABC"<sip:21@192.168.10.50>;tag=5MPih4VA69ay6MZYFmK.w.XWHCf9upQK to <sip:12625551212@192.168.10.50>;tag=023fc949; reason: RemoteBye
    07-Nov-2013 10:25:56.032 L:18.1[Extn] Sending: OnSendResp Send 200/BYE from 0.0.0.0:0 tid=Pj5Jb.UWgTYM041kj3FE2SWkk1W9SDF3td Call-ID=Z9Y2ZFWwnKMZ41sLnHNVKF8yvQNhRszT:
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.10.102:39234;rport=39234;branch=z9hG4bKPj5Jb.UWgTYM041kj3FE2SWkk1W9SDF3td
    Contact: <sip:12625551212@192.168.10.50:5060>
    To: <sip:12625551212@192.168.10.50>;tag=023fc949
    From: "ABC"<sip:21@192.168.10.50>;tag=5MPih4VA69ay6MZYFmK.w.XWHCf9upQK
    Call-ID: Z9Y2ZFWwnKMZ41sLnHNVKF8yvQNhRszT
    CSeq: 2840 BYE
    Content-Length: 0
    07-Nov-2013 10:25:56.032 SendMsg from <sip:12625551212@192.168.10.50>;tag=023fc949 to "ABC"<sip:21@192.168.10.50>;tag=5MPih4VA69ay6MZYFmK.w.XWHCf9upQK
    07-Nov-2013 10:25:56.031 Session 46968 of leg L:18.1[Extn] is confirmed
    07-Nov-2013 10:25:56.031 L:18.1[Extn] got Confirmed Recv Req ACK from 192.168.10.102:39234 tid=Pjo-c1h-bl0EuMBZJNf4HbovkPso9EIApj Call-ID=Z9Y2ZFWwnKMZ41sLnHNVKF8yvQNhRszT:
    ACK sip:12625551212@192.168.10.50:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.10.102:39234;rport=39234;branch=z9hG4bKPjo-c1h-bl0EuMBZJNf4HbovkPso9EIApj
    Max-Forwards: 70
    To: <sip:12625551212@192.168.10.50>;tag=023fc949
    From: "ABC"<sip:21@192.168.10.50>;tag=5MPih4VA69ay6MZYFmK.w.XWHCf9upQK
    Call-ID: Z9Y2ZFWwnKMZ41sLnHNVKF8yvQNhRszT
    CSeq: 2839 ACK
    Content-Length: 0
     
  7. gbschulz

    Joined:
    Nov 4, 2013
    Messages:
    7
    Likes Received:
    0
    One further update. It appears as if the call from the Android app does briefly go through to the dialed number (it rang once at the destination number) before the call is terminated.
     
  8. gbschulz

    Joined:
    Nov 4, 2013
    Messages:
    7
    Likes Received:
    0
    SOLVED!

    It turns out that the Grandstream profile had the "Accept INVITE from Proxy Only" turned on. This prevented the hand-off of the call to the Android app. Turning this option OFF fixed the problem.

    I appreciate the help from leejor on the forum.
     
  9. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    Wow, I'll have to remember that one.

    As I don't use the Grandstream gateway(s), that is an option that I haven't seen before, nor do I recall this issue cropping up before on the forums.

    Did you manually configure the gateway? If it was auto provisioned, I'm wondering why it was not "set" correctly to deal with your phone.
     
  10. gbschulz

    Joined:
    Nov 4, 2013
    Messages:
    7
    Likes Received:
    0
    That was a default configuration. So Grandstream users be aware!
     
Thread Status:
Not open for further replies.