<?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 Re: custom field in sip message in IP Telephony and Phones</title>
    <link>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683878#M369302</link>
    <description>&lt;P&gt;Jun 22 13:23:24: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:&lt;BR /&gt; Received:&lt;BR /&gt; INVITE &lt;A href="mailto:sip%3A9014@media1.as50464.net" target="_blank"&gt;sip:9014@media1.as50464.net&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253A9014@media1.as50464.net" target="_blank"&gt;sip%3A9014@media1.as50464.net&lt;/A&gt;&amp;gt; SIP/2.0&lt;BR /&gt; Record-Route: &amp;lt;&lt;A href="mailto:sip%3Amo@172.26.0.16" target="_blank"&gt;sip:mo@172.26.0.16&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253Amo@172.26.0.16" target="_blank"&gt;sip%3Amo@172.26.0.16&lt;/A&gt;&amp;gt;;r2=on;lr=on;ftag=3RJdXhmP;vst=AAAAAE1VUlwfHhAUGQ5DWiEeUFRdVwUADxZBMDQ2NC5uZXQ-;nat=yes;rtp=SAVPF;did=337.89b2&amp;gt;&lt;BR /&gt; Record-Route: &amp;lt;&lt;A href="http://sip:mo@172.26.0.16:443" target="_blank"&gt;sip:mo@172.26.0.16:443&lt;/A&gt;&amp;lt;&lt;A href="http://sip:mo@172.26.0.16:443/" target="_blank"&gt;http://sip:mo@172.26.0.16:443/&lt;/A&gt;&amp;gt;;transport=ws;r2=on;lr=on;ftag=3RJdXhmP;vst=AAAAAE1VUlwfHhAUGQ5DWiEeUFRdVwUADxZBMDQ2NC5uZXQ-;nat=yes;rtp=SAVPF;did=337.89b2&amp;gt;&lt;BR /&gt; Via: SIP/2.0/UDP 172.26.0.16;branch=z9hG4bK1bbd.fd560798bff7a5ccedfbaa4d1e090140.0&lt;BR /&gt; Via: SIP/2.0/UDP 195.191.76.184:5060;received=195.191.76.184;branch=UjhUioE-F0xb-03oAoHu297bzERk7Q2VdOqdEFrZ5U9vt;rport=16157&lt;BR /&gt; Contact: &amp;lt;&lt;A href="mailto:sip%3Amkb_mobile2@195.191.76." target="_blank"&gt;sip:mkb_mobile2@195.191.76.&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253Amkb_mobile2@195.191.76" target="_blank"&gt;sip%3Amkb_mobile2@195.191.76&lt;/A&gt;.&amp;gt;184:16157;transport=udp;alias=195.191.76.184~16157~6&amp;gt;&lt;BR /&gt; From: &amp;lt;&lt;A href="mailto:sip%3Amkb_mobile2@media1.as50464.net" target="_blank"&gt;sip:mkb_mobile2@media1.as50464.net&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253Amkb_mobile2@media1.as50464.net" target="_blank"&gt;sip%3Amkb_mobile2@media1.as50464.net&lt;/A&gt;&amp;gt;&amp;gt;;tag=3RJdXhmP&lt;BR /&gt; To: &amp;lt;&lt;A href="mailto:sip%3A9014@media1.as50464.net" target="_blank"&gt;sip:9014@media1.as50464.net&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253A9014@media1.as50464.net" target="_blank"&gt;sip%3A9014@media1.as50464.net&lt;/A&gt;&amp;gt;&amp;gt;&lt;BR /&gt; CSeq: 20 INVITE&lt;BR /&gt; Call-ID: AwfUnFYIoy9p&lt;BR /&gt; Max-Forwards: 69&lt;BR /&gt; Supported: replaces, outbound&lt;BR /&gt; Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, UPDATE&lt;BR /&gt; Content-Type: application/sdp&lt;BR /&gt; X-Key: 4b2e96e85de7767202961fe05cd85f59d431ffa75e01956e0b3b6be009ACK &lt;A href="http://sip:9014@172.28.241.251:5060" target="_blank"&gt;sip:9014@172.28.241.251:5060&lt;/A&gt;&amp;lt;&lt;A href="http://sip:9014@172.28.241.251:5060/" target="_blank"&gt;http://sip:9014@172.28.241.251:5060/&lt;/A&gt;&amp;gt; SIP/2.0&lt;BR /&gt; Call-ID: AwfUnFYIoy9p&lt;BR /&gt; CSeq: 20 ACK&lt;BR /&gt; Via: SIP/2.0/UDP 172.26.0.16;branch=z9hG4bK1bbd.c94f3aa074b6547bb498d124d768d9fb.0&lt;BR /&gt; Via: SIP/2.0/UDP 195.191.76.184:16157;received=195.191.76.184;rport=16157;branch=Mv5DjxB-4K2Q-YbHrBhLu6jaLs224XbEK9d7PyBxK27xt&lt;BR /&gt; From: &amp;lt;&lt;A href="mailto:sip%3Amkb_mobile2@media1.as50464.net" target="_blank"&gt;sip:mkb_mobile2@media1.as50464.net&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253Amkb_mobile2@media1.as50464.net" target="_blank"&gt;sip%3Amkb_mobile2@media1.as50464.net&lt;/A&gt;&amp;gt;&amp;gt;;tag=3RJdXhmP&lt;BR /&gt; To: &amp;lt;&lt;A href="mailto:sip%3A9014@media1.as50464.net" target="_blank"&gt;sip:9014@media1.as50464.net&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253A9014@media1.as50464.net" target="_blank"&gt;sip%3A9014@media1.as50464.net&lt;/A&gt;&amp;gt;&amp;gt;;tag=A706411C-1DDF&lt;BR /&gt; X-Key: 82116890e9969341396e9e77072a14f14ed89549e0d76f5bd42ea1f3a136097a9b95da85e11837bf9085ed62c4c7cac4c7d6e7ff41eb8a991a0df1500b9da028&lt;BR /&gt; Max-Forwards: 69&lt;BR /&gt; User-Agent: PPP PP&amp;gt;P1P0P9P;&lt;BR /&gt; DeviceUID: 5F0D6C2D-CB73-43EA-80E2-35D4158372D0&lt;BR /&gt; &lt;FONT size="5"&gt;&lt;STRONG&gt;ClientCode: 886841&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;so i need to use sip-copy list?&lt;/P&gt;</description>
    <pubDate>Wed, 08 Aug 2018 07:21:00 GMT</pubDate>
    <dc:creator>Evgeny Andreev</dc:creator>
    <dc:date>2018-08-08T07:21:00Z</dc:date>
    <item>
      <title>custom field in sip message</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683020#M369247</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;
&lt;P&gt;sip app - SIP - cisco router voice bundle - SIP - genesys sip server&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;if i initiate call from sip app to genesys server with custom field in INVITE message (ClientCode: 123456), i couldn't see it on genesys server. On cisco router i see this field only in INVITE from sip app.&lt;/P&gt;
&lt;P&gt;Voice call works fine&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;sip app - SIP - genesys sip server&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;in thist topology custom field is recieved on genesys server&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;dial-peers on router&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;dial-peer voice 121 voip&lt;BR /&gt; description **** MOBILE APP ***&lt;BR /&gt; destination-pattern 7800&lt;BR /&gt; session protocol sipv2&lt;BR /&gt; dtmf-relay cisco-rtp h245-alphanumeric h245-signal rtp-nte&lt;BR /&gt; codec g711alaw&lt;BR /&gt; no vad&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;dial-peer voice 100 voip&lt;BR /&gt; description ***GENESYS SIP SERVER***&lt;BR /&gt; huntstop&lt;BR /&gt; preference 3&lt;BR /&gt; destination-pattern 9[0,9].&lt;BR /&gt; session protocol sipv2&lt;BR /&gt; session target ipv4:172.28.240.56&lt;BR /&gt; dtmf-relay rtp-nte&lt;BR /&gt; codec g711alaw&lt;BR /&gt; no vad&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ideas why cisco router cuts custom field??&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Sun, 17 Mar 2019 20:17:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683020#M369247</guid>
      <dc:creator>Evgeny Andreev</dc:creator>
      <dc:date>2019-03-17T20:17:54Z</dc:date>
    </item>
    <item>
      <title>Re: custom field in sip message</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683355#M369274</link>
      <description>Can you show the complete INVITE please ? You should be able to match the header against a sip profile and use a copy list to add it back when the INVITE is sent out. CUBE does a check and drops unsupported information so what you see if working as designed AFAIK.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Aug 2018 15:30:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683355#M369274</guid>
      <dc:creator>R0g22</dc:creator>
      <dc:date>2018-08-07T15:30:57Z</dc:date>
    </item>
    <item>
      <title>Re: custom field in sip message</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683381#M369280</link>
      <description>Just wondering, why do you have session protocol sipv2 on dial-peer 121, obviously trying to make this a SIP dial-peer, but then have H323 DTMF relay configured?</description>
      <pubDate>Tue, 07 Aug 2018 15:54:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683381#M369280</guid>
      <dc:creator>Anthony Holloway</dc:creator>
      <dc:date>2018-08-07T15:54:11Z</dc:date>
    </item>
    <item>
      <title>Re: custom field in sip message</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683878#M369302</link>
      <description>&lt;P&gt;Jun 22 13:23:24: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:&lt;BR /&gt; Received:&lt;BR /&gt; INVITE &lt;A href="mailto:sip%3A9014@media1.as50464.net" target="_blank"&gt;sip:9014@media1.as50464.net&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253A9014@media1.as50464.net" target="_blank"&gt;sip%3A9014@media1.as50464.net&lt;/A&gt;&amp;gt; SIP/2.0&lt;BR /&gt; Record-Route: &amp;lt;&lt;A href="mailto:sip%3Amo@172.26.0.16" target="_blank"&gt;sip:mo@172.26.0.16&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253Amo@172.26.0.16" target="_blank"&gt;sip%3Amo@172.26.0.16&lt;/A&gt;&amp;gt;;r2=on;lr=on;ftag=3RJdXhmP;vst=AAAAAE1VUlwfHhAUGQ5DWiEeUFRdVwUADxZBMDQ2NC5uZXQ-;nat=yes;rtp=SAVPF;did=337.89b2&amp;gt;&lt;BR /&gt; Record-Route: &amp;lt;&lt;A href="http://sip:mo@172.26.0.16:443" target="_blank"&gt;sip:mo@172.26.0.16:443&lt;/A&gt;&amp;lt;&lt;A href="http://sip:mo@172.26.0.16:443/" target="_blank"&gt;http://sip:mo@172.26.0.16:443/&lt;/A&gt;&amp;gt;;transport=ws;r2=on;lr=on;ftag=3RJdXhmP;vst=AAAAAE1VUlwfHhAUGQ5DWiEeUFRdVwUADxZBMDQ2NC5uZXQ-;nat=yes;rtp=SAVPF;did=337.89b2&amp;gt;&lt;BR /&gt; Via: SIP/2.0/UDP 172.26.0.16;branch=z9hG4bK1bbd.fd560798bff7a5ccedfbaa4d1e090140.0&lt;BR /&gt; Via: SIP/2.0/UDP 195.191.76.184:5060;received=195.191.76.184;branch=UjhUioE-F0xb-03oAoHu297bzERk7Q2VdOqdEFrZ5U9vt;rport=16157&lt;BR /&gt; Contact: &amp;lt;&lt;A href="mailto:sip%3Amkb_mobile2@195.191.76." target="_blank"&gt;sip:mkb_mobile2@195.191.76.&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253Amkb_mobile2@195.191.76" target="_blank"&gt;sip%3Amkb_mobile2@195.191.76&lt;/A&gt;.&amp;gt;184:16157;transport=udp;alias=195.191.76.184~16157~6&amp;gt;&lt;BR /&gt; From: &amp;lt;&lt;A href="mailto:sip%3Amkb_mobile2@media1.as50464.net" target="_blank"&gt;sip:mkb_mobile2@media1.as50464.net&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253Amkb_mobile2@media1.as50464.net" target="_blank"&gt;sip%3Amkb_mobile2@media1.as50464.net&lt;/A&gt;&amp;gt;&amp;gt;;tag=3RJdXhmP&lt;BR /&gt; To: &amp;lt;&lt;A href="mailto:sip%3A9014@media1.as50464.net" target="_blank"&gt;sip:9014@media1.as50464.net&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253A9014@media1.as50464.net" target="_blank"&gt;sip%3A9014@media1.as50464.net&lt;/A&gt;&amp;gt;&amp;gt;&lt;BR /&gt; CSeq: 20 INVITE&lt;BR /&gt; Call-ID: AwfUnFYIoy9p&lt;BR /&gt; Max-Forwards: 69&lt;BR /&gt; Supported: replaces, outbound&lt;BR /&gt; Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, UPDATE&lt;BR /&gt; Content-Type: application/sdp&lt;BR /&gt; X-Key: 4b2e96e85de7767202961fe05cd85f59d431ffa75e01956e0b3b6be009ACK &lt;A href="http://sip:9014@172.28.241.251:5060" target="_blank"&gt;sip:9014@172.28.241.251:5060&lt;/A&gt;&amp;lt;&lt;A href="http://sip:9014@172.28.241.251:5060/" target="_blank"&gt;http://sip:9014@172.28.241.251:5060/&lt;/A&gt;&amp;gt; SIP/2.0&lt;BR /&gt; Call-ID: AwfUnFYIoy9p&lt;BR /&gt; CSeq: 20 ACK&lt;BR /&gt; Via: SIP/2.0/UDP 172.26.0.16;branch=z9hG4bK1bbd.c94f3aa074b6547bb498d124d768d9fb.0&lt;BR /&gt; Via: SIP/2.0/UDP 195.191.76.184:16157;received=195.191.76.184;rport=16157;branch=Mv5DjxB-4K2Q-YbHrBhLu6jaLs224XbEK9d7PyBxK27xt&lt;BR /&gt; From: &amp;lt;&lt;A href="mailto:sip%3Amkb_mobile2@media1.as50464.net" target="_blank"&gt;sip:mkb_mobile2@media1.as50464.net&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253Amkb_mobile2@media1.as50464.net" target="_blank"&gt;sip%3Amkb_mobile2@media1.as50464.net&lt;/A&gt;&amp;gt;&amp;gt;;tag=3RJdXhmP&lt;BR /&gt; To: &amp;lt;&lt;A href="mailto:sip%3A9014@media1.as50464.net" target="_blank"&gt;sip:9014@media1.as50464.net&lt;/A&gt;&amp;lt;mailto:&lt;A href="mailto:sip%253A9014@media1.as50464.net" target="_blank"&gt;sip%3A9014@media1.as50464.net&lt;/A&gt;&amp;gt;&amp;gt;;tag=A706411C-1DDF&lt;BR /&gt; X-Key: 82116890e9969341396e9e77072a14f14ed89549e0d76f5bd42ea1f3a136097a9b95da85e11837bf9085ed62c4c7cac4c7d6e7ff41eb8a991a0df1500b9da028&lt;BR /&gt; Max-Forwards: 69&lt;BR /&gt; User-Agent: PPP PP&amp;gt;P1P0P9P;&lt;BR /&gt; DeviceUID: 5F0D6C2D-CB73-43EA-80E2-35D4158372D0&lt;BR /&gt; &lt;FONT size="5"&gt;&lt;STRONG&gt;ClientCode: 886841&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;so i need to use sip-copy list?&lt;/P&gt;</description>
      <pubDate>Wed, 08 Aug 2018 07:21:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683878#M369302</guid>
      <dc:creator>Evgeny Andreev</dc:creator>
      <dc:date>2018-08-08T07:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: custom field in sip message</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683919#M369306</link>
      <description>Configure voice class&lt;BR /&gt;&lt;BR /&gt;voice class sip-hdr-passthrulist 10&lt;BR /&gt; passthru-hdr ClientCode&lt;BR /&gt;&lt;BR /&gt;Under the inbound dial-peer put this command&lt;BR /&gt;&lt;BR /&gt;voice-class sip pass-thru headers 10&lt;BR /&gt;</description>
      <pubDate>Wed, 08 Aug 2018 08:34:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/custom-field-in-sip-message/m-p/3683919#M369306</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2018-08-08T08:34:33Z</dc:date>
    </item>
  </channel>
</rss>

