Only "one way voice" with SAMSUNG GT-I9003

Discussion in 'Android' started by gwasner, Jan 16, 2013.

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

    Joined:
    Jan 16, 2013
    Messages:
    3
    Likes Received:
    0
    Dear forum,

    I install 3CX on Samsung GT-I9003.
    Like to use WLAN

    Everything works fine, I can take call, I can receive calls. I can hear the caller.
    BUT: the caller cannot hear me?

    On the Router I configure already a rule and forward/allow all IP Ports to my IP-Address.

    Did someone have similar problems?

    Thanks
    George
     
  2. mixig

    mixig Active Member

    Joined:
    Dec 13, 2011
    Messages:
    519
    Likes Received:
    11
    Is that extension local (WLAN is on the 3cx network) or remote extension (WLAN is on some other location), How extesion is connectedd to the 3cx, SIP or 3cx tunnel?
     
  3. gwasner

    Joined:
    Jan 16, 2013
    Messages:
    3
    Likes Received:
    0
    hello mixig,

    thanks for helping me.
    WLAN is on the 3cx network.

    - Yesterday I try from a other location with WLAN (again WLAN is on the 3cx network), same behavior. I can understand clear, but the other here nothing.

    I install Version 2.0.5 (this shows me 3CX), maybe ther is a other version what I can try?

    Thanks for any idea

    George
     
  4. gwasner

    Joined:
    Jan 16, 2013
    Messages:
    3
    Likes Received:
    0
    hello mixig,

    below I copy my settings, may I shoud use a other "PBX Port: 5060" or "Local SIP Port: 5260"?


    Server Settings:
    I am Out of Office: inaktiv
    Local PBX IP: sipgate.de
    External PBX IP: sipgate.de
    PBX Port: 5060
    STUN Server: empty
    Proxy: sipgate.de

    Other Settings/Advanced:
    Local SIP Port: 5260
    Registration Timeout: 120
    Keep-Alive Interval: 60
    DTMF Method: RFC-2833
    TCP transport: inaktiv
    Nat Helper: aktiv
    Enable: ICE: inaktiv


    Thanks
    George
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    But, you are using the 3CX phone with a VoIP provider, or the 3CX PBX? It looks like it is with a VoIP provider, so i'm not sure what the 3CX network is.

    Port forwarding should not really be necessary, and the fact that you can hear the called party but they can't hear you, means that the incoming packets are getting through. It's the outgoing ones that seem to be having a problem, which is usually , not the case.

    Are you sure that it is not a microphone issue, that has come up in the past, with some model phones. if you press a button, does the other end hear the DTMF tone? Have you tried using a headset?
     
  6. td101

    Joined:
    Feb 21, 2013
    Messages:
    3
    Likes Received:
    0
    i have the same problem: i can hear other side, but they can't hear me.

    i am using sony xperia sx, android 4.0.4
    3cx is 2.0.5

    using also sipgate.de as provider.
    wlan-connection
    tried with and without vpn (which should have restrictions at all)

    any information on how to solve this problem?
     
  7. td101

    Joined:
    Feb 21, 2013
    Messages:
    3
    Likes Received:
    0
    i just downloaded the sipgate-app and tried again: same problem. no the other side can't hear me. but dial-tones are transmitted... strange.
     
  8. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    I'm assuming that by "dial tones", you are referring to DTMF. that being the case, it sounds as if there is an audio path, but, that the Mic is not being connected (used).

    Have you tried a call using a bluetooth headset, or a wired headset? Do do you hear yourself in the earpiece (sidetone)?

    Have you tried restarting the phone and then stopping all "extra" services, that allow themselves to be shut off.
     
  9. td101

    Joined:
    Feb 21, 2013
    Messages:
    3
    Likes Received:
    0
    yes, i ment DTMF :)

    i just tried with a headset: same problem. still one-way-communication
     
Thread Status:
Not open for further replies.