- VoiceOps - lists.voiceops.org

Verizon SIP DTMF issues in Orlando Florida
by jared＠compuwizz.net Jan. 25, 2012

Jan. 25, 2012

Things were quiet... We are experiencing DTMF problems with Verizon Wholesale for DIDs in Orlando, Florida. This started last night. Our other VZ DIDs work fine.The problem doesn't exist when called from Sprint or Verizon cell phones, but do when called via our provider trunks and Verizon landlines. Is anyone else seeing something similar? Thanks! Jared

1 0

Broadsoft Device Management vs. Enhanced IP Config
by RDawson＠alliedtelecom.net Jan. 18, 2012

Jan. 18, 2012

The shop I came from used Enhanced IP Config for endpoint provisioning so I am used to just setting a DHCP option and being done with it. The install I am just completing at my current employer makes use of Device Management and from what I am seeing you have to configure each phone to pull from the appropriate phone model folder which would require touching every phone? I assume there is a way to automate this process? Perhaps I am just being stupid and overlooking the obvious? I am digging through the Polycom configs now to see if you can do something like on the SPA phones i.e. macro substitution. Anyone tackled this?

1 0

Good rates for termination
by aussiesystems＠gmail.com Jan. 15, 2012

Jan. 15, 2012

Hi All, I have very good rates for termination in Bangladesh (All routes). Minimum traffic guaranty required. If interested please knock off list. Regards Aus

2 1

Local calling areas & 7-digit dialing (NANP)
by nathana＠fsr.com Jan. 12, 2012

Jan. 12, 2012

So we have 7-digit dialing in place for NANP destinations. The implementation is really stupid-simple: if 7 digits are dialed, take the originating number's area code and tack it on to the front of the dialed number. I am pretty sure this is how most commercial ITSPs do it (as tested also on Vonage and Packet8). But for certain areas, this doesn't properly mimic the 7-digit dialing that people who still have a POTS circuit from their LEC are used to. Take ours for example: I'm in Moscow, ID (NPA 208). We sit smack-dab on the WA/ID state border. 8 miles to the west of us is Pullman, WA (NPA 509). Both cities have the same ILEC: Frontier (f/k/a Verizon f/k/a GTE). There has been an understanding here since (I think) the mid-80s that calls between Moscow and Pullman are and will remain local. But on top of that, if you dial a Pullman NXX from Moscow or a Moscow NXX from Pullman as 7-digits, the call is patched through even though the NPA is different and even though (in some cases) both NPAs have NXXes that overlap with each other (although the corresponding NXX in the same NPA as the caller would be considered a long-distance call in all cases I can think of). The ILEC phone switch still does the "right" thing. It's been this way for YEARS, and people here are used to it. Now say I wanted to implement something like that for our customers. I know what the special exceptions are for this local market, and could probably make it work on our switch. But I only know about them because I've lived here and know the drill as a result. And I don't know how common or not this kind of thing is in other areas where you might be on the geographical edge of one's NPA(s). So the question I have is, is there some kind of central resource/authority that I can go to in order to find out what the dialing rules are for a given rate center (mandatory 10-digits/7-digits only within your own NPA/7-digits for certain local NPA-NXX outside your own NPA)? ...or is the only way to know for sure to find out from the locals? -- Nathan

4 3

T.38 re-invites
by nathana＠fsr.com Jan. 10, 2012

Jan. 10, 2012

This might not be the most appropriate forum for such a question, but given that implementation bugs in either NOC gear or CPE gear can cause headaches for network operators, I offer this here in the hope that perhaps a fellow VoiceOp here may have run into this before and knows the answer... It is my understanding that with SIP, *either* party to a call can send another INVITE (a so-called "re-invite") at any time during an active session; this could be used to change the endpoint of a call or redirect it elsewhere, and is also commonly used to renegotiate the media in use (audio, video, image, and associated codecs) without dropping the call even while the endpoints remain the same. Does this hold true, though, for re-invites whose purpose is to switch from an RTP audio stream to a T.38 UDPTL stream? Can *either* peer send that INVITE? Or is there a rule -- spoken or unspoken -- that states that a T.38 re-invite can only be initiated by the *receiver* of the fax, and not the transmitter? I have some ATAs that appear to send out a T.38 re-invite upon detection of a fax tone regardless of whether the ATA placed the call or answered the call, and if I am understanding what I'm seeing in my packet captures, I think the fact that these ATAs do this even when they are going to play the role of the T.38 transmitter is confusing the heck out of my (Asterisk) SBC and the termination provider. But I can't find any concrete evidence to support the idea that T.38 re-invites should only be initiated by the receiver. -- Nathan Anderson First Step Internet, LLC nathana at fsr.com

5 5

Broadsoft SIP Trunks and ILD Fraud
by zak＠simplesignal.com Jan. 10, 2012

Jan. 10, 2012

Good Morning Voice OPS Is anyone else experiencing anything like this? If so please share what you have done / or will to make it stop We have a series of smaller SIP trunk customers using Broadsoft trunk groups. By design the trunk groups have a concurrent call limitation based off the customer?s order. These smaller SIP trunks groups when compromised are able to run up HUGE fraud bills even tho they only have 5 or 6 SIP trunks. Needing to know if anyone else is seeing this that has Broadsoft and what was done to protect yourselves? Otherwise Happy NYE J Zak Rupas VoIP Engineer *SimpleSignal* 3600 S Yosemite Suite 150 Denver, CO 80237 One Number Rings All My Phones: 303-242-8606 SimpleSignal.com <http://www.simplesignal.com/> | Blog<http://www.simplesignal.com/blog>| Facebook <http://www.facebook.com/SimpleSignal?ref=ts> | Twitter<http://twitter.com/simplesignal>

9 16

Acme Packet/Broadsoft/ENUM
by RDawson＠alliedtelecom.net Jan. 6, 2012

Jan. 6, 2012

Is anyone using ENUM with their Acme/BS deployment that wouldn't mind sharing a snippet of their zone file showing the proper record configuration? Thanks, Rob

4 9

Australian Broadsoft Sales Contact
by nick＠inticon.net.au Jan. 5, 2012

Jan. 5, 2012

While not entirely ontopic Is anyone on this list able to put me in contact with someone who can assist with Broadsoft presales? I've had no luck with the online contact form and was unable to get anyone to call me back after calling through late last year. Cheers Nick Brown.

2 1

please unsubscribe
by andrew.warburton＠aapt.com.au Jan. 5, 2012

Jan. 5, 2012

thanks! *Andrew Warburton* Business Development Manager | Wholesale AAPT Limited, 180 - 188 Burnley St Richmond, VIC 3121 *P +61 3 *8308 3838 | *M **+61 426 779 333* * * This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it.

2 1

Voice Mail retention guidelines
by ujjval＠simplesignal.com Jan. 4, 2012

Jan. 4, 2012

Hi All Do you have any specific guidelines in your SLAs around how long you retain customer voicemails? Is there any legal requirement ITSPs have to fulfill regarding this at federal or state levels? Appreciate your input. Thx, Ujjval

4 3