Dave, you're wrong to use FS as transcoder only as Kristian, I and other said real SIP proxy servers as Opensips, Kamalio are built to use it as you need ----- Original Message ----- From: "Dave Horton" <dave@dchorton.com> To: "Kristian Kielhofner" <kris@kriskinc.com> Cc: "FreeSWITCH Users Help" <freeswitch-users@lists.freeswitch.org> Sent: Thursday, April 14, 2011 2:18 PM Subject: Re: [Freeswitch-users] Relay Proxy-Authentication requests to thecaller
In my case, I am trying to use it as a simple transcoding server. And the rich media support of codecs, and the ease of managing multiple sip profiles and setting up a back-to-back user agent scenario lend themselves quite well to the task IMO. I don't think the other solutions handle media or transcoding at all (correct me if I'm wrong) so trying to build the solution using those platforms would actually leave quite a lot of heavy lifting to do.
I have built a lot of SIP apps over the past 10 years, on a lot of different networks, and I have found that it is critical to be able to tweak SIP headers to make these interop. I wish it weren't the case, but it has been and still remains so. FS seems to only allow true custom headers (e.g., X- headers) to be manipulated at this level, and I find it to be a shortcoming.
On Apr 14, 2011, at 2:11 PM, Kristian Kielhofner wrote:
These requests have baffled me...
Are you trying to use FreeSWITCH as an outbound proxy (or something)?
This type of low-level SIP mangling is usually more well suited to OpenSIPS, Kamailio, etc. Even then you'd have some work cut out for you...
On Thu, Apr 14, 2011 at 1:36 PM, Dave Horton <dave@dchorton.com> wrote:
I had the same question/issue myself, and would be interested to know if there is a way. For myself, I had to do two things to get this to work: 1. Disable authentication so that FS would not itself generate a challenge. In vars.xml I added this: <X-PRE-PROCESS cmd="set" data="internal_auth_calls=false"/> and in my internal.xml (because calls were coming in on my internal profile): <param name="accept-blind-auth" value="true"/> 2. Then I had to hack mod_sofia to create a new channel variable containing the received Proxy-Authorization on the inbound leg, and also let me set it on the outbound leg. After that it worked, but I would still prefer a solution that didn't require changing mod_sofia, if one exists...
Hi All!
I would like to know if there is a param we could set in sofia profile to let freeswitch relay Proxy-Authentication requests to the caller instead of absorbing it.
Regards,
Hamid
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Kristian Kielhofner
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org