January 2011 - VoiceOps - lists.voiceops.org

Terminating LD Traffic
by naushit＠yahoo.com Jan. 9, 2011

Jan. 9, 2011

Eric, You did not mentioned LATA or Area, I assume you are looking for nation wide connectivity? We are New York based CLEC, and we have plenty of extra bandwidth to ILEC End offfice and Tandem office. We would be happy to share bandwidth at cost and collocate your equipment in our data center in most affordable way. We are also interested in trading Chicago DIDs ( or any other area DIDs too) for NYC DIDs . Please contact me off the list. -Naush. From: Eric Hiller <clec at cygnustel.com> To: voiceops at voiceops.org Cc: Sent: Saturday, January 8, 2011 7:25:39 PM Subject: [VoiceOps] Terminating LD Traffic >From my understanding if you want to terminate Long Distance traffic to the LECs exchanges you have to have end office trunking. Being that end office trunks are special access the only affordable way to do this is to be collocated in the exchange or have 3rd party trunking into the exchange. I would like to start looking into this as we are having to collocate in an increasing number of exchanges and I would like to try to recoup some money by terminations if possible. Does anyone else do this or have any advice on the matter? Thanks guys! -Eric _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

2 1

"Ring Down" Phone
by robert.dawson＠mindshift.com Jan. 7, 2011

Jan. 7, 2011

I am sure I have seen these before but I am not turning anything up . . . basically looking for an endpoint with no keypad that is programmed to dial a specified number when it goes off hook - just like a door box. Anyone know of anything offhand? Thanks, Rob

6 6

Porting numbers from Centurytel
by mylists＠battleop.com Jan. 4, 2011

Jan. 4, 2011

Does anyone know of a SIP provider that can port numbers from Centurylink ILec markets across the country? We run into this often where a customer has remote locations that are in Centurylink territory and we can't port their numbers back to our network. Most of these markets have small Centurylink footprints or they are somewhat rural. Richey

1 0

Polycom Ghost Ringing
by clec＠cygnustel.com Jan. 3, 2011

Jan. 3, 2011

We are having the strangest issue that I have seen for some time. A customer of ours with Polycom phones (4x ip335, 2x ip550) will occasionally (maybe 1 in 50 calls) hear ringing on the line along with the other party. It has happened on both incoming and outgoing calls across apparently all of the phones. We use ip550 in our office and have never had such a problem (we run the same firmware as well, although their hardware is newer). It can be fixed if the person using the phone puts the other person on hold and then takes them off hold. They have just been doing this by double pressing hold so the other party doesn't even realize it. Call setup on these calls is all normal: invite from pbx to phone 100 trying from phone to pbx 180 ringing from phone to pbx 200 ok from phone to pbx ack from pbx to phone <start rtp> I have listened to the RTP and there is absolutely no ringing! At this point I am entirely out of ideas! Does anyone have anything to suggest or has possibly encountered this before? Thanks for any ideas or help! -Eric

4 3

Is call forwarding in Polycom phones fundamentally broken?
by jdupuy-list＠socket.net Jan. 3, 2011

Jan. 3, 2011

I've encountered this problem in the past, many years ago, when working with Asterisk farms. I'm encountering it again now working with the Broadsoft platform: Polycom Soundpoint IP phones can do call forwarding in two ways: client-side and server-side. In client-side mode, the phone itself does the forwarding. If the phone is unreachable for any reason, the call forwarding never actually happens. That is because the call server doesn't know to forward the call and the phone isn't reachable to do the forwarding. By default, the call usually goes to VM, which is not what the user wanted. So, it works most of the time, but not predictably. So, it is broken by design. (Plus with the half-broken NAT support on the Polycoms, any forwarded calls needlessly burn two audio streams because the call is not likely to transfer off the handset. But, I'll refrain on Polycom NAT commentary for the moment...) So, we go with server-side... In server-side mode, the phone refuses to show that the phone is forwarded anywhere on the screen. It is not uncommon for the user to "wonder why they aren't getting calls" if they forget to cancel the forwarding. So, it is also broken by design. (Albeit, not as badly as client-side, since at least it will always function.) This does not appear to be a bug, since it is well documented by Polycom. The only work-around I've come up with is writing a customized hack that modifies the idle screen, but that is far less than ideal. :) In general, I really like Polycom phones, but may have no choice but to switch to cisco/aastra/etc. But, before I do, has anyone come up with a better work-around? John

4 4