<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Change UPDATE's FROM field to match caller id (RPID) with SIP normalization script in Call Control</title>
    <link>https://community.cisco.com/t5/call-control/change-update-s-from-field-to-match-caller-id-rpid-with-sip/m-p/3480366#M834</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;We have CUCM 9.1 connected internally to Mitel (MCD 6.0) via SIP.&amp;nbsp; Transferred calls between the two systems don't display the correct caller ID on Mitel sets.&amp;nbsp; This is because Mitel uses the FROM field in UPDATE messages for caller ID on sets display.&amp;nbsp; CUCM never changes the FROM field.&amp;nbsp; It is always the originating name and number.&amp;nbsp; Wondering if a SIP Normalization script can be written to change the FROM field in UPDATE messages to match the RPID and or PAI caller ID info.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 May 2014 19:19:10 GMT</pubDate>
    <dc:creator>rick_declerk</dc:creator>
    <dc:date>2014-05-01T19:19:10Z</dc:date>
    <item>
      <title>Change UPDATE's FROM field to match caller id (RPID) with SIP normalization script</title>
      <link>https://community.cisco.com/t5/call-control/change-update-s-from-field-to-match-caller-id-rpid-with-sip/m-p/3480366#M834</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;We have CUCM 9.1 connected internally to Mitel (MCD 6.0) via SIP.&amp;nbsp; Transferred calls between the two systems don't display the correct caller ID on Mitel sets.&amp;nbsp; This is because Mitel uses the FROM field in UPDATE messages for caller ID on sets display.&amp;nbsp; CUCM never changes the FROM field.&amp;nbsp; It is always the originating name and number.&amp;nbsp; Wondering if a SIP Normalization script can be written to change the FROM field in UPDATE messages to match the RPID and or PAI caller ID info.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 May 2014 19:19:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/change-update-s-from-field-to-match-caller-id-rpid-with-sip/m-p/3480366#M834</guid>
      <dc:creator>rick_declerk</dc:creator>
      <dc:date>2014-05-01T19:19:10Z</dc:date>
    </item>
    <item>
      <title>Re: Change UPDATE's FROM field to match caller id (RPID) with SIP normalization script</title>
      <link>https://community.cisco.com/t5/call-control/change-update-s-from-field-to-match-caller-id-rpid-with-sip/m-p/3480367#M835</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rick,&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;P class="pB1_Body1"&gt;It is possible to trigger transparent pass through&amp;nbsp; of information on from one SIP dialog (representing 1 of the call legs) &lt;BR /&gt;to the other.&amp;nbsp;&amp;nbsp; Currently, transparency is limited to INVITE dialogs between 2 SIP Trunks. If SIP Line is involved, transparency is not supported. SUBSCRIBE dialogs, PUBLISH, out-of-dialog REFER, out-of-dialog unsolicited NOTIFY are not supported, and MESSAGE are not supported. &lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;P class="pB1_Body1"&gt;Please refer &lt;A href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/sip_tn/8_5_1/sip_t_n/10-sip_transparency.html#wp1070471"&gt;Supported Features &lt;/A&gt; for more details.&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;P class="pB1_Body1"&gt;Thanks and Regards,&lt;/P&gt;&lt;P class="pB1_Body1"&gt;Geevarghese&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 May 2014 10:20:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/change-update-s-from-field-to-match-caller-id-rpid-with-sip/m-p/3480367#M835</guid>
      <dc:creator>Geevarghese Cheria</dc:creator>
      <dc:date>2014-05-08T10:20:49Z</dc:date>
    </item>
  </channel>
</rss>

