The Milkfish SIP Router Features
NAT fixing for registrations addressed to a SIP Provider in the internet (Local SIP NAT traversal)
The IP address in the contact header field of outgoing registration messages is replaced by the current WAN address of therouter. By that, requests to your account registered at a SIP provider are routed correctly to your router. STUN or something similar is no more required.
“Drive-by” registration of outgoing registrations
Registrations addressed to a SIP provider in the internet are also stored by the local registrar on the router. By that, the router can resolve incoming requests from the LAN or WAN side to the corresponding user agent client.
RTP proxy between the WAN and the LAN world (Local/Near-end NAT fixing for the media stream)
The IP addresses for the media stream are replaced by the WAN and LAN addresses of your router, respectively. On the router an RTP proxy handles the media communication between the two worlds. This leads to an easy firewall configuration and fixes local adresses in outgoing session description messages. STUN or something similar is no more required.
Creation of local subscribers
It is possible to create accounts with passwords for local subscribers on the router. This can be used for phones which are only used internally and which are not registered at a SIP provider in the internet. Together with the Homesip service and the From Header substitution these accounts are able to place calls to and receive calls from the internet. So for pure internet calls no more provider is needed. The account settings can be stored persistently in the flash memory of the router.
Internal Calls within the LAN
By creating local accounts on the router and with the help of “Drive-by” registrations a database with all the SIP clientsin the LAN is available on the router. With that, internal communication is possible. By creating aliases also quick dialing becomes possible.
Aliases for quick dialing
It is possible to create aliases for quick dialling of local accounts and friends. With that, it possible to call Nick by e.g. dialing just “nick” instead of Nick’s formal URI, being “343556453545@sipgateway.com” . The aliases can be stored persistently in the flash memory of the router.
DynSip Service for dynamic SIP address resolution
DnySip is a DynDNS-like service for SIP. With that, all your clients in your local SIP database on your router are reachable via client@your_user_name.dynsip.org. This very helpful for internet connections with dynamic addresses as it enables Point-to-Point calling between clients using such internet connections with or even without a VoIP provider.
SIP Messaging
It is possible to send SIP/SIMPLE messages via the router - through both, Shell or Web Interface.
From Header substitution
If From Header substitution is enabled, local addresses in the From Header of outgoing messages can be replaced either by the WAN IP address or a given domain (e.g. your Homesip address; your_user_name.homesip.net)
Performance Auditing
With the audit functionality it is possible to track the router’s availability (uptime) and utilization.
SIP Tracing
It is possible to record SIP messages passing the router. This is helpful for debugging.
Further Details can be found in the Documentation here.
If you already like our features or could imagine to have some more, let us know and consider to help us advance with this project.
