To handle NAT I can think of 2 solutions:
1. add STUN support
2. Send an OPTIONS request to the proxy before sending the INVITE. Then, the report parameter and received parameter in the reply to the OPTIONS request could be used to find out the public IP:port. Further, keep alive must be added too.
As most software (ser/openser/Asterisk) support NAT traversal I will not add this feature - but you may add it yourself.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1318360
Originator: NO
To handle NAT I can think of 2 solutions:
1. add STUN support
2. Send an OPTIONS request to the proxy before sending the INVITE. Then, the report parameter and received parameter in the reply to the OPTIONS request could be used to find out the public IP:port. Further, keep alive must be added too.
As most software (ser/openser/Asterisk) support NAT traversal I will not add this feature - but you may add it yourself.