Net::SIP::StatelessProxy - Simple implementation of a stateless proxy
This package implements a simple stateless SIP proxy. Basic idea is that the proxy has either a single or two legs and that the packets are exchanged between those legs, e.g. packets incoming on one leg will be forwarded through the other leg.
Because this is a stateless proxy no retransmits will be done by the proxy.
The proxy can be used in connection with Net::SIP::Registrar to work as a registrar too. In this case incoming packets from the dispatcher need to be forwarded to the registrar and only if the registrar does not handle the packet (method receive in Net::SIP::Registrar returns
() ) it should be handled by the proxy.
While forwarding the proxy will be insert itself into the packet, e.g. it will add Via and Record-Route header while forwarding requests.
Additionally it will rewrite the Contact header while forwarding packets, e.g. if the Contact header points to some client it will rewrite it, so that it points to the proxy and if it already points to the proxy it will rewrite it back so that it again points to the client.
- new ( %ARGS )
Creates a new stateless proxy. With %ARGS the behavior can be influenced:
The Net::SIP::Dispatcher object managing the proxy.
This is either a hash reference which can be used in the constructor of Net::SIP::Registrar or a registrar object itself (only criteria is that it needs to have a method receive with the behavior described for Net::SIP::Registrar).
If given all incoming REGISTER requests will be forwarded to the registrar (by calling it's method receive) and only if the registrar does not handle the packet (method returns
()) it will be handled by the proxy.
Special marker string which is used in rewriting Contact headers, if a Contact header points to the proxy itself and contains this string it will rewritten, so that it points to the original Contact header.
- receive ( PACKET, LEG, FROM )
PACKET is the incoming packet, LEG is the Net::SIP::Leg where the packet arrived and FROM is the
"ip:port"of the sender.
Talled from the dispatcher on incoming packets. The packet will be rewritten (
Record-Routeheaders added, Contact modified) and then the packet will be forwarded through the other leg (or through the same leg if there is only one leg).
For requests it can determine the target of the forwarded packet by looking at the route or if no route it looks at the URI. For responses it looks at the next Via header.