Overriding it negates the reason for it in the first place, to catch call loops.  If it is that low coming in, its due to a provider send unreasonably low max forwards.  Looking at the sip traffic coming in should show you this.  You should request the party sending very low max forwards to comply with standards.

Mike

On Jan 9, 2014, at 2:59 AM, Grant Bagdasarian <GB@cm.nl> wrote:

Hello,
 
I have yet to investigate why the outgoing leg when bridging an incoming leg has a very low Max-Forwards value.
It always starts with Max-Forwards: 7 which causes problems. I did force the value to be 70 by setting {max_forwards=70} in the bridge application, which works great, but this means I have to do this every time I do a bridge somewhere in the dialplan.
 
Is there a way to set this value globally so each outgoing leg takes this value for its Max-Forwards header? Perhaps in the sip_profiles, var.xml, or somewhere else?
 
Thanks,
 
Grant
_________________________________________________________________________
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