May 2015 - VoiceOps - lists.voiceops.org

Maintenance for Performance Technologies SEGway
by scott＠socket.net May 17, 2017

May 17, 2017

We have been using a set of PTI SEGway x201s with point code emulation for a number of years now. We also have an unlicensed spare in stock. The maintenance contract renewals are due and the two quotes I've received are quite high. I know of at least one other company that has chosen to drop the vendor maintenance and take care of that in-house. I would like to hear from anyone that is currently using SEGways and find out what they chose to do for maintenance. I would also be very interested to hear of any bad experiences from chosing the in-house option. Thanks. Scott Stratman Network Facilities Manager SOCKET 573-999-4376 scott at socket.net 1-800-SOCKET-3 www.socket.net

3 2

Calls to Verizion Failing
by tim.donahue＠gmail.com May 18, 2015

May 18, 2015

Hi all, We have a client complaining that calls to the 818 area code are failing with a "No circuits available" message. The only common link we have found is the calls are terminating over our Verizon Wholesale trunk. We have other calls completing without issue across the rest of the country. I don't know why Verizon would be generating an audible error message instead of sending us a SIP 503 error code so we could progress on to another carrier, which is what we have always seen them do in the past. Is anyone else seeing a similar behavior on Verizon? Tim Donahue

3 3

Verizon all circuits busy
by peeip989＠gmail.com May 14, 2015

May 14, 2015

Anyone having any issues with "all circuits busy" messages, specifically to Verizon DIDs? We are hearing complaints of this, primarily from wireless callers and (I think) mostly east coast. Our trunks with VZ look normal, but was just wondering if maybe there is a capacity issue between wireless and wireline, or if this problem may be isolated to us (or to our region -- Philly metro). Thanks, Pete

3 3

CLEC List?
by ryan＠finnesey.com May 13, 2015

May 13, 2015

Good morning I know at one point there was an active CLEC listserv is this no longer the case I can't seem to find it. Cheers Ryan

2 3

SIPNOC - tech and business methods make it worth attending
by lindsey＠e-c-group.com May 11, 2015

May 11, 2015

Folks -- I like the SIPNOC conference <http://www.sipforum.org/content/view/369/270/>, the meeting of we who do VoIP in a serious way. Sure, you can read the <http://www.sipforum.org/component/option,com_docman/task,cat_view/gid,149/I…> PDFs <http://www.sipforum.org/component/option,com_docman/task,cat_view/gid,138/I…> online <http://www.sipforum.org/component/option,com_docman/task,cat_view/gid,123/I…> afterwards <http://www.sipforum.org/component/option,com_docman/task,cat_view/gid,111/I…>. But that's just smelling the aroma, not eating the food. Here are some of my favorites over the years: -- Engineering SIP Timers. Samuel Rausch of Comcast talked about how they tuned and tested the SIP timers, T1, T2, etc., and gave an overall introduction to all the timers. -- A tour of SIP over IPv6 and real-world stories on deploying SIP over IPv6. Which headers need to be changed? -- XO's Method for onboarding SIP trunking customers with self-tests. The key idea here: don't certify. Let customers run the tests and have infrastructure that makes it easy for the service provider to determine if they work. -- Lots of details on Faxing over VoIP. Including insight on the T.30 codes and acronyms, how T.38 and VoIP makes it harder, and workarounds used in the T.38 implementations. -- Bill Salmon of InComm focused on how to manage the risks of migrating to VoIP carriers you can't trust; e.g., "feathering" traffic to a new carrier without exposing your entire customer base. (This is really a very important idea when you can't completely trust a new service.) -- Finding and working around RTP Media Problems, like big jumps in timestamps, and changing RTP streams with new SSRCs in a talk by David Hiers of ADP. -- Nasty problems in RTP and audio quality that can be fixed in SBCs or other middleboxes. These talks are given by the people who write the software that does it. If you want your company to be associated with such in-depth coolness, sign up to sponsor. <http://www.sipforum.org/content/view/369/270/#sponsorships> This year at SIPNOC, Sherwin Crown and I are teaching a day-long technical intro to VoIP on June 23. If you need to get up to speed fast, bring your questions and your manager. SIPNOC is just outside the Washington-Dulles Airport <http://www.sipforum.org/content/view/369/270/#venue>. Register online <http://www.sipforum.org/content/view/369/270/#registration>, or shoot me any questions. --- mailto:mark at ecg.co tel:+1-229-316-0013 http://ecg.co/lindsey

1 0

Rural call completion hotline
by peter＠4isps.com May 6, 2015

May 6, 2015

http://www.telecompetitor.com/verizon-rural-call-completion-hotline-launche… -- Regards, Peter Radizeski @ RAD-INFO INC Circuits * Bandwidth * Consulting (813) 963-5884

10 13

Rural call completion hotline
by april＠teliax.com May 6, 2015

May 6, 2015

Spent most of Monday watching the presentation. Kudos to Verizon for making it publicly available. If anything, it's a window into the industry's feelings on RCC and perceived pain points. It's good information for a mid-size LCR/IXC to have when working with larger carriers. At times, the talks felt a little finger-pointy with RLECs always being painted the victim, and not (to Jay's point) sometimes complicit in their own "problems." It was a little harsh to hear some of the rhetoric against "bad actor LCRs," and the open source community, especially having spent so much of our time building an advanced LCR network, taking trouble ticket reports seriously, and doing it all with FreeSWITCH/Kamailio and the ilk. On the flip side, having worked with LCR carriers who have absolutely no idea what they're doing is infuriating and makes the rest of us look bad... Rural call completion is definitely A Thing, and will continue to be A Thing even with the advent of mobile networks, a move to packet-switched (VoLTE in the countryside, anyone?) technologies, and especially with the race-to-the-bottom attitude that so many carriers (LCR or not) seem to take. Quality (however you measure it), as usual, is the first thing to go, and the entire industry suffers for it. The take-away for me was, choose carefully your vendors, manage them tightly, don't save a penny to lose a dollar, and that when it comes to being an LCR, reputation is everything.

1 0