- VoiceOps - lists.voiceops.org

International (Non-US/Canada) Termination Providers
by ivan.kovacevic＠startelecom.ca April 8, 2019

April 8, 2019

Hello, We have been struggling to find good international routes. We mostly handle contact centre traffic in NA and do not have much traffic ($500ish per month) internationally, but it has been exceedingly painful to manage. We've tried a couple of carriers (Level3 - expensive and bad, TATA - cheaper but bad and will randomly block traffic, couple of CLECs who also offer A-Z). Financially it's not worth the hassle and managing the providers, but our contact centre clients do need to be able to make non-contact centre international calls on occasion, so we have to support it. Any suggestions? <http://www.startelecom.ca> *Ivan Kovacevic* *STAR TELECOM* *www.startelecom.ca <http://www.startelecom.ca>* -- NOTE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by replying to this email, and destroy all copies of the original message.

6 5

Hotel Phone
by kuylenj＠eastex.com April 5, 2019

April 5, 2019

I've never heard of any other 911 requirement for hotel or business phones outside of not have to dial 9 to dial 911, ie 9911. Kari's Law. Can anyone provide a link with more information? Thanks. Important/Confidential: This communication and any files or documents attached to it are intended only for the use of the person(s) or entity to which it is addressed. It contains information that may be confidential and exempt from disclosure under applicable law. If you are not the intended recipient of this communication, you are hereby notified that the copying, disclosure, distribution, storage, retransmission or other use of this communication is strictly prohibited. If you have received this communication by mistake, please notify the sender immediately and destroy all forms of this communication (electronic or paper).

10 14

[outages] flowroute increased 2400 percent belgium ?
by beckman＠angryox.com April 5, 2019

April 5, 2019

An interesting method to avoid calls while there is a known outage. Increase rates by 24x and hope nobody uses it! Maybe that rate puts Belgium in a rate that will fail for everyone. Creative, though bizarre. Izzy -- how did you notice? Curious what monitoring you might have in place for such major changes. On Fri, 5 Apr 2019, Ryan Collins via Outages wrote: > Received a notification from Voxbone this morning regarding a large network outage in Belgium: > > Dear Customer, > > We're currently investigating a network outage in Belgium and we're working on a quick resolution. > > We are sorry for any inconvenience this may cause. Please open a ticket and refer to superticket # 192462 if you need more information on this issue. > > > > >> On Apr 5, 2019, at 13:53, Izzy Goldstein - TeleGo via Outages <outages at outages.org> wrote: >> >> One of our divisions was using flowroutes for international termination >> and we noticed prices to Belgium increased by about an astonishment %2400 >> >> did anyone else notice this ? >> >> who are you using for International Termination ? >> >> who else has the fraud protection like they use ? >> >> -- >> Izzy Goldstein >> Chief Technology Officer >> Main: (212) 477-1000 x 2085 <tel:(212)%20477-1000> >> Direct: (929) 477-2085 <tel:(929)%20477-2085> >> Website: www.telego.com <http://www.telego.net/> >> >> <http://www.telego.com/> >> >> Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. >> >> TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w> >> _______________________________________________ >> Outages mailing list >> Outages at outages.org >> https://puck.nether.net/mailman/listinfo/outages > > --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman at angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------

1 0

flowroute increased 2400 percent belgium ?
by igoldstein＠telego.net April 5, 2019

April 5, 2019

One of our divisions was using flowroutes for international termination and we noticed prices to Belgium increased by about an astonishment %2400 did anyone else notice this ? who are you using for International Termination ? who else has the fraud protection like they use ? -- Izzy Goldstein Chief Technology Officer Main: (212) 477-1000 x 2085 <(212)%20477-1000> Direct: (929) 477-2085 Website: www.telego.com <http://www.telego.net/> <http://www.telego.com/> Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>

1 0

Hotel Phone System
by colton.conor＠gmail.com April 4, 2019

April 4, 2019

Anyone have recommendations on brands and models to deploy for a hotel? We use Broadsoft as our voip switch, but the though of using standard licenses for a 100 room hotel would be expensive in monthly license cost alone. Hotel only wants 10 phone lines, so we are thinking about providing an onsite PBX with 10 SIP trunks as the input.

8 10

Kamailio Managed Cloud
by abalashov＠evaristesys.com April 2, 2019

April 2, 2019

For immediate release: ATLANTA, GA (1 April 2019)--Following its long tradition of forward-thinking innovation in open-source Real-Time Communications (RTC), the leadership of the Kamailio SIP server project (formerly known as OpenSER) has launched the Kamailio Managed Cloud (KMC). Alex Balashov of Evariste Systems and Fred Posner of The Palner Group were among several key North American stakeholders on hand to discuss it further. As Posner told us, "Kamailio Managed Cloud is a new, best-of-breed managed Kamailio hosting environment. We provide elasticity by leveraging human capital. Using our patent-pending Orchestration Turk system, our managed cloud technicians will purchase your SuperMicro bare-metal server, known as a KamBox, drive to the data centre, and rack-and-stack it on demand -- all in response to a SOAP API call! And when you want to remove your on-demand KamBox, just issue a 'delete' operation and we will decommission the hardware -- live!" "Dedicated KamBox colocation really puts the Management in Managed Cloud," emphasised Balashov. "But that doesn't mean we keep the customer out of the loop. We are using the most modern XMLHttpRequest and 'AJAX' techniques to provide a real-time dashboard with KamBox status to all users, though it will not work with Internet Explorer 6 -- we're addressing that." "Anyway, there are numerous other cloud platforms out there, many of which rely on virtualisation and automated orchestration and the like. It really takes the human touch out of the equation and gives the short shrift to quality, while also taking away jobs. And besides, how can a so-called 'virtual' machine be truly carrier-grade?" Kamailio Managed Cloud launched in two principal regions today -- US-EAST-1, located in Jacksonville, Florida, USA, and EU-CENTRAL-1, based in the booming tech hub of central Europe and birthplace of OpenSER: Berlin, Germany. Unnamed sources tell us that strategic expansion is planned for several other regions, including Flint, Michigan, USA. The mechanics of Kamailio Managed Cloud have invited questions about how other elastic cloud resources are managed, more especially elastic storage. According to KMC senior management, storage is provided via a mechanism developed by ASIPTO StorageWorks. ASIPTO chief Daniel-Constantin Mierla was on hand at the KMC launch to explain: "It's very easy. When a customer requests more space with a simple and lightweight SOAP call with just a little custom XML namespaces, then depending on the region, Fred or I receive an SMS on our smartphones from our advanced PHP backend and drive to the data centre to insert another hard drive into one of the KamBox's several drive bays. We are using the latest in advanced mobile communications, SMS, to ensure fastest response time. Of course our service level is comprehensive and includes Managed Partition Table Labelling and Managed LVM Insertion. Also there is optional Managed Filesystem Formatting for a complete portfolio of managed services. ASIPTO StorageWorks moves at the speed of global e-business. Just text us your desired filesystem layout and partitioning scheme. It is really that easy!" When asked about business focus, marketing turnaround veteran Henning Westerholt, Executive Vice President of Business Development for KMC responded: "Our target customer is a socially conscious Millennial-run corporation or start-up who see value in the unique blend of managed services and an artisanal, hand-crafted, organic approach that is compatible with social justice and takes a people-centric view." Asked to elaborate upon his vision of social justice, Westerholt added: "Virtualisation, orchestration and auto-scaling take the people out of the equation, and Kamailio is, in the end, about people, as communication in general is about people. What would it be without the people? Moreover, these mechanisms take away gainful opportunities from hard-working university graduates. Kubernetes, Docker Swarm, VMWare, and KVM contravene the social policy objective of full employment." At press time, Posner, who also heads up KMC Labs North America, was said to be lending his pioneering business vision and knack for seeing around technology trend corners to intensive work on next-generation, bleeding-edge functionality for KMC. While Posner was tight-lipped about the specifics, he did state that the 'dispatcher' module is slated to be deprecated in favour of a "human load-balancing approach to SIP requests that is both cloud-native and eco-conscious". Industry analysts agree that protocol-aware load-balancing strategies are complicated and that the application of human judgment to the problem represents a fertile field for dynamic innovation and investment. Reports from regional press confirm that KMC Labs are in the process of building a fullfilment centre for this innovative offering, said to be branded "Central Switchboard", at an undisclosed site in Bangladesh, where thousands of "Load Balance Operator" jobs have been advertised in and around the Dhaka market. -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 1

Keyless VoIP Phone
by kuylenj＠eastex.com March 30, 2019

March 30, 2019

Any suggestions for a SIP handset without any keys? This will be setup similar to a lobby phone or emergency phone. Thanks Important/Confidential: This communication and any files or documents attached to it are intended only for the use of the person(s) or entity to which it is addressed. It contains information that may be confidential and exempt from disclosure under applicable law. If you are not the intended recipient of this communication, you are hereby notified that the copying, disclosure, distribution, storage, retransmission or other use of this communication is strictly prohibited. If you have received this communication by mistake, please notify the sender immediately and destroy all forms of this communication (electronic or paper).

5 5

Request for Opinions: High density ATA's
by ryandelgrosso＠gmail.com March 26, 2019

March 26, 2019

I have found myself with a number of hospital opportunities and servicing the staff with IP phones is a no-brainer, however there is the need for multi-hundred room connectivity for patient room phones and the staff mandate is to keep it analog because "ip phones there will grow legs". I am looking for 24+ port density with amphenol connectors, and ideally some kind of rudimentary internal routing so i dont need to register all 24 discreet ports and can route by some header (to or uri) within a single registration. Right now im looking at AudioCodes and the Sangoma Vega series. Obihai would be my natural choice here but don't have anything that fits my density requirements. Any opinions on these or others I should consider. Anyone deploy these and can speak to the experience? Thanks in advance -Ryan

9 13

Request for Opinions: High density ATA's
by nathana＠fsr.com March 26, 2019

March 26, 2019

Oh, I also meant to mention the following: Though I haven't tested use of RPID on inbound, I have tested it on outbound and it works. If you don't even want to bother with registration at all, and you anticipate that each TA will have a static IP, these TAs support that, too ("Register Mode" > "Service Provider"). -- Nathan -----Original Message----- From: Nathan Anderson Sent: Tuesday, March 26, 2019 2:36 PM To: 'Ryan Delgrosso'; 'voiceops at voiceops.org' Subject: RE: [VoiceOps] Request for Opinions: High density ATA's So I can confirm that, with the latest firmware, it is possible to have these Yeastar TAs perform a single registration to a SIP proxy/registrar and still have each FXS port be individually addressable. Though it has been a long time, thinking back, I'm almost sure this wasn't the case when we first started using these, which is why I wasn't sure (I've never used them in this way, although I have *wanted* to). It looks like at some point they addressed this, and either I wasn't aware, or if I had become aware at the time they released it, I didn't trust it enough based on past experience to put it into production anywhere. (The lack of this feature may have also been one of the things I was hoping to address by rolling my own firmware. Again, this was a long time ago...) The trick is to... 1) ...set the "Register Mode" for the "VoIP Server" to "Template Register" 2) ...set the "DID Number" field for each FXS port to a unique value 3) ...address that particular FXS port in the INVITE by using its given "DID Number" in the "To:" header If under "SIP Settings" > "Advanced Settings" you enable "trust" for "Remote Party ID", then you can probably address the FXS port by sending its "DID Number" in the RPID header instead (I haven't tested this yet). That addresses inbound. For outbound, you can control what it uses for the "From:" header in the INVITEs that the TA sends out on a per-FXS basis by making sure to set each FXS port's "Caller ID Number" field. Leave the "From User" setting/field black for the "VoIP Server" in question (which will globally override the "From:" and "Contact:" fields) UNLESS you also enable "SIP Settings" > "Advanced Settings" > enable "send" for "Remote Party ID", which will cause it to put the FXS CLID in the RPID header. I haven't found a way to get it to use PAI instead of RPID, and indeed it may not even be possible given the age of the version of Asterisk we are dealing with here (not sure there was any PAI header support in 1.6.x, and even if there was, the web GUI here does not seem to expose it). But I would think that if PAI was a hard requirement of yours, it would be easy enough to deal with via a small SIP proxy sitting between the TAs and your main registrar that rewrites RPID to PAI. Good luck, -- Nathan -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nathan Anderson Sent: Saturday, March 23, 2019 7:10 PM To: 'Ryan Delgrosso'; 'voiceops at voiceops.org' Subject: Re: [VoiceOps] Request for Opinions: High density ATA's This is a little "outside the box" maybe, but you can get 32 ports of FXS from the Yeastar TA3200 (https://www.yeastar.com/fxs-voip-gateways/) I've only ever used the 4- and 8-port versions which aren't rackmount and only have single-pair RJ11s, but supposedly the 1U 16-, 24-, and 32-port ones have both RJ11s on the front *and* Amphenols/RJ21s on the back. And the 3200 can be had brand-new for about ~USD$550/ea shipped all day every day, if you know where to look...so the only way I know how to beat these $-wise would be some refurbished Adtran TA924e (which are arguably a more solid unit anyway, both on hardware and software side). Though the price is right, these units definitely have their quirks. I'm not 100% sure they can do single registration per-unit instead of per-port...I'll pull one of my small-port-count ones out to test. They actually run Linux + Asterisk (ancient and very hacked-up/custom 1.6.2.x build as I recall) and for a while I contemplated building a custom ROM of my own for it from source in order to work around my own irritations, but last time I'd looked they hadn't released their internally-developed patches for either the kernel, Asterisk, or their build environment and I couldn't get them to budge on this, so I sicced the FSF and Digium legal teams on them...I think their attitude may have changed after that but I haven't had time to pursue further. Also, even if I get the patches, it appears that their analog interfaces are not based on Digium DAHDI reference designs like so many others, but is custom hardware (+ software drivers which they may not have any obligation to release sources for, depending on how their drivers actually link up to DAHDI itself), so it may be a fool's errand regardless. -- Nathan -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Ryan Delgrosso Sent: Thursday, March 21, 2019 8:56 AM To: voiceops at voiceops.org Subject: [VoiceOps] Request for Opinions: High density ATA's I have found myself with a number of hospital opportunities and servicing the staff with IP phones is a no-brainer, however there is the need for multi-hundred room connectivity for patient room phones and the staff mandate is to keep it analog because "ip phones there will grow legs". I am looking for 24+ port density with amphenol connectors, and ideally some kind of rudimentary internal routing so i dont need to register all 24 discreet ports and can route by some header (to or uri) within a single registration. Right now im looking at AudioCodes and the Sangoma Vega series. Obihai would be my natural choice here but don't have anything that fits my density requirements. Any opinions on these or others I should consider. Anyone deploy these and can speak to the experience? Thanks in advance -Ryan _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

1 0

Canadian (LATA 800) Calls routed to wrong CIC / Verizon contact?
by ivan.kovacevic＠startelecom.ca March 25, 2019

March 25, 2019

Wondering if anyone has come across discrepancies in call rating between originating carrier and their routing (CIC) carrier. So we have a scenario where calls with Canadian ANI are being routed to our non-Canadian CIC (US Carrier). Our US carrier is treating these calls as Canadian, based on ANI. The carrier (Verizon) handing calls off to our US carrier (instead of to our Canadian carrier) does so based on a different criteria (probably fact that they originate on one of their trunks in the US). So one of the two carriers here is wrong - either Verizon who should not be handing calls over to our US carrier, or our US carrier who should not be rating the calls as Canadian. This is what I got from our US carrier: *"TF rating jurisdiction will use the dipped LRN of the CPN first, then moves to the CPN (if no LRN present), then the orignum (if no CPN) and lastly the NPA-NXX of the originating FG-D trunk. Given that all of the calls I?m seeing coming out of this Pittsburgh area have a CPN value, we?d be dipping that CPN to figure out where it was coming from, and if that returns a Canadian number, we?d treat it as Canadian origination. That 504613 number would only be used if we got no CPN at all on the call."* The practical impact is that our cost is twice as high for our Canadian calls with the non-Canadian carrier. I am sure there is potential for this sort of discrepancy at other LATA level (if someone is using TF LCR or LATA based routing). If there is a Verizon contact on the list, I would be curious to get their opinion on why these calls (have examples willing to share) are rated as US, and how is Verizon's rating different from our US carrier. Thanks, <http://www.startelecom.ca> *Ivan Kovacevic* *VP Client Services* *STAR TELECOM* *5915 Airport Rd. Suite 610, Mississauga, ON L4V 1T1 Canada**www.startelecom.ca <http://www.startelecom.ca>* -- NOTE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by replying to this email, and destroy all copies of the original message.

1 0