Am 01.07.2010 10:41, schrieb jerome.marchet@orange-ftgroup.com:
Probably because by encoding/decoding the proxy can still be stateless. If the proxy removes the headers, it has to add them later again, so it has to store the date locally.
By just encoding them, the whole data is still stored in the message.
regards Klaus
Hello,
On 7/1/10 10:41 AM, jerome.marchet@orange-ftgroup.com wrote:
the goals of topoh module were set to offer topology hiding functionality within a proxy, so right now it offers: - topology hiding even for transaction stateless mode (not even tm is required) - transparent mode for config file - inside the config, you will see the plain sip message, without any encodings - it survives restarts - restarting the sip server has no impact on ongoing calls - works over distributed farm of sip servers - encoding can be done by one instance, decoding works fine on another one that shares the same secret. This is good for HA, where invite was processed by active server and the bye happens to be processed by standby because HA switched. Another case is for load balancing, no need to care of routing messages within a call to same box - high performance for call processing - it can easily handle thousands of call setups per second, which is hard to achieve in b2bua
What you suggest is a b2bua and there are many options already available. For example SEMS (SIP Express Media Server) has an application for sip signaling only back to back user agent. Also, same can be achieved more or less with asterisk or freeswitch.
Cheers, Daniel
2010/7/1 Daniel-Constantin Mierla miconda@gmail.com:
Hi, I see two limitations in the topoh module:
1) It's works for every messages. Would make sense a flag or a function (i.e. "use_topoh()") so a parameter ;topoh is added to the Via and Record-Route headers and the proxy could decode the headers when such parameter is found?
2) If I'm not wrong, this feature breaks some SIP features as "call capture" or "attender transference", am I right?
Hello,
On 7/1/10 6:48 PM, Iñaki Baz Castillo wrote:
patches are welcome ;-)
Not sure what you mean with "call capture", but there is no limitation on call transfer.
Cheers, Daniel
2010/7/1 Daniel-Constantin Mierla miconda@gmail.com:
Sure :)
With "call capture" I mean subscription to dialog event so you get information about dialogs (call-id, from-tag, to-tag) and then you can send an INVITE with "Replaces" header containing such values (but the UAS wouldn't recognize those values as they have been modified by topoh module, am I wrong?
Humm, yes, I could be wrong: does topoh module modify the Call-Id header in case it contains @SOURCE_IP? (I know that Call-Id value is just a token, but lot of UA's append @SOURCE_IP to the Call-Id).
Regards.
-
Daniel-Constantin Mierla -
Iñaki Baz Castillo -
jerome.marchet＠orange-ftgroup.com -
Klaus Darilion