In current version of code, the "Via" in register request looks like:
Via: SIP/2.0/UDP 192.168.1.100:50001;branch=z9hG4bK.iJM9FQ5m5ZRW0ZJZTAvNGlTyN9JPA6Nl
In a common VoIP software, the "Via" in register request looks like:
Via: SIP/2.0/UDP 192.168.1.100:50001;rport;branch=z9hG4bK.iJM9FQ5m5ZRW0ZJZTAvNGlTyN9JPA6Nl
The difference is that an extra "rport" is added. (See RFC3581)
This allows the client to be in the NAT without causing message loss. This version of code works fine on my FreeSwitch server.
However, the code does not carefully tune the writing style and configuration features, perhaps adding additional configurable items would be better.
In current version of code, the "Via" in register request looks like:
Via: SIP/2.0/UDP 192.168.1.100:50001;branch=z9hG4bK.iJM9FQ5m5ZRW0ZJZTAvNGlTyN9JPA6NlIn a common VoIP software, the "Via" in register request looks like:Via: SIP/2.0/UDP 192.168.1.100:50001;rport;branch=z9hG4bK.iJM9FQ5m5ZRW0ZJZTAvNGlTyN9JPA6NlThe difference is that an extra "rport" is added. (See RFC3581)
This allows the client to be in the NAT without causing message loss. This version of code works fine on my FreeSwitch server.
However, the code does not carefully tune the writing style and configuration features, perhaps adding additional configurable items would be better.