Calls completing but no audio

[Xponder1]

Mystery solved

Do not put a "&" in line display.
Working again. Thanks Brandon.

Would of never in a million years thought of that LOL.
I changed the line display yesterday at some point so best guess when the change took affect my line took a nose dive.

[dswartz]

You're kidding, I hope! Putting a "bad character" in the line display on vpanel keeps your calls from completing? WTH Sounds like some script somewhere is not sanitizing the input properly

[VOIPoTim]

You're kidding, I hope! Putting a "bad character" in the line display on vpanel keeps your calls from completing? WTH Sounds like some script somewhere is not sanitizing the input properly

This turned out to be a case of the PAP2 not liking the characters. We didn't imagine it wouldn't accept characters.

[Xponder1]

You're kidding, I hope! Putting a "bad character" in the line display on vpanel keeps your calls from completing? WTH Sounds like some script somewhere is not sanitizing the input properly

Brandon said he would be doing something about it today so that does not happen.

The call went pretty much like
Brandon "I see you have a & in your line display let me just clear that out.
Ok now reboot your ATA. OK let me make a test call."

It worked....
*sigh* I am just glad it is working again.

[frankd1]

A couple days ago, I had problem with calling two specific #s. I heard dead air, repeatedly called with no success, then the other party finally called me back asking if I needed help (calls were connecting and caller ID showing). I called support twice, and they changed the routing for those specific exchanges, which seemed to fix the problem. I understand and agree w/ Tim's strategy of limiting discussion of technical specifics, so the following is strictly me matching two disparate pieces of info and assuming they're related, but since Tim mentioned the big shift to bandwidth.com, I assumed my problem was related to shifting routes from level3 to bw.com, since I had no problem calling the #s before when level3 was the big kahuna. I readily and freely acknowledge I probably don't know what the frak I'm talking about.

[usa2k]

So the line#1/line#2 name feature is gone from ATA Preferences now.

[Xponder1]

This turned out to be a case of the PAP2 not liking the characters. We didn't imagine it wouldn't accept characters.

Thank you for your help Tim. Stuff happens. Perhaps others will read this and remember they used a "&" too. It's hard to link Vpanel issues with a ATA issue at least in my brain.

Then again I think I asked you the other day if its possible that Vpanel going down could cause a temporary outage because my line dropped the moment "The Planet" dropped off the planet. I actually enjoy helping get stuff fixed.

Have a great day.

[Xponder1]

So the line#1/line#2 name feature is gone from ATA Preferences now.

Just refreshed and can confirm that is the case. I would imagine it was taken out until a fix can be put in place. Probably very easy to just reset everyone to null to fix the problems and then resolve the issue.

[dswartz]

This turned out to be a case of the PAP2 not liking the characters. We didn't imagine it wouldn't accept characters.

Oh, ick. Well, better there than in your servers

[VOIPoBrandon]

Hey guys -- I've seen this come up a few times now where an invalid character "according" to PAP2 was put inside of the line display name, what is odd though is that these characters generally would be 100% fine, that is if the PAP2 was properly sending them to our SIP proxies "escaped". For the time being we have "disabled" this ability for everyone -- to prevent further adverse action and support inquiries regarding this, however shortly here you will be given the ability to alter it again, which we will handle from a server-side stand point, which will also mean that it will update 100% dynamically and not involve the PAP2 (thus rending the change instantly), in which case you guys will also be able to put in your common symbols without any problems.

Thanks guys!