Transfers with sipx work by way of a REFER from the AA. You need to see if the CM can interpret those without interfering with your other configurations it uses.
voice service voip supplementary-service sip refer >>> Michael LeBlanc <[EMAIL PROTECTED]> 12/03/08 10:48 PM >>>Thanks for your >>> comments about running SipX on multiple ports. It's something we may need >>> to look at in the future, but for the PoC we're doing, I was able to get >>> the gateway to talk to SipX on 5060. I was asking about running SipX on multiple ports because of our gateway deployment. We're using a Cisco CallManager as our PSTN gateway, and it talks to a few different VoIP implementations. The practice is to talk to each implementation on a different port for management purposes. So it would make things easier if SipX could listen for SIP traffic on multiple ports, but it sounds like it would be easier to put something between the CallManager and SipX -- like OpenSIPS, Asterisk, etc -- and then re-route traffic. To wrap things up, I got voicemail from the PSTN working as well. It was just an issue of RTP traffic being blocked between the SipX host and the gateway. At this point, almost everything seems to work -- inbound calling, outbound calling. The only remaining issue is auto attendant transfers to internal extensions for calls originating from the PSTN (and running through the CallManager). I'll start a separate thread with a description of that issue, to see you have have any thoughts.... Thanks again, Mike You can run multiple instances on the same host; I've run 5 sipXecs'ssimultaneously. In principle it's simple, in practice it's messy. Theport numbers are controlled by a configuration file. (The exact methodis being changed, but the capability remains -- down in the bowels,sipXecs listening ports can be reconfigured.) The mess is that you haveto give each sipXecs instance a different tree of directories to storeits stuff in. You can do that by creating a chroot environment, or byrebuilding the code from source, providing "./configure--prefix=/root/of/sipXecs/execution/file/tree". Dale yes, with great care - this really isn't a "supported" thing to do, butwith manual configuration it can be made to work. > , or have the > same instance listen on multiple ports? no. What are you trying to do that you need this? </[EMAIL PROTECTED]>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
