Thanks to all for your help:
1) Using dlg_bridge in Kamailio was my first option Daniel, but the
customer said that some of their IP-PBX may not support the REFER method
(old propiertary SIP implementations, you know...). Anyway I'll take into
account this option for the demo, because the comercial SBC that is going to
be used can deal with the REFER to perform the call transfer in a way
friendly with old SIP implementations. Missing the final status of the call
may not be a problem for our customer.
2) On the other hand we're planning to introduce SEMS in our networks as
media and application server. The click2dial service meets application
server functionality so we though it was a good chance to try out SEMS. If,
as Raphel says, implementing the late media negotiation will only involve
little changes in the code, we'll try to implement it.
Thanks again, nice to learn from all of you. Regards
Anton
4.4. Flow IV
A Controller B
|(1) INVITE offer1 | |
|no media | |
|<---------------------| |
|(2) 200 answer1 | |
|no media | |
|--------------------->| |
|(3) ACK | |
|<---------------------| |
| |(4) INVITE no SDP |
| |--------------------->|
| |(5) 200 OK offer2 |
| |<---------------------|
|(6) INVITE offer2' | |
|<---------------------| |
|(7) 200 answer2' | |
|--------------------->| |
| |(8) ACK answer2 |
| |--------------------->|
|(9) ACK | |
|<---------------------| |
|(10) RTP | |
|.............................................|
2010/1/22 Daniel-Constantin Mierla <[email protected]>
>
>
> On 1/21/10 11:30 PM, Juha Heinanen wrote:
>
>> Raphael Coeffic writes:
>>
>> > This should be possible, however not out-of-the box... The main issue
>> is
>> > that SEMS is not (yet) used to send INVITE without SDP offer. However,
>> > as you are looking for a signaling only application (SEMS does not
>> > handle any media itself), it should be possible with little
>> > modifications. Concerning the "click" part of the "click-to-dial", the
>> > easiest way is to define a DI interface for your application plug-in,
>> > and use the xmlrpc2di plug-in to make this interface available over
>> > XMLRPC. Then, it should be a child's play to get your functions called
>> > from some PHP code.
>>
>> this DI call would indeed be a very useful addition to sems. i'm
>> currently using sip router tm.t_uac_wait xmlrpc command for the same
>> purpose, but would prefer sems, because in sip router tm.t_uac_wait
>> blocks the process until invite is answered or times out.
>>
>>
> it is recommended to set sip router to use a different port for xmlrpc so
> sip processing is not affected. Another option is using udp protocol
> directly with MI commands.
>
> The other option to implement click-to-dial is using dialog module with
> dlg_bridge:
> http://kamailio.org/docs/modules/3.0.x/modules_k/dialog.html#id2524918
>
> With the benefit of easiness to use and no blocking, drawback: no return of
> the sip reply code for entire operation.
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla
> * http://www.asipto.com/
>
>
> _______________________________________________
> Sems mailing list
> [email protected]
> http://lists.iptel.org/mailman/listinfo/sems
>
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
