Ok this is a stop gap for some people running 3.x polycom firmware. We smack down...

I'm currently working with Polycom to resolve this issue. (SR #: 1-31824511)

git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@12340 d0543943-73ff-0310-b7d9-9358b9ac24b2

diff --git a/conf/dialplan/default.xml b/conf/dialplan/default.xml
index c93fea429f8554c46d05d31cc5f997a753e0054a..c31d644f63d3cf47ef08be522b00062c5e0fcb47 100644 (file)
--- a/conf/dialplan/default.xml
+++ b/conf/dialplan/default.xml
@@ -86,6 +86,16 @@
        <!-- Offer SRTP on outbound legs if we have it on inbound. -->
        <!-- <action application="export" data="sip_secure_media=true"/> -->
       </condition>
+
+      <!-- 
+          This will cause us to not enable SRTP on known broken 3.x.x Polycom Firmware.
+      -->
+      <condition field="${sip_secure_media}" expression="^true$" break="never"/>
+      <condition field="${sip_user_agent}" expression="^PolycomSound(Point|Station)IP-S(S|P)IP_\d{3,4}-UA\/((3).(\d).(\d).(\d{4}))$" break="never">
+       <action application="set" data="sip_secure_media=false"/>
+       <action application="log" data="crit Your phone is a Polycom running 3.x firmware that is known broken for SRTP."/>
+      </condition>
+
       <condition>
        <action application="hash" data="insert/${domain_name}-spymap/${caller_id_number}/${uuid}"/>
        <action application="hash" data="insert/${domain_name}-last_dial/${caller_id_number}/${destination_number}"/>