<div dir="ltr">Unfortunately this is par for the course when dealing with 3rd party interconnects.<div><br></div><div>Some will adhere to the RFC beautifully, and others (often large multi-national telcos) will have their own interpretation of the RFC that you find they require.</div>
<div><br></div><div>The best advice I can give here is to have a testing phase (even if only a few calls) - so you can compare your respective understandings of costs and CDRs before going fully live with a carrier.</div>
<div><br></div><div><br></div><div>Pete</div><div><a href="http://www.voxbeam.com">http://www.voxbeam.com</a></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 10 December 2013 20:47, Nick Cameo <span dir="ltr"><<a href="mailto:symack@gmail.com" target="_blank">symack@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Just did a text using uac_replace_to, and appended the prefix to the<br>
TO Header, and now the calls are going through. What kind of chemistry<br>
project is this? How many RFC standards are we breaking? Is there<br>
anyway to do this for just this service provider's (gateway + prefix)<br>
without hacking my beautifully scripted opensips file.<br>
<br>
Feature request? DB flag for adding prefix to the TO Header?<br>
<br>
Kind Regards,<br>
<div class="HOEnZb"><div class="h5"><br>
Nick.<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>