<html><head></head><body bgcolor="#FFFFFF"><div>Here's what I did with a couple of Vz SIP trunks in the US.</div><div><br></div><div><a href="Http://www.iptinfo.com/?p=302">Http://www.iptinfo.com/?p=302</a></div><div><br>
</div><div>This works if they're using PAI, but not diversion headers, which they were doing for our remote sites. In that case, we just used the external phone number mask applied to the phones for the caller-id.</div>
<div><br></div><div><br><div><br></div>Sent from an Apple iOS device with very tiny touchscreen input keys. Please excude my typtos.</div><div><br>On Dec 14, 2011, at 8:33 AM, Nick <<a href="mailto:csvoip@googlemail.com">csvoip@googlemail.com</a>> wrote:<br>
<br></div><div></div><div><p>Hi, I am just deploying Verizon SIP trunks now with CUCM 8.6.2a, as Verizon
needs to see the call coming from a number within the range assigned to the
trunks in the format 44XXXXXXXXXX, I would like to know the best way to achieve
this, in this situation I need most users to have CLI blocked to the called
party, however I have a number of users that need to be able to display a CLI
which could be different for a number of departments.</p>
<p>I am using device mobility and standard local route groups, is this best to
be configured from the CUCM or CUBE and how can this be done?</p>
<p>Cheers</p>
<p>Nick</p>
</div><div><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br><span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
</div></body></html>