[VoiceOps] verizon 399 response
jared at compuwizz.net
Fri Jun 25 10:55:49 EDT 2010
We saw this during interop, but calls placed fine. However when we went to
production, calls wouldn't go through. Turns out if your on e164+ they want
the callerid to be +1XXXXXXXXXX and if you are on their national dialplan,
they want it as XXXXXXXXXX instead.This is for rpid or p-asserted.
This was for their SIP 2WAY service, our outbound only isn't up in
On Fri, Jun 25, 2010 at 10:07 AM, David Hiers <hiersd at gmail.com> wrote:
> Do you peer with verizon?
> Do you get peppered with their custom "Warning: 399" headers inside
> their 200 responses? If so, have you ever gotten a decent explanation
> of these headers?
> VoiceOps mailing list
> VoiceOps at voiceops.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps