On 1/22/10 8:15 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
> 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.
sure, but my understanding is that still process that is running
tm.t_uac_wait is blocked that limits the number of parallel
click-to-dials.
haven't implemented it nor used, but I think it is this way ... blocking.
> 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.
i think we discussed this already earlier: use of dlg_bridge does not
allow click-to-dial to a specific contact of the AoR.
Have you tried to set To to contact address and outbound proxy to
received address? The only troubles I can think of are with multi-homed
environment, to select the outgoing socket, if the destination is
reachable from all network interfaces kamailio is listening.
Anyhow, most of the click-to-dial pages do not expose the contact
details. To get your way, first it should fetch location records for
that user and then you select one.
This may not be available (e.g., willing to click to dial to a foreign
network user) or not exposed to web. Besides, in most of the cases, the
contact info a person gets is sip address, that being added to personal
phonebook and used from there to dial.
Cheers,
Daniel
--
Daniel-Constantin Mierla
* http://www.asipto.com/
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
