In order to fix  XX-8438 (be able to pick up calls via aliases) it looks like 
we're going to need to tag each row in the alias IMDB table with a description 
of its type, so that the "sipx-userforward=false" URI parameter only suppresses 
the application of alias IMDB rows that are user-forwards, and not other rows.  
On the server side, that isn't very difficult, it's very easy to add a column 
to the IMDB.  On the configuration side, things are less clear, and I need some 
help.

It looks like all aliases rows are generated by creating an 'AliasMapping" 
object, which eventually is serialized out into the aliases XML.  It's easy 
enough to add a 'relation' parameter to the AliasMapping constructor, and I've 
invented the following values to tag AliasMapping's that are created for 
different purposes:

      <enumeration value='parkorbit'/>
      <annotation>
        <documentation>
          Park orbit routing.
        </documentation>
      </annotation>
      <enumeration value='callgroup'/>
      <annotation>
        <documentation>
          Call group routing.
        </documentation>
      </annotation>
      <enumeration value='abstractcallsequence'/>
      <annotation>
        <documentation>
          Generated by AbstractCallSequence.
        </documentation>
      </annotation>
      <enumeration value='moh'/>
      <annotation>
        <documentation>
          Music-on-hold provisioning.
        </documentation>
      </annotation>
      <enumeration value='conference'/>
      <annotation>
        <documentation>
          Conference provisioning.
        </documentation>
      </annotation>
      <enumeration value='acd'/>
      <annotation>
        <documentation>
          Automatic call distributor provisioning.
        </documentation>
      </annotation>

Each of these values is used as the third parameter of 'new AliasMapping()' in 
different sections of sipXconfig.  But I haven't yet figured out which 
constructors correspond to user forwarding, and for that matter, I don't know 
if the different sections of the code represent semantically consistent alias 
rows, or if some of the constructors are really service routines that are used 
for several different types of aliases.

Dale
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to