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.

Remote ext Fring

Discussion in '3CX Phone System - General' started by wlmoate, Sep 10, 2009.

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

    Joined:
    Sep 10, 2009
    Messages:
    6
    Likes Received:
    0
    Hello

    I have just installed 3CX and have configured a number of ext 2 are via soft phones. The other is a Polycom 320. I can ring between all the devices and have audio. I have set up a SIP account on Fring on the Nokia N95

    When I dial from the softphone or the Polycom to the Nokia it rings and when I answer I get audio

    However when I call from the Fring app to the Polycom it rings but when I answer. Ringing is still heard at the Nokia for a few seconds. Once it stops I have no audio. I have opened all ports on the firewall.

    Below is a cop of the firewall log

    Any help is appreciated

    Wayne

    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

    <20:08:37>: Phase 1, checking servers connection, please wait...
    <20:08:37>: Stun Checker service is reachable. Phase 1 check passed.
    <20:08:37>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <20:08:38>: UDP SIP Port is set to 5060. Response received correctly with no translation. Phase 2a check passed.

    <20:08:38>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <20:08:38>: TCP SIP Port is set to 5060. Response received correctly with no translation. Phase 2b check passed.

    <20:08:38>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <20:08:39>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.

    <20:08:39>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <20:09:00>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
    <20:09:00>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
    <20:09:00>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
    <20:09:00>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
    <20:09:00>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
    <20:09:00>: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
    <20:09:00>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
    <20:09:00>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
    <20:09:00>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
    <20:09:00>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
    <20:09:00>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
    <20:09:00>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
    <20:09:00>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
    <20:09:00>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
    <20:09:00>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
    <20:09:00>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
    <20:09:00>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
    <20:09:00>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
    <20:09:00>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
    <20:09:00>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
    <20:09:00>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
    <20:09:00>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
    <20:09:00>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
    <20:09:00>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
    <20:09:00>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
    <20:09:00>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
    <20:09:00>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
    <20:09:00>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
    <20:09:00>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
    <20:09:00>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
    <20:09:00>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
    <20:09:00>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
    <20:09:00>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
    <20:09:00>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
    <20:09:00>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
    <20:09:00>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
    <20:09:00>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
    <20:09:00>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
    <20:09:00>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
    <20:09:00>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
    <20:09:00>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
    <20:09:00>: UDP RTP Port 9041. Response received correctly with no translation. Phase 4-42 check passed.
    <20:09:00>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
    <20:09:00>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
    <20:09:00>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
    <20:09:00>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
    <20:09:00>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
    <20:09:00>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
    <20:09:00>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
    <20:09:00>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.


    Application exit code is 0
    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

    <20:08:37>: Phase 1, checking servers connection, please wait...
    <20:08:37>: Stun Checker service is reachable. Phase 1 check passed.
    <20:08:37>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <20:08:38>: UDP SIP Port is set to 5060. Response received correctly with no translation. Phase 2a check passed.

    <20:08:38>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <20:08:38>: TCP SIP Port is set to 5060. Response received correctly with no translation. Phase 2b check passed.

    <20:08:38>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <20:08:39>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.

    <20:08:39>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <20:09:00>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
    <20:09:00>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
    <20:09:00>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
    <20:09:00>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
    <20:09:00>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
    <20:09:00>: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
    <20:09:00>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
    <20:09:00>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
    <20:09:00>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
    <20:09:00>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
    <20:09:00>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
    <20:09:00>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
    <20:09:00>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
    <20:09:00>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
    <20:09:00>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
    <20:09:00>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
    <20:09:00>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
    <20:09:00>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
    <20:09:00>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
    <20:09:00>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
    <20:09:00>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
    <20:09:00>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
    <20:09:00>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
    <20:09:00>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
    <20:09:00>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
    <20:09:00>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
    <20:09:00>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
    <20:09:00>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
    <20:09:00>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
    <20:09:00>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
    <20:09:00>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
    <20:09:00>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
    <20:09:00>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
    <20:09:00>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
    <20:09:00>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
    <20:09:00>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
    <20:09:00>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
    <20:09:00>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
    <20:09:00>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
    <20:09:00>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
    <20:09:00>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
    <20:09:00>: UDP RTP Port 9041. Response received correctly with no translation. Phase 4-42 check passed.
    <20:09:00>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
    <20:09:00>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
    <20:09:00>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
    <20:09:00>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
    <20:09:00>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
    <20:09:00>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
    <20:09:00>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
    <20:09:00>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.


    Application exit code is 0
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,086
    Likes Received:
    326
    Are you using the Fring app from outside or within your network?
     
  3. wlmoate

    Joined:
    Sep 10, 2009
    Messages:
    6
    Likes Received:
    0
    From outside the network. However I get the same result when inside the network

    Wayne
     
  4. tpinnovations

    tpinnovations Member

    Joined:
    Jul 30, 2009
    Messages:
    296
    Likes Received:
    0
    Fring proxy's the SIP connection threw there servers, are you using public wifi or a wireless network you own?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. wlmoate

    Joined:
    Sep 10, 2009
    Messages:
    6
    Likes Received:
    0
    Hi

    I am using a 3g mobile phone connection.
    Wayne
     
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,086
    Likes Received:
    326
    Sorry, meant to ask, is there one way audio or nothing either way? Static public IP at the 3CX end?
     
  7. tpinnovations

    tpinnovations Member

    Joined:
    Jul 30, 2009
    Messages:
    296
    Likes Received:
    0
    While there is a hack to operate Fring over 3G, To my knowledge providers have blocked the ports for it to work.

    Try it over a wireless connection you manage first, if that works then we can begin to troubleshoot operation on other networks.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. wlmoate

    Joined:
    Sep 10, 2009
    Messages:
    6
    Likes Received:
    0
    Leejor No audio when making a call from Fring to a phone within the local network. I do get audio when calling from the local network to Fring. Yes I have a static Public IP.

    Tpinnovations I will try from another Wifi connection
     
  9. houston

    Joined:
    Jul 21, 2009
    Messages:
    40
    Likes Received:
    0
    Just installed in on my new Touch Pro2 on Sprint. While I can only get audio via the speakerphone or bluetooth, it does manage to make and receive calls. Testing in the wee hours on a good 3g connection (meaning little to no other users) I got quite good call quality.

    If I can find a better app though, I won't stick with Fring. It DOES work, but the emphasis is really on all the non-SIP features. I have no interest in them, and the extra steps required to just place a call via sip to someone NOT in my contacts is quite a hassle.

    Anyway, I CAN confirm, at least for Sprint, that they do not block SIP, whether it's using Fring, or a laptop with X-Lite on it.
     
  10. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,086
    Likes Received:
    326
    I have had Fring up and working on an HP Smart phone, so i know it will work. I just didn't care to give out that info to a third party so I never pursued it beyond an initial test. That test, however was over WiFi, not using the data capabilities of a carriers network, and, as suggested, that may be the issue. I think that we've all heard how at&t is being overloaded by iPhones downloading data at times and how they are shunning the use of the Skype App.

    If your phone supports WiFi, I would first make an attempt to get it working from outside your network on that. Then if it still doesn't work over your mobile carriers data network, you can blame them. Sending the data to ring a line is relatively small, sending data to maintain an intelligible conversation requires a bit more bandwidth, perhaps more than they are willing to let you use.
     
  11. charlief

    Joined:
    Aug 30, 2008
    Messages:
    9
    Likes Received:
    0
    You should if you possibly can avoid Fring for use with 3CX and there is very good reason for this. Whilst you think your Fring enabled phone is connecting with your 3CX, it is not. Your phone is connecting to a Fring server in the UK or US and then the Fring server is connecting to 3CX. To call from extension 1 to extension 2 will have your audio signal passed half way round the world before it is delivered. And whilst you think you are in control of your own codecs, you are not as the connection from your Fring phone to a Fring server does not use your codecs of choice, it uses its own proprietary ones which are highly compressed and quality suffers. The distance the audio travels introduces latency.
    This also will affect how Fring works behind a firewall, because if you are using Fring as an internal extension on WiFi, it needs to "break out" and "break back in" to your network and let Fring access the internet to function.
    If you have any of the following Nokias,
    E51 E60 E61 E61i E63 E65 E66 E70 E71 E90 N79 N80ie N81(8gb) N82 N95 N95 8gb
    you are in luck because they all have a VoIP engine hardwired in, but you will need a 3rd party application to unlock all or any of their capabilities, such as VoIP over 3G (therefore a completely mobile extension of 3CX, no WiFi required), and G729 codecs, stun etc.
    You’re best bet is to come to us at http://www.voip4mobiles.com and getting us to build a sis file for you which activates the full VoIp capabilities geared towards 3CX at hardware level of your phone including 3G That way you can also configure several phones very quickly. If it is just mobile VoIp you want we have sis files free, too. And Android Windows and Iphone versions are coming soon.
    We are 3CX authorised distributors.
     
Thread Status:
Not open for further replies.