Multiple calls..

Discussion in '3CX Phone System - General' started by new4, Jul 3, 2011.

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

    Joined:
    Apr 7, 2009
    Messages:
    31
    Likes Received:
    0
    Hi to all! :p

    I was wondering if anyone can help me with the following situation that I'm facing with the 3cx pbx:

    When an incoming call comes through a registered voip provider, a ringproup consisting of ext.100 & ext.101 rings. Now when 100 picks up and talk, if during this time another caller calls the same voip number, the free extension (i.e 101) rings properly and the caller is in queue hearing the message, but when ext. 101 picks up the line is buzzing constantly. However,the second caller keeps hearing the queue message properly!! Now when ext.100 hungs up with the first caller, then whoever picks up (ext.100 or ext.101) can talk with the second caller! I know that this sounds like an audio negotiation problem!The phones I'm using are two ordinary analogue phones that I've pluged into the fxs ports of a fritzbox 7140 which I use just as an ATA (not a modem/router)
    Pls refer to attachments for current settings.

    Any help will be highly appreciated :!:

    Thank you in advance all,

    Vassilis
    Rhodes island - Greece
     

    Attached Files:

  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,762
    Likes Received:
    286
    What do you mean by that? A buzzing sound in the earpiece of the phone? What does the 3CX server log show during the call?
     
  3. varietel

    Joined:
    Oct 29, 2010
    Messages:
    22
    Likes Received:
    0
    I am not familiar with the ATA box you have listed but I noticed both phones are showing the same IP address. If there are ports 1 and 2 for phone 1 and phone 2 on the box then shouldn't the IP addresses be different?

    Regards,

    Roger Partovi
    Varietel Communications
    801-889-1414
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,762
    Likes Received:
    286
    Being one ATA with multiple ports, I can understand the single IP....but, each extension, on that device, should have it's own, unique, port number.
     
  5. new4

    Joined:
    Apr 7, 2009
    Messages:
    31
    Likes Received:
    0
    Yes, that's exactly what I thought at first.. But I can't locate anywhere the specific field so that I could give each extension its own (unique) port number. Pls, refer to attachment for ALL available settings of the extension.. P.S The buzzing means, that the second caller (the first is already on a call at the time) keeps hearing the queue message, but when the free extension picks up, then the callee (e.g extension 101) hears the buzzing tone :S
     

    Attached Files:

  6. varietel

    Joined:
    Oct 29, 2010
    Messages:
    22
    Likes Received:
    0
    First, I appologize. I was refferring to port numbers being the same not IP addresses.
    It looks like FritzBox has an Integrated SIP server which does not allow the use of ports 5060 TCP and UDP with the 3CX Phone System. The following excerpt about this conflict for FritzBox 7170 is from the 3CX blog site. I thought the same might be true for 7140. Please get the full document from the blog.

    Configuring AVM FritzBox as a Firewall with 3CX Phone System
    Submitted by nb on April 14, 2010 – 3:28 pmNo Comment.
    This guide will show how to configure an AVM Fritzbox router / firewall as a border device with 3CX Phone System in the LAN. The tests were made using a FritzBox 7170 with firmware version 29.04.76
    .IMPORTANT: The FritzBox has an integrated SiP Server inside. This makes the usage and natting of ports 5060 TCP and UDP to the 3CX Phone System impossible because the Fritzbox will not let you. Hence we have to configure 3CX to listen for SiP on a different port.

    The text is in German but the fields are translated to English. So you probably can figure out how to set the SIP to use other ports instead of 5060.

    Good luck,

    Roger Partovi
    Varietel Communications
    801-889-1414
    roger@varietel.net
     
  7. new4

    Joined:
    Apr 7, 2009
    Messages:
    31
    Likes Received:
    0
    Thank you for the help. I'll have a look at the 3cx blog site about this.So, I guess all I have to do is change the listen port of Fritz to something different than 5060 (pls refer to attached picture). However, what still puzzles me is why everything is ok with the fon1 port of the Fritz (calls can be placed to and from it), and why does -when fon1 is in a call- the fon2 port rings properly, but when picked up, the caller gets a busy signal :oops:
     

    Attached Files:

  8. varietel

    Joined:
    Oct 29, 2010
    Messages:
    22
    Likes Received:
    0
    Great questions. It is strange that Fon1 works on port 5060. I can think of some reasons for the voice not working after the second call is picked up as RTP uses different ports than signaling. Let us know if you get it working.

    Good Luck,

    Roger Partovi
    Varietel Communications
    801-889-1414
    roger@varietel.net
     
  9. new4

    Joined:
    Apr 7, 2009
    Messages:
    31
    Likes Received:
    0
    Port change from 5060 to 5062 has just been tested on Fritz!Box but unfortunately it didn't work :S Problem remains exactly the same as it used to with listen port set to 5060 . Concerning the shared IP, could it be that instead of that it should be set to "Establish own Internet connection (NAT router with PPPoE or IP)" :?: Pls refer to attachment.

    Thank you in advance,

    Vassilis
     

    Attached Files:

  10. varietel

    Joined:
    Oct 29, 2010
    Messages:
    22
    Likes Received:
    0
    I am sorry that the port change did not work. Have you run the Firewall checker in 3CX? If you haven't, run the Firewall checker to make sure all proper ports are forwarded.

    Configuring the Fritzbox for proper Natting seems to depend on how you are connected to Internet. I found the following page on Internet regarding your question.
    http://help.avm.de/fritzbox.php?oem=avme&hardware=139&language=en&set=007&topic=hilfe_internetdual&deviceFeatures=101000111111110101101111111111100011111111100&userSettings=0100
    I hope it is helpful. If you still have problems after making the changes according to this site I suggest you do a capture with Wireshark and send it to 3CX support.

    Best of luck.

    Roger Partovi
    Varietel Communications
    Certified 3CX Partner
    801-889-1414
    roger@varietel.net
    http://www.varietel.net
     
  11. new4

    Joined:
    Apr 7, 2009
    Messages:
    31
    Likes Received:
    0
    Thank you for the link plus the recommendations. Please find below the results of the firewall checker. Unfortunately I already tried to send a wireshark captute to 3cx support, but since I still use ver8 (because of some incompatibilities with the hardware I'm using I can't use an upgrade) the reply was that my version is no longer supported :oops:

    If you see anything strange in the following, kindly let me know.

    Thank you in advance for your efforts,

    Vassilis
    Rhodes island - Greece

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

    <15:05:42>: Phase 1, checking servers connection, please wait...
    <15:05:42>: Stun Checker service is reachable. Phase 1 check passed.
    <15:05:42>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <15:05:43>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 5061::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/support/firewall-checker.html

    <15:05:43>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <15:05:43>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 5061::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/support/firewall-checker.html

    <15:05:43>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <15:05:43>: TCP TUNNEL Port is set to 5090. Response received WITH TRANSLATION 5091::5090. Phase 3 check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/support/firewall-checker.html

    <15:05:43>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <15:05:53>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
    <15:05:53>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
    <15:05:53>: UDP RTP Port 9002. Response received WITH TRANSLATION 9003::9002. Phase 4-03 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9003. Response received WITH TRANSLATION 9004::9003. Phase 4-04 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9004. Response received WITH TRANSLATION 9005::9004. Phase 4-05 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9005. Response received WITH TRANSLATION 9006::9005. Phase 4-06 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9006. Response received WITH TRANSLATION 9009::9006. Phase 4-07 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9007. Response received WITH TRANSLATION 9010::9007. Phase 4-08 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
    <15:05:53>: UDP RTP Port 9009. Response received WITH TRANSLATION 9015::9009. Phase 4-10 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9010. Response received WITH TRANSLATION 9016::9010. Phase 4-11 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9011. Response received WITH TRANSLATION 9017::9011. Phase 4-12 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
    <15:05:53>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
    <15:05:53>: UDP RTP Port 9014. Response received WITH TRANSLATION 9021::9014. Phase 4-15 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9015. Response received WITH TRANSLATION 9034::9015. Phase 4-16 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9016. Response received WITH TRANSLATION 9035::9016. Phase 4-17 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9017. Response received WITH TRANSLATION 9036::9017. Phase 4-18 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
    <15:05:53>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
    <15:05:53>: UDP RTP Port 9020. Response received WITH TRANSLATION 9037::9020. Phase 4-21 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9021. Response received WITH TRANSLATION 9038::9021. Phase 4-22 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
    <15:05:53>: UDP RTP Port 9023. Response received WITH TRANSLATION 9039::9023. Phase 4-24 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9024. Response received WITH TRANSLATION 9025::9024. Phase 4-25 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9025. Response received WITH TRANSLATION 9040::9025. Phase 4-26 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
    <15:05:53>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
    <15:05:53>: UDP RTP Port 9028. Response received WITH TRANSLATION 9029::9028. Phase 4-29 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9029. Response received WITH TRANSLATION 9030::9029. Phase 4-30 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9030. Response received WITH TRANSLATION 9032::9030. Phase 4-31 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9031. Response received WITH TRANSLATION 9033::9031. Phase 4-32 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9032. Response received WITH TRANSLATION 9041::9032. Phase 4-33 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9033. Response received WITH TRANSLATION 9042::9033. Phase 4-34 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9034. Response received WITH TRANSLATION 9043::9034. Phase 4-35 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9035. Response received WITH TRANSLATION 9044::9035. Phase 4-36 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9036. Response received WITH TRANSLATION 9045::9036. Phase 4-37 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9037. Response received WITH TRANSLATION 9046::9037. Phase 4-38 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9038. Response received WITH TRANSLATION 9047::9038. Phase 4-39 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9039. Response received WITH TRANSLATION 9048::9039. Phase 4-40 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9040. Response received WITH TRANSLATION 9049::9040. Phase 4-41 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9041. Response received WITH TRANSLATION 9050::9041. Phase 4-42 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9042. Response received WITH TRANSLATION 9051::9042. Phase 4-43 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9043. Response received WITH TRANSLATION 9052::9043. Phase 4-44 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9044. Response received WITH TRANSLATION 9053::9044. Phase 4-45 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9045. Response received WITH TRANSLATION 9054::9045. Phase 4-46 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9046. Response received WITH TRANSLATION 9055::9046. Phase 4-47 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9047. Response received WITH TRANSLATION 9056::9047. Phase 4-48 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9048. Response received WITH TRANSLATION 9057::9048. Phase 4-49 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <15:05:53>: UDP RTP Port 9049. Response received WITH TRANSLATION 9058::9049. Phase 4-50 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html


    Application exit code is 43
     

    Attached Files:

  12. varietel

    Joined:
    Oct 29, 2010
    Messages:
    22
    Likes Received:
    0
    As you can see from the Firewall checker output for almost all the ports you have limited functionality. For 3CX to run properly Firewall checker should have all the tests passed. You have to get a code 0 at the end indicating no errors. Have you done all the port forwardings according to 3CX instructions? The minimum, you need to forward the ports that are listed in your Firewall attachment:
    5060
    5090
    9000-9049 (UDP)

    At this time it doesn't matter if you can do a wireshark capture because if these ports are not open the calls are not going to work properly.

    Regards,

    Roger Partovi
    Varietel Communications
    3CX Certified Partner
    801-889-1414
    roger@varietel.net
    http://www.varietel.net
     
Thread Status:
Not open for further replies.