Hi guys! In my installation I have a public FS being connected by lots of clients and being used to connect them with each other. Some of them might be backed by various NATs. And though they all use STUN to discover their public IP address, sometimes it's just not enough to provide two-way sound. These clients all have ICE and TURN support, but it is useless, since FS doesn't support ICE (at least that's what I know), and there are no ICE-related headers in FS's originating SDP for b-leg. Currently, all calls are being connected by means of bridge app with proxy_media mode enabled. For now, I can only think of couple of ways to enable ICE negotiation between a and b: 1. Redirect a directly to b. But to accomplish this I've to know b's IP, that it was registered with, which is being stored in sip_registrations db. Can I obtain it with db app in dialplan and substitute as a parameter to deflect app? 2. Force FS to copy remote SDP headers, or at least a part of them, to it's local SDP. 3. I feel I might be missing something important... Please help me to find a best solution to enable ICE negotiation. Best regards, RobertT.
Should someone want to know the answers I found, here they are. I had two ideas about how to forward SDP ICE-related headers from FS to leg-B. *1. Redirect a directly to b. But to accomplish this I've to know b's IP, that it was registered with, which is being stored in sip_registrations db. Can I obtain it with db app in dialplan and substitute as a parameter to deflect app? *This is* *rather simple - just call "defend" app from dialplan with ${destination_number} parameter. Actually, FS answers with a bit awkward address in Refer-to header, containing <profile_name><destination>@<domain>, so one would have to parse recieved address manually, to use a correct sip uri. Did I make something wrong?.. * * *2. Force FS to copy remote SDP headers, or at least a part of them, to it's local SDP.* This is even more simple - just set inbound_bypass_media to true in sofia profile settings, and FS will leave all of the SDP headers intact. But, you have to remember, that media traffic for this profile will bypass FS, as parameter's name implies. Therefore FS will not be able to manipulate media data in anyway. Best regards, RobertT.
participants (1)
-
RobertT