[VoiceOps] verizon 399 response

[Jared Geiger]

Hi David,

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
production yet.

Regards,
Jared Geiger

On Fri, Jun 25, 2010 at 10:07 AM, David Hiers <hiersd at gmail.com> wrote:

> Hi,
> 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?
>
>
> Thanks,
>
> David
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20100625/d94ea931/attachment.html>