Dear freeswitch support As you suggested, I have completed the ISUP<->SIP-T conversion work. While there are some problems to integrate my code to freeswitch. 1. I got one sangoma license and can bridge the freetmd to sofia now. But how can I intercept the ISUP mesasge(from the freetdm) and run to my application and then to Sofia module? Is there any external control like ESL to do the work? The diagram is like: SIP-T ISUP SofiaModule<-------------My Conversion---------------------->freetdm 2. I have been working with ESL "SEND" command to control the Sofia module, while it needs to divide the conversion SIP-T message. Is there anyway to put the one whole SIP-T message to Sofia module to handle? like one external SIP-T message to freeswitch? And vice versa, Is there good way to receive the whole SIP message from sofia module instead of using ESL to detect the SIP message info? Appreciated your comments. Windy ======== 2013-03-25 06:55:07 Original Message： ======== On Sun, Mar 24, 2013 at 9:43 AM, xiaofengcanyuexp@163.com <xiaofengcanyuexp@163.com> wrote: Dear freeswitch support I have been studying freeswitch for a few weeks. I will be planning to take the freeswitch as a signal gateway connecting PSTN(ISUP) and SIP. It needs convert the ISUP to SIP based on RFC3372/RFC3204/RFC3398 and vice versa. I notice in the mime_type.cfg supporting applicaiton/ISUP, but I don't find any code in sofia(SIP) module to decode/encode the application/ISUP. My question is: Does freeswitch support to do the signalling gateway connecting ISUP(freeTDM module also has the MTP layer support) and SIP(SIP-T/SIP-I)? If yes, could you let me know how it works? Hello Windy, There is no support in FreeSWITCH for SIP-I or SIP-T ISUP to SIP conversion is supported using Sangoma's SS7 module based on Trillium SS7 stack. Note this is licensed, not open source (this is true for all the MTP layers and ISUP, SCCP etc). Sangoma uses a raw/proprietary mechanism to pass-thru complete IAM messages in a SIP network, it is a crude embedding of the IAM message encoded using base64, within SIP header. We are aware this is crude and by far does not cover all cases, but it was done as quick and dirty way to avoid implementing the whole SIP-I/SIP-T spec and at the same time not miss any IAM information. In all honesty we've had not seen many requests for it so that has kept us from doing the implementation work. Cheers, Moises Silva Manager, Software Engineering msilva@sangoma.com Sangoma Technologies 100 Renfrew Drive, Suite 100, Markham, ON L3R 9R6 Canada t. +1 800 388 2475 (N. America) t. +1 905 474 1990 x128 f. +1 905 474 9223 Products | Solutions | Events | Contact | Wiki | Facebook | Twitter`| | YouTube = = = = = = = = = = = = = = = = = = = = = = Thanks Windy = = = = = = = = = = = = = = = = = = = = = = Thanks Windy