Re: [SR-Users] Attended transfer in load-balanced multi-server setup

2011-04-16 Thread Iñaki Baz Castillo
2011/4/13 Pan B. Christensen p...@ibidium.no: Scenarios: A call comes in from Nortel/PSTN (user A) through Nortel1 to a SIP device (user B). User B pushes the transfer button (puts current call on hold and makes a new call) and dials a Nortel / PSTN number to user C. This call goes out

Re: [SR-Users] loose_route security

2011-04-16 Thread Iñaki Baz Castillo
2011/4/11 Daniel-Constantin Mierla mico...@gmail.com: first, skipping authentication for within dialog requests in default configuration file comes mainly from the early years when not many sip endpoints supported that. But can be done, of course and perhaps it should be enabled (or at least

Re: [SR-Users] Fwd: [RAI] SIPit 28 summary

2011-04-16 Thread Iñaki Baz Castillo
2011/4/15 Klaus Darilion klaus.mailingli...@pernau.at: Support for various items in the proxy/registrars:  50% path  50% outbound  33% sip/stun multiplexing  20% diversion  18% gruu  17% history-info  17% service-route Correct me if I'm wrong: Items implemented in Kamailio/sip-router: -

Re: [SR-Users] loose_route security

2011-04-16 Thread Juha Heinanen
Iñaki Baz Castillo writes: - Later alice sends a REFER or a re-INVITE. Note that the request would contain From: sip:2...@domain.org (even if the AoR of alice us sip:al...@domain.org. This is because From/To URI are usually unchanged whithin a dialog. inaki, refer would contain header

Re: [SR-Users] Fwd: [RAI] SIPit 28 summary

2011-04-16 Thread Olle E. Johansson
16 apr 2011 kl. 15.59 skrev Iñaki Baz Castillo: 2011/4/15 Klaus Darilion klaus.mailingli...@pernau.at: Support for various items in the proxy/registrars: 50% path 50% outbound 33% sip/stun multiplexing 20% diversion 18% gruu 17% history-info 17% service-route Correct me if I'm

Re: [SR-Users] Fwd: [RAI] SIPit 28 summary

2011-04-16 Thread Iñaki Baz Castillo
2011/4/16 Olle E. Johansson o...@edvina.net: Yes, Kamailio is behind and after focusing so much on the merger of the code I think it would be good to plan some new features for a coming release. The issue is what of all the new SIP features we need. History-info seems useful for Asterisk,

Re: [SR-Users] Fwd: [RAI] SIPit 28 summary

2011-04-16 Thread Iñaki Baz Castillo
2011/4/16 Iñaki Baz Castillo i...@aliax.net: Diversion is deprecated. No, it became RFC 5806 past year:  http://tools.ietf.org/html/rfc5806 But it has Category: Historic. -- Iñaki Baz Castillo i...@aliax.net ___ SIP Express Router (SER) and

Re: [SR-Users] Fwd: [RAI] SIPit 28 summary

2011-04-16 Thread Juha Heinanen
Iñaki Baz Castillo writes: No, it became RFC 5806 past year:  http://tools.ietf.org/html/rfc5806 But it has Category: Historic. they could not make it anything else because official solution is history-info that almost no one has implemented. -- juha

Re: [SR-Users] Fwd: [RAI] SIPit 28 summary

2011-04-16 Thread Daniel-Constantin Mierla
On 4/16/11 7:30 PM, Olle E. Johansson wrote: 16 apr 2011 kl. 15.59 skrev Iñaki Baz Castillo: 2011/4/15 Klaus Darilionklaus.mailingli...@pernau.at: Support for various items in the proxy/registrars: 50% path 50% outbound 33% sip/stun multiplexing 20% diversion 18% gruu 17%

Re: [SR-Users] Fwd: [RAI] SIPit 28 summary

2011-04-16 Thread Alex Balashov
I wholeheartedly agree with Daniel's assessment. 3.x and 3.1.x have seen incredibly important feature gains that have been revolutionary for our work. It is true that a lot of the feature growth has been in internal/runtime capabilities of Kamailio as a pseudoprogrammatic execution

Re: [SR-Users] Fwd: [RAI] SIPit 28 summary

2011-04-16 Thread Iñaki Baz Castillo
2011/4/16 Daniel-Constantin Mierla mico...@gmail.com: As for next release, there are lot of features added (http://sip-router.org/wiki/features/new-in-devel), more to come, but I think most of developers here got tired hunting the ghosts of IETF specs that never were any useful nor had a touch