The refuse_t38 by itself is usually enough. Its possible that since the provider is using update instead of invites, that the update is being auto 200ok by the sofia stack and not giving fs a chance to refuse it.
Le 20/01/2014 21:45, *Ali Pey* wrote :
> Your carrier is sending the Update message and not the Invite, so you should
> ask them. FS, supports Update and that's why it's in the Allow message. I'm
> not sure if and how you can remove an allow parameter and I don't think that
> would make a difference.
>
> Ask your carrier to send a Re-Invite if you prefer that. Also, if you are
> behind a proxy servers such as OpenSIPS, you can do certain message
> manipulation to force certain behavior.
OK, thank you very much. I could easily delete "UPDATE, " in "allow:" field
sent by FreeSwitch using SIPProxy http://sourceforge.net/projects/sipproxy/
since I already used SIPProxy to modify messages sent by other clients like
Linphone, but I can't figure out what I have to set in FS to have all SIP
messages sent and received through SIPProxy.
In a client like Linphone, this setting is easy :
[proxy_3]
reg_proxy=<sip:192.168.1.6:5064> # SIPProxy IP:port
reg_route=<sip:192.168.1.6:5064> # SIPProxy IP:port
reg_identity=sip:0033972XXXXXX@sip.ovh.fr
But how to set reg_proxy and reg_route or equivalents in FreeSwitch ?
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
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