- VoiceOps - lists.voiceops.org

No RTP stream during 183 w/SDP via Peerless?
by april＠teliax.com June 5, 2015

June 5, 2015

Hi all, I'm seeing a rash of calls this week, egressing Peerless, with no RTP stream during 183. First it looked like multiple vendors (or a CPE issue) but checking SDP, calls exhibiting the behavior are originating from Peerless. Calls will receive a 183 Progress w/SDP, then 200 OK w/SDP, but no RBT or media is heard during the 183. Tickets are being opened with Peerless (and other ULCs who are using Peerless) but I'm curious if this is being observed elsewhere...

5 8

SIP 404 Not Found vs 603 Decline
by beckman＠angryox.com June 3, 2015

June 3, 2015

I offer a feature to our customers that allows them to configure their DID to respond with "This number is disconnected" message for specific, annoying callers, based on their CallerID. Some customers send a Busy signal (486 BUSY) for these annoying callers. It seems that some Robocallers will retry numbers that ring busy repeatedly, sometimes annoyingly aggressively. I'm switching the default to declining the call, which brings me to which SIP response is correct and/or ideal. >From the RFC: https://www.ietf.org/rfc/rfc3261.txt Section 21.4.5 404 Not Found The server has definitive information that the user does not exist at the domain specified in the Request-URI. This status is also returned if the domain in the Request-URI does not match any of the domains handled by the recipient of the request. Section 21.6.2 603 Decline The callee's machine was successfully contacted but the user explicitly does not wish to or cannot participate. The response MAY indicate a better time to call in the Retry-After header field. This status response is returned only if the client knows that no other end point will answer the request. We are currently sending a 603 Decline, which seems appropriate given the nature. However we also get calls to numbers we service which are not active, in which case 404 Not Found seems more appropriate. What is the real-world behavior of the calling party for these responses? If I change the cause code, will there be unintended consequences? Any suggestions or experience is appreciated. Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman at angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------

5 5

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

Polycom BLF w/ SBC
by david＠ringfree.biz April 27, 2015

April 27, 2015

HI All, Has anyone ever had luck with getting Polycom BLF to work through a non-Broadworks SBC? We're looking at internally moving to a SEMS based SBC.. However we've had 0 luck so far with getting any BLF from Polycom to function... Thanks David -- [image: Ringfree Communications, Inc] <http://ringfree.biz/> David Wessell / President 828-575-0030 x101/ david at ringfree.biz Ringfree Communications, Inc Office: 828-575-0030 / Fax: 888-243-7830 PO BOX 1994 Hendersonville, NC 28793 http://ringfree.biz This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Company Name is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.

6 5

(no subject)
by myaklin＠firstlight.net April 24, 2015

April 24, 2015

What ticks me off is the lack of the authorities and the largest telephone companies giving a crap about hunting down where these fraud calls are going and getting them shut down. Also are the large telephone companies even paying the terminating telephone company or just pocketing the fraud money themselves? Because they seem to enjoy billing the victims and if the victim does not pay they will turn off their service. Seems like a telephone number can be tracked right to the telephone company who delivers the call to the end user which means the end user can be questioned to determine what is really going on. Yes I know they go over seas but the worst telephone companies who know fraud is happening can simply be told we will no longer deliver calls to you period. Clean your act up or live in your own little cut off piece of the world. Or am I naive? This is not like hacking on the internet. These are telephone numbers which can easily be traced to exactly who is paying for the service and the telephone company terminating the call. Matt P.S. resending to the list because my new email address was not on the mailing list. my old was. just added it. ________________________________ From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Mark R Lindsey <lindsey at e-c-group.com> Sent: Friday, April 24, 2015 1:24 PM To: Rob Dawson Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] (no subject) I talk to a lot of service providers that are improving their security in the aftermath of fraud. When they're recovering from a fraud event: -- They're coping with a loss of tens-of-thousands of dollars. -- The ops teams must answer to senior management about how they let this happen. -- They're confounded to know how the attacker figured out their password scheme, or their phone config file names. -- Sometimes they're frustrated to find a silly mistake that was made long ago, and never fixed. -- Sometimes they're concerned about an insider threat. (Is somebody selling our list of MAC addresses necessary to download all the config files?) -- They may have legal questions, because in hosted PBX and SIP trunking, knowing exactly who's responsible for the security and who's got to pay for the fraud is unclear. So for several reasons, you'll find them in poor spirits, and seldom ready to chit-chat. All that said: good, informal relationships among the engineers and ops folks at different service providers can help a lot. Go to SIPNOC every year and meet your peers at other SP's. And go to your vendors' events, like the BroadSoft and Metaswitch customer meetings. Get to know some other tech folks, and keep in touch. And of course, we consultants can help too. People from ECG and other consulting firms do promise to keep secrets of our clients, but we also learn the techniques and know-how used by the fraud attackers and the defenders. --- mailto:mark at ecg.co tel:+1-229-316-0013 http://ecg.co/lindsey On Apr 24, 2015, at 13:06 , Rob Dawson <rdawson at force3.com<mailto:rdawson at force3.com>> wrote: I wasn?t necessarily thinking of a commercial solution, something more ad hoc, but they do have some pretty innovative and cool solutions. Rob From: Alex Hardie [mailto:ahardie at bellsouth.net] Sent: Friday, April 24, 2015 11:55 AM To: Rob Dawson Cc: voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: Re: [VoiceOps] (no subject) Have you looked at PinDrop? They specialize in toll fraud for both enterprises and carriers. Alex Hardie alex hardie | ahardie at bellsouth.net<mailto:ahardie at bellsouth.net> | +1 404 229 7635 On Apr 24, 2015, at 11:51 AM, Rob Dawson <rdawson at force3.com<mailto:rdawson at force3.com>> wrote: Anyone aware of a voice fraud mailing list or listing service? Something of a repository of new attack vectors and remediations or something . . . just thinking it would be cool to see what new attacks people are running into. If not, any thoughts on something like this? Rob _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops

1 0