Michael,<br><br>Is your implementation an IMS like implementation, with lots of TelCO/CableCO rigid requirements in order to interface with proprietary Softswitch and MediaGTY?<br><br>Here is what is know about SIPt and SIPi<br>
SIP-T is originally from IETF.<br>SIP-I (SIP ISUP mapping) is from ITU (Q.1912.5)which specifies recommendations for interworking of ISUP/BICC and SIP-T<br><br>SIP-T (SIP for Telephones) is a mechanism that uses SIP to facilitate the interconnection of the PSTN with<br>
packet networks. It is characterized by the encapsulation of legacy signalling (typically, though not<br>exclusively, ISUP) in the SIP body for feature transparency, translation of ISUP information into the SIP<br>header for routability, and use of the INFO method for mid-call signalling.<br>
Inter-MGC signalling is used to establish, modify, and terminate sessions between peers. The MGC<br>control profiles include several inter-MGC signalling protocols, and this IA addresses the SIP-T option<br>(See figure 2). Figure 2 shows only MGCs controlling a trunking gateway, but this IA also covers a MGC<br>
that controls an access or residential gateway, and operates in a mode where ISUP is generated, as for a<br>normal PSTN trunk call, and then encapsulated in SIP (i.e. SIP-T)<br><br>I am sure that if there was a bounty, some of the bright people in the FS community would take on the project.<br>
<br>Regards,<br>-E<br>