January 2011 - VoiceOps - lists.voiceops.org

unsubscribe
by chris＠tidalwavetelecom.com Jan. 27, 2011

Jan. 27, 2011

Best Regards, Chris Chris Talbot Tidal Wave Telecom <blocked::http://www.tidalwavetelecom.com/> www.tidalwavetelecom.com (tel) +1.805.523.8187 This electronic transmission contains information and is confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify the sender immediately and delete the message.

1 0

h.323 breech and toll fraud case
by carlos＠televolve.com Jan. 27, 2011

Jan. 27, 2011

Lonny Clark wrote: > The guy dialing the number and the guy receiving the call may never know > that the call went through a hack - they may be just calling as normal. > It's the carriers in between that are scamming the other carriers to > bear their costs. According to the customer's carrier, the call path was: End user switch > Carrier SBC > Level 3 > Globalstar So I'm still not seeing where the profit is, unless it's a Globalstar reseller taking a cut of the incoming call charges. -- Carlos Alvarez TelEvolve 602-889-3003

2 1

Hosted Support Models
by robert.dawson＠mindshift.com Jan. 27, 2011

Jan. 27, 2011

How many of you selling hosted business services are using a tiered support model vs. first call being handled by a skilled resource? If you switched models either way what was the outcome? Thanks, Rob

3 2

Verizon DE/MD area issues
by sil＠infiltrated.net Jan. 26, 2011

Jan. 26, 2011

Out of utter curiosity, has anyone been experiencing any issues with calls to and around Delaware to Verizon endpoints? Because of number portability I can't confirm fully that *all issues* are Verizon endpoints, but I've been seeing an unusually high amount of problems with clients calling to numbers in DE and MD which appear to be Verizon owned (**SEFRDESFDS0 switch 302-629 exchange). 1361 failures today, first 20 (should I say, first and only 20) I checked turn out to be various VZ endpoints in the DE, MD areas. Anyone else seeing things out of the ordinary in those parts? Further is it me, or has Level3 also been acting a bit on the stupid side. -- =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ J. Oquendo SGFA, SGFE, C|EH, CNDA, CHFI, OSCP, CPT "It takes 20 years to build a reputation and five minutes to ruin it. If you think about that, you'll do things differently." - Warren Buffett 227C 5D35 7DCB 0893 95AA 4771 1DCE 1FD1 5CCD 6B5E http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x5CCD6B5E

2 1

LOA/CFA Chicagoland
by clec＠cygnustel.com Jan. 26, 2011

Jan. 26, 2011

Is anyone here capable of or know of anyone who is capable of (and wishing to) allow LOA/CFA on their ILEC collocations in Chicagoland. We are just looking for the ability to either rent a mux or some rack space for 911 DS0s. Any help would be GREATLY appreciated, I am pulling my hair out here! -Eric

3 3

Level3 Outage Orlando Area?
by cpena＠ststelecom.com Jan. 26, 2011

Jan. 26, 2011

An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110126/766ac215/at…>

1 0

using a T1 to extend PRI service and involuntary fax over sip
by mark＠noc.mainstreet.net Jan. 25, 2011

Jan. 25, 2011

I stumbled across a situation where a fax-to-email service gets inbound calls, from Carrier X, over a PRI into a cisco 5350 which then relays the calls, via an x-conn PRI, to a directly-attached linux box. This has worked for years. About a year ago, it was revealed that the above-mentioned PRI connects to the edge of Carrier X's SIP infrastructure. That is, calls start from some PSTN-connected fax machine, somewhere in the USA, go through a PSTN-to-SIP gateway, travel as SIP to the building where this cisco 5350 is, and then go through Carrier X's SIP-to-TDM equipment for delivery over the PRI to the cisco 5350. This led to some concern, since we all know that fax over SIP can be problematic. But everything was working, hundreds of faxes a day were pulsing through the system. Up until September the cisco 5350 was in the same building as Carrier X's TDM equipment. In late September, a point-to-point, B8ZS/ESF T1 was used to extend the in-building cross-connect between Carrier X and the cisco 5350. The cisco 5350, and related servers, are now eight miles away (both endpoints in Manhattan, using VerizonBusiness for the T1, both endpoints "on-net", no ILEC involved). Since November, maybe half a percent of the faxes fail to work. They get a communication error at the start, at the modem negotiation. The T1 circuit is clean. Some people think that failures may not have been reported/noticed in October, but they occured nevertheless. This would suggest that the previous set-up was a very delicately balanced system and the moving of the cisco5350 eight miles away, necessitating the use of a T1 to carry the PRI to the new location, may be the root cause of the failures. Occam's razor reasoning supports this. The grassy knoll people believe that, in November, Carrier X started an effort to wring more out of their SIP network. Perhaps they started using different peers in various parts of the country. Maybe their PSTN-to-SIP gateways were tuned to use less bandwidth. When asked, Carrier X answered a different question, in a fashion similar to a politician. I'm wondering whether any experts here have an opinion to offer? Thanks, -mark

8 14

Do you belong to RICA (Rural Independent Competitive Alliance)? I had never heard of it but just got a flier in the mail for their annual meeting in San Antonio? -Eric
by clec＠cygnustel.com Jan. 24, 2011

Jan. 24, 2011

Does anyone here belong to the RICA (Rural Independent Competitive Alliance)? I had never heard of it but just got a flier in the mail for their annual meeting in San Antonio? Thanks, -Eric

1 0

Matter of quality
by sip.vsp.5060＠gmail.com Jan. 21, 2011

Jan. 21, 2011

A large carrier with a national VOIP footprint indicated that they use average call length as their primary problem finder. If enough people quickly hang up and redial, they start looking for a bad gateway, circuit, etc. Reactive and coarse, but that's how they do things. -S For those on this list who'd be willing to share particularly from say an ITSP (Carrier) side, off-list, on-list, etc., what are the percentages for quality, system issues some of you are using for baselines/metrics. For example, I have one or two (alright maybe 10-20 at max) common 's:whiner:clients:g' who have caught management's ear. "My call to a cellular dropped after 120 minutes!@" From my POV, I have two maybe three common clients who are complaining... "Dropped call, call sounded garbled, etc., etc., etc" From my perspective, even if I had 1,000 of these calls in a day, it's less than .5% of the amount of calls I process. Nevertheless, we as engineers want to perform due diligence versus blurting the ever popular "told you so." This means tracking down all other carriers' issues (Comcast filtering anyone), any potential outages, and so on (you all know the routine). So long story (rambling) short, what are some of the gauges you guys (big boys not onesies twosies) use to measure quality metrics (amount of dropped calls versus successful calls, ARS ratios, MOS, etc). I use a combo of Acmes, NCites and soon to be Transnexus in the mix. Also, what pro-grade measurement tools are recommended, less I waste an hour @ CAIDA or similar. Requirements of tools in mind: MOS would be nice, tracing calls would be nice, storing SIP sessions would be cool. High volume traffic parsing (think 100s of gigs here) Making coffee, even cooler! (Beggars can't be choosy). For the vendors on the list selling tools, please don't solicit, I'd rather hear what peers have to say rather than spend time on the phone away from the beauty of figuring out why someone else's configuration/setup doesn't work. =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ J. Oquendo SGFA, SGFE, C|EH, CNDA, CHFI, OSCP, CPT "It takes 20 years to build a reputation and five minutes to ruin it. If you think about that, you'll do things differently." - Warren Buffett 227C 5D35 7DCB 0893 95AA 4771 1DCE 1FD1 5CCD 6B5E http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x5CCD6B5E _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

1 0

Regarding Matter of Quality
by CCurry＠telovations.com Jan. 20, 2011

Jan. 20, 2011

We use Palladion from IPTEGO. We looked at the entire market vendors for monitoring tools and this was head and shoulders above the rest. Specifically addressing your requirements, all calls and speech quality measurements and also the actual RTP if you want, is recorded in the database going back days or months if you require. So you can go back and find dropped calls. It will specifically detect the dropped call if signaling is not seen for a specified number of seconds. Alternatively you could look for a dropout of speech quality In addition to your other requirements, it obviously does MOS, packet loss and jitter etc. It has a nice message flow diagram, to trace a call from different geographic locations in your network. This is accessed from a simple drill down from the summary information. Also it can scale to very high volumes. It uses standard Linux hardware, so you can drop another quad/HEX core blade into your box and you are good to go unfortunately, it doesn't make the coffee. But it's cheaper than running these measurements on a network device such as an SBC etc. [cid:image001.png at 01CBB8A3.414DF840]

2 1