<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Reverse Number Lookup and Dealing with Legacy PBX</title><link>http://blogs.technet.com/msukucc/archive/2009/05/21/reverse-number-lookup-and-dealing-with-legacy-pbx.aspx</link><description>Working with customers I have come across a number of scenarios where the caller ID presented from the PBX is not in E164/DID (Direct Inward Dial) format. Some gateways allow for extensive manipulation of the caller ID, some less so. The good news is</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Microsoft UK UC Blog : Reverse Number Lookup and Dealing with &amp;#8230; | Free Reverse Cell Phone Lookup</title><link>http://blogs.technet.com/msukucc/archive/2009/05/21/reverse-number-lookup-and-dealing-with-legacy-pbx.aspx#3244255</link><pubDate>Thu, 21 May 2009 22:51:10 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3244255</guid><dc:creator>Microsoft UK UC Blog : Reverse Number Lookup and Dealing with &amp;#8230; | Free Reverse Cell Phone Lookup</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://free-reverse-cell-phone-lookup.info/?p=1205"&gt;http://free-reverse-cell-phone-lookup.info/?p=1205&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Reverse Number Lookup and Dealing with Legacy PBX</title><link>http://blogs.technet.com/msukucc/archive/2009/05/21/reverse-number-lookup-and-dealing-with-legacy-pbx.aspx#3250848</link><pubDate>Fri, 05 Jun 2009 18:57:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3250848</guid><dc:creator>Office Communications Server Team Blog</dc:creator><description>&lt;p&gt;One of our consultants in the UK, Paul Brombley did a write up on a deployment and how they dealt with...&lt;/p&gt;
</description></item><item><title>re: Reverse Number Lookup and Dealing with Legacy PBX</title><link>http://blogs.technet.com/msukucc/archive/2009/05/21/reverse-number-lookup-and-dealing-with-legacy-pbx.aspx#3255054</link><pubDate>Mon, 15 Jun 2009 20:54:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3255054</guid><dc:creator>Carlo</dc:creator><description>&lt;p&gt;Nice post. &amp;nbsp;When you create your location profile for mediation server specifically, I am assuming you must name it the netbios name of the mediation server itself for it to work correctly? &amp;nbsp;In your example, &amp;quot;ReadingMediationServer&amp;quot; &amp;nbsp;Is this correct? &amp;nbsp;If so then these rules will be applied for all inbound calls from the gateway to the Mediation Server. &amp;nbsp;For outbound calls, I'm assuming that the users' set Location Profile NormRules will only be applied and not the Mediation Server specific rules?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
</description></item><item><title>re: Reverse Number Lookup and Dealing with Legacy PBX</title><link>http://blogs.technet.com/msukucc/archive/2009/05/21/reverse-number-lookup-and-dealing-with-legacy-pbx.aspx#3259914</link><pubDate>Tue, 30 Jun 2009 13:51:07 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3259914</guid><dc:creator>Paul Brombley</dc:creator><description>&lt;p&gt;The location profile for the Mediation server can be called anything. There are no specific rules. The only time the name of the Location Profile matters is when tying up with Exchange UM.&lt;/p&gt;
</description></item><item><title>re: Reverse Number Lookup and Dealing with Legacy PBX</title><link>http://blogs.technet.com/msukucc/archive/2009/05/21/reverse-number-lookup-and-dealing-with-legacy-pbx.aspx#3264898</link><pubDate>Wed, 15 Jul 2009 18:33:46 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3264898</guid><dc:creator>Jason Shave</dc:creator><description>&lt;p&gt;The only problem with this scenario as I understand it is that missed call notifications and voice mail notifications only contain the original phone number from the SIP INVITE.&lt;/p&gt;
&lt;p&gt;In other words, you can't perform click to dial on these &amp;quot;raw&amp;quot; numbers unless you have normalization rules to handle them.&lt;/p&gt;
&lt;p&gt;For example, if a call comes in as a SIP INVITE from &amp;quot;7805551212&amp;quot; here in North America, we can use an inbound normalization rule at the Mediation server to change it to &amp;quot;+17805551212&amp;quot; however the missed call notification will show &amp;quot;7805551212&amp;quot; only.&lt;/p&gt;
</description></item><item><title>re: Reverse Number Lookup and Dealing with Legacy PBX</title><link>http://blogs.technet.com/msukucc/archive/2009/05/21/reverse-number-lookup-and-dealing-with-legacy-pbx.aspx#3278529</link><pubDate>Tue, 01 Sep 2009 20:19:18 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3278529</guid><dc:creator>Reverse Lookup Guru</dc:creator><description>&lt;p&gt;That was insanely informative, and I'm going to read through it again just to make sure that I got everything. Thanks!&lt;/p&gt;
</description></item></channel></rss>