Yes you remove the force-contact variable from the <domain> tag and only set it in the individual <user> tag.
That is how you can pick and choose which ones do the options.
You can also configure a force-expires on each user so the register will reply with a very short expiry time to
trigger the client to re-register at any frequency you want. You can enable this without enabling the force-contact
The force-contact option automatically sets the expire time to 20 seconds but you can make it even lower if you wish.
Jonathan Palley napsal(a):
> I get the feeling that some of these edge optimizations are,I think so. And this why I think about to do it myself :-)
> rightfully, not the top priority for the core team.
If someone other see it useful...
If I have success in doing such changes to sources, I'm very glad if you
> If you make
> these changes I'm happy to help test as all of our users are behind a
> NAT.
help me with testing. Thanks Jonathan!
And I have nearly no experiences with FreeSWITCH :-)
> Right now we don't have enough users to justify doing this
> optimization ourselves though.
>
Yes, I agree. But few of them (for example Nokia mobile phones) can't do
> As for keeping the UDP connection open I recommend having the client
> send "blank" UDP packets and setting the interval there.
>
that. And this why should I send keep-alive packets (dummy packets or
valid OPTIONS), but only to few of NATed UACs. Thus I have to have an
option to distinguish between UACs which need to be nat-pinged and which
not :-)
Best regards,
kokoska.rokoska
_______________________________________________
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