Hi David,<br><br>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. <br>
<br>This was for their SIP 2WAY service, our outbound only isn't up in production yet.<br><br>Regards,<br>Jared Geiger<br><br><div class="gmail_quote">On Fri, Jun 25, 2010 at 10:07 AM, David Hiers <span dir="ltr"><<a href="mailto:hiersd@gmail.com">hiersd@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi,<br>
Do you peer with verizon?<br>
<br>
Do you get peppered with their custom "Warning: 399" headers inside<br>
their 200 responses? If so, have you ever gotten a decent explanation<br>
of these headers?<br>
<br>
<br>
Thanks,<br>
<br>
David<br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div><br>