<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>RE: Cisco CME and NET VX900 SIP trunk</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=" />
  <subtitle>RE: Cisco CME and NET VX900 SIP trunk</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=</id>
  <updated>2013-06-20T05:45:42Z</updated>
  <dc:date>2013-06-20T05:45:42Z</dc:date>
  <entry>
    <title>RE: Cisco CME and NET VX900 SIP trunk</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=2348337" />
    <author>
      <name>Joe Quigley</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=2348337</id>
    <updated>2010-07-12T02:58:30Z</updated>
    <published>2010-07-12T02:58:30Z</published>
    <summary type="html">I'm sure the original poster has long figured this out, but recently I've run into a similar issue and found the cause to be the pattern on the VX900 not being syntactically correct for the SIP messaging.
 
For example, I had {$$$}{$$$$} for incoming matching, but in order to preserve the id of "e.164num@ipaddress" the pattern should be {$$$}{$$$$}@+</summary>
    <dc:creator>Joe Quigley</dc:creator>
    <dc:date>2010-07-12T02:58:30Z</dc:date>
  </entry>
</feed>

