Jump to content

amn

Members
  • Posts

    145
  • Joined

  • Last visited

  • Days Won

    12

Posts posted by amn

  1. 3 hours ago, extremerotary said:

    @amn

    Are you a hosted customer of 2600hz, or are you asking "As a service provider, how do others handle resellers/customers bringing their own carriers?" - I ask, because I don't know how 2600hz hosted platform handles those.

    As a service provider with your own cluster you have a few options. You can create carriers in the offnet database that require that flag in order for them to be used. Then, in those accounts, you'll set that flag on the devices. This will fulfill the outbound requirement. Inbound is pretty straight-forward; add them to your ecallmgr ACLs, and the numbers will route as they will.

    There is also some functionality in the 'resource' callflow module (newer version of 'offnet') that allows for a specific account to have its own carrier list. For more dev info on that, take a read on this article and let me know if you have additional questions: https://docs.2600hz.com/dev/applications/callflow/doc/resources/

    I am only talking about reseller accounts with their own carriers.  Not offnet/global.  Yes it's my own cluster.  

  2. How are people handling bring your own carriers?  Some carriers only do IP authentication and as far as I can tell, IP authentication won't work for bring your own carrier because the carrier only allows the IP to be used once.  Or am I missing something?   Also, the carrier would need to be registered to each Freeswitch server used for outbound correct?  How should I do that?  I think for inbound I should just be able to add the Carrier IP to the ACL right?

    Any other gotcha's I need to be aware of for bring your own carrier?

  3. 6 minutes ago, Tuly said:

    Not worried about clients using API, Most of them don't even know what CMD is or even how to download teamviewer😊😊    But they sure know how to go into the Web and start clicking buy numbers....

    Maybe I am giving most customers too much credit  B|.  I guess it kind of depends on what kind of customer you are going for .

    Be that as it may, restricting in the token will accomplish everything you need to.  UI will probably just throw an error.  

  4. Keep in mind that removing the ability from the UI does not remove the ability from the API.  Anyone who has access to the UI will also have full access to the API.   So it is better to try restrict the API using token restrictions.  Not sure if that is possible or not in token restrictions.

    https://github.com/2600hz/kazoo/blob/master/applications/crossbar/doc/token_restrictions.md

     

  5. On 11/29/2017 at 6:31 AM, Bobby Camisa said:

    I'm trying to be optimistic. The way these companies are moving, they are more concerned about delivering media content then they are voice. Verizon and Comcast are trying to purchase assets from Twenty-First Century Fox inc. Follow the link below, there is a blurb about it there.  I believe they see the future as media companies. I don't think they care much about VoIP. I think the biggest losers are NetFlix, HULU, YouTube, Google, and companies of the like. These companies also have the capital to ride the "fast lanes."  I honestly have no idea what's going to happen. I do know there are people that are allot smarter than me that will figure out a work around to whatever the ISP's intend to do. I'm also sure when they figure it out, it will spread like wild fire. 

    https://finance.yahoo.com/news/telecom-stock-roundup-fcc-plans-192107893.html

    Verizon is a phone company.  Comcast is also now a phone company.  I think it's pretty safe to say that a phone company is going to want to target VoIP.

    I might be in favor of getting rid of neutrality rules if telecoms agreed to stop defending their monopolies.  That is never going to happen.  They have fought Google every step of the way during the rollout of Google Fiber.  Sounds like Google has basically given up now.  

  6. On 11/22/2017 at 7:27 AM, Bobby Camisa said:

    If you're providing video services I think there is cause for concern. I don't think you have much to fear on VoIP, even hosted. Hosted is using port 7000, it's going to look like random internet traffic. The voice packets are so small, I don't think there is a reason to be concerned. I think the Netflix and the likes have cause for concern. The larger companies care more about media then they do voice. If you're delivering voice through an ATA, or an Adtran TA9xx you may want to change the ports being used for voice traffic to mirror what hosted is using by default. 

    Pretty sure most ISPs can do deep packet inspection.  So they can determine the type of traffic without looking at ports.  It would also be trivial to block or slow down traffic to certain IP's. So they could very easily block or de-prioritize all of 2600hz's hosted VoIP traffic, for example.  

    The only possible workaround I can see is using VPN's. That comes with its own headaches and will degrade quality.  ISP's can target those as well just like Netflix and other companies currently do.

    If you want to know more about what they can do, take a look at products they already own.
    https://www.sandvine.com/

     

  7. I think it could be the death of VoIP as we know it.  I am pretty sure Comcast already throttles VoIP traffic in some locations depending on how busy the internet is.  At least for residential customers.  They never admit it and I don't think their support people even know about it.  

    They won't even bother asking for payment for a faster lane or anything like that because it competes directly with their services.  So I think VoIP will be the worst case scenario when net neutrality goes away.

  8. This post further up + the next post right after is what everyone needs to get started.  That automates the important first step of creating the token.  Can't do anything else until you do that and it's not very practical to try do it manually.  Should be a sticky or added to the 2600hz documentation.

     

  9. On 10/2/2017 at 10:03 AM, JR^ said:

    Agreed too. Creating a Monster App for that would be inferior in every way to Postman! And check out the tutorial from Joris, it's easy to use and cover a LOT of APIs :) 

    There is also the swagger.json file that can be used to import all the API's into PostMan.   Don't see that be mentioned in that tutorial.  That collection.json link seems to be a subset (?) of that.

  10. There is a monster developer app that works just fine.  Not maintained though.  There is one tiny fix needed that has never been merged.

    https://github.com/siplabs/monster-ui-apiexplorer/pull/6

    I just use Postman now.  Bit of a learning curve but anyone messing around with developer level stuff should not have problems.  Just have to put in the time to learn it.   

    It is NOT 'easy' as in "I like using iPhone/Mac because it's easy".  It's easy as in "I develop cloud solutions in Erlang,PHP, Javascript and PostMan is easy".

  11. 36 minutes ago, Karl Stallknecht said:

    @Logicwrath I've read tons of posts from people who had to do this exact thing...we had one customer that we did it for and it worked, but luckily the root issue went away so we could remove the VPN and just go back to the normal setup. I've always been afraid it might start back up at any of our clients though.

    I don't know what else would cause problems to disappear by adding VPN other than throttling.

  12. 2 minutes ago, Logicwrath said:

    Assuming this is true.  What is the easiest way to stop giving them the option to throttle it?  Does encrypting the audio mask it enough or is something like a VPN required?

    I have read plenty of posts over the years where users setup a VPN to their hosted PBX and all audio issues cease to exist.  I would absolutely hate to be in this situation.  It would be great if just encrypting the audio would hide this enough to stop Comcast from filtering the traffic but I suspect the unencrypted signaling traffic would give them the ability to identify which traffic to shape or sabotoge.  I believe as Net Neutrality laws get weaker we will see more specific anti-competitive actions being taken by providers like Comcast.

    You could certainly test the theory by adding a VPN.

  13.  

    On 9/23/2017 at 9:25 AM, esoare said:

    Don't want to high jack this. 

    Any us-west.p.zswitch.net West Coast Data Center customers with "Comcast" having issues? 

    Brought 3 customers on-board over the past Month 8-10 forward. And they seem to have issues. Spent about 1-3 cumulative man days on one customer in troubleshooting.

    Pulling hair out...oh wait, hair is just jumping ship. ;) 

    It is rumored that Comcast throttles SIP.  I know I have seen some issues with Comcast on residential plans.  Could just be that the Comcast network is getting congested in some areas at some times of the day too.

  14. right now if you type sup -h you get 

    Usage: sup [-?] [-n [<node>]] [-c [<cookie>]] [-t [<timeout>]] [-v]
               [<module>] [<function>] [args ...]

      -?, --help     Show the program options
      -n, --node     Node name [default: kazoo_apps]
      -c, --cookie   Erlang cookie [default: change_me]
      -t, --timeout  Command timeout [default: 0]
      -v, --verbose  Be verbose
      <module>       The name of the remote module
      <function>     The name of the remote module's function

    It would sure be nice if it output all the sup commands.  

    I generate them using the included script

    mkdir /usr/doc
    
    /opt/kazoo/lib/sup*/priv/build-autocomplete.escript \
    /etc/bash_completion.d/sup.bash /opt/kazoo > /usr/doc/sup_commands

    There are about 800 of them.  To shorten that up could maybe take an argument so if someone were to type in

    sup -h ecall

    it could show all the commands that start with sup ecallmgr etc.  Maybe even autocomplete.

  15. On 7/13/2017 at 10:44 AM, Anthony Manzella said:

    Thanks guys. I wanted to give back to the community :)

    @mc_ Yes I will post it there soon

    @Darren Schreiber Feel free to copy :)

    If you want to "give back to the community" perhaps you should not be copying a lot of it from another website and taking credit without giving any to the work done by the website.  In particular the captagent part where the similarities are beyond coincidental

    https://www.powerpbx.org/content/homer-voip-monitoring-install-guide-v1

×
×
  • Create New...