CircleNet would like to introduce ourselves to the Obi world
Sam_from_CircleNet:
Good Morning ToddAllen,
We proxy all of the audio through our servers so the only traffic that you should see from circlenet should be comming from our sip server in Atlanta or Fremont CA. None of the traffic you are seeing from China Telecom is from us. We don't pass your IP address to any of our upstream carriers either so I can't see any way anyone outside of our network would see you?
Please open a ticket on this one and if possible send a screenshot of the router output to support@circlenet.us or even better a wireshark pcap if you can. I'm wondering if it is possible with your FW config that the listening port isn't open until after the first call is placed and your just not seeing the constant background scanning?
On the second issue the 90 second disconnect/audio issues, please open a ticket on these and if possible give us a specific called number and time when the problem occurred and we'll look into it and see if we can help.
As to encryption we don't do any kind of encryption outside of our network for the audio channels currently. If you are looking to encrypt your traffic between you and the provider I suggest callwithus, they have a VPN service that I think will do what your looking for.
Sam
ToddAllen:
Thanks, I opened a ticket regarding the dropped calls and will work on putting together the info for a 2nd ticket regarding the inbound IP traffic I'm concerned about. Is support@circlenet.us an email address? Would you prefer I cut and paste samples from a router log directly into the ticket or should I email a log file? I want to do wireshark captures but it will take some time as I don't currently have wireshark installed and the last time I used it I remember it was non-trivial to get working and that was just to monitor LAN traffic. This time I'll need to catch the traffic being dropped by the router's WAN interface and I'll have to look into how to do that.
I think you are right about some of the traffic being background noise, especially after it slows to a trickle. Perhaps that would start up on its own if I force a new IP and waited a sufficient amount of time without placing a call, but I haven't specifically tried that yet and only started vigilantly monitoring router traffic after installing the PBX software and encountering difficulties. But the traffic immediately after a call is more concerning as there can be a lot of it and some of it is from IPs registered to CircleNet and I don't understand why CircleNet's traffic would be on the various ports I'm seeing.
As for the comment from voiper1 suggesting my post might be an inappropriate attempt to promote FreeSWITCH, I only brought it up as I made a few calls ok when I used the Obi100 directly to CircleNet but after making the Obi100 an extension on the PBX I encountered the issues described. There's little reason to promote FreeSWITCH as it is a free open source project. I previously tried SipWitch which didn't seem to have the features I wanted or much documentation and Asterisk for which I failed to find sufficient noob friendly configuration guidance and couldn't get working properly. It would have been easier if I had just upgraded to a more expensive Obi with more trunks though long term the free software solution has advantages. And I chose to bring it up here as I wasn't sure it was an appropriate issue for CircleNet's ticket system, I had already been communicating through this forum and it seemed there were some fairly knowledgeable folks here who might have insight and advice.
Quote from: Sam_from_CircleNet on May 18, 2014, 03:24:23 am
Good Morning ToddAllen,
We proxy all of the audio through our servers so the only traffic that you should see from circlenet should be comming from our sip server in Atlanta or Fremont CA. None of the traffic you are seeing from China Telecom is from us. We don't pass your IP address to any of our upstream carriers either so I can't see any way anyone outside of our network would see you?
Please open a ticket on this one and if possible send a screenshot of the router output to support@circlenet.us or even better a wireshark pcap if you can. I'm wondering if it is possible with your FW config that the listening port isn't open until after the first call is placed and your just not seeing the constant background scanning?
On the second issue the 90 second disconnect/audio issues, please open a ticket on these and if possible give us a specific called number and time when the problem occurred and we'll look into it and see if we can help.
As to encryption we don't do any kind of encryption outside of our network for the audio channels currently. If you are looking to encrypt your traffic between you and the provider I suggest callwithus, they have a VPN service that I think will do what your looking for.
Sam
Sam_from_CircleNet:
ToddAllen,
If you'd like to paste directly into the ticket that would be awesome, if you have issues with that or if you need to attach a binary file like a pcap the email address is fine we check them both.
The audio traffic from calls made on our network might come to you on lots of high number ports. Our SIP servers use port 5060 for setup and RTP and ports 10,000 to 20,000 for transporting the actual audio. NAT can cause problems with this if the NAT is also firewalling or performs PAT (port address translation). Often when we see half-duplex audio a NAT/firewall device is performing PAT or dropping one of the udp audio streams based on a firewall rule. I sometimes wish SIP behaved more like IAX (One port) but it doesn't.
If you are very security conscious about your inbound traffic and want to keep a default deny policy (And if you have a PBX believe me I understand why you would be!) you could send calls directly to one server cluster (for example atl.circlenet.us) and then white list just that IP with a permit any/any type rule. This has two downsides however, first if that cluster fails you will not reroute to another one and secondly there isn't a guarantee that we won't change it's IP address in the future.
Sam
voiper1:
Quote from: ToddAllen on May 18, 2014, 08:29:23 am
As for the comment from voiper1 suggesting my post might be an inappropriate attempt to promote FreeSWITCH, I only brought it up as I made a few calls ok when I used the Obi100 directly to CircleNet but after making the Obi100 an extension on the PBX I encountered the issues described. There's little reason to promote FreeSWITCH as it is a free open source project.
Its ok, I completely understand where you are coming from. It just seemed out of place. But glad Sam helped you. His email gets replied to rather quickly. It is amazing what the Obi can do as well as working with something free like FreeSwitch. But many post things just to promote something or tear it down. Posting about FreeSwitch and saying security issues with CircleNet seemed odd. NO worries! Take it easy.
Cheers... :)
baxtr:
Well, I finally bit the bullet and replaced GV with CircleNet on SP1. Voip.ms is on SP2 and I left it alone. I had not touched the OBI110 setup in several years and forgot everything about provisioning. I finally did it from the OBi Dashboard
Approved Service Providers --> Next --> Generic Service Provider:
Generic Service Provider: CircleNet
Primary Line for Outgoing Calls --> Checked
Service Provider Proxy Server: outbound.circlenet.us
Service Provider Proxy Server Port: 5060
Outbound Proxy Server: outbound.circlenet.us
User Name: Your assigned user name from CircleNet
Password: Your CircleNet password
URI: Blank
I initially had problems with the server, west.circlenet.us not registering (completing the call). When I changed it to outbound.circlenet.us, everything proceeded smoothly. This also happened with the Zoiper softphone on a Nokia Lumia 521. Sam_from_CircleNet may wish to look into this issue. Other posts say registration is not necessary and I do not see any place to explicitly register in the setup.
The quality of calls via OBI with CircleNet seems about on par with Voip.ms. Zoiper on a cellphone has sporadic quality issues with both CircleNet and Voip.ms When placing a call via OBI, I do notice a slightly longer delay with CircleNet from the time the call is placed until connection is made when compared with Voip.ms. This may be related to the server location. I am located in the Los Angeles area and using a Voip.ms LA server.
I intend to support CircleNet. I like their business plan; e.g. no bull s..t pay in advance plans, just keep a positive balance and you are good-to-go. Also, their minutes are about half the price of Voip.ms. In my case, this is largely irrelevant because I don't make many calls.
Navigation
[0] Message Index
[#] Next page
[*] Previous page