Hi

o Jerome Martin [03/13/09 12:36]:
Hi Stephan :-)

> dial_auth_b2b: unknown method name
set direct_export=di_dial in xmlrpc2di.conf to be able to call dial_auth_b2b directly, like s.dial_auth_b2b(application,announcement,from,to,caller_ruri,callee_ruri,realm,auth_user,auth_pwd)

it is the same as
s.di("di_dial", "dial_auth_b2b", application,announcement,from,to,caller_ruri,callee_ruri,realm,auth_user,auth_pwd)

The direct_export is only to have the convenience that the XMLRPC function names are taken from the module DI API export (that _list function).

ok, makes sense.
This is the bit I was missing, thanks :-)
I also noticed in the sample conf that you can provide a list of modules there, this is cool :-)
yes...that is useful. if you haven't seen it check out this: http://svn.berlios.de/wsvn/sems/trunk/apps/dsm/doc/examples/dsm_di_monit/Readme_ddm.txt and that: http://svn.berlios.de/wsvn/sems/trunk/apps/dsm/doc/examples/dsm_di_monit/dsm_di_monitoring.dsm, there DI from monitoring and dsm is combined.


> Mmmmmh ...
> OK, so I am now trying this, deduced from the code source reading :
> > s = ServerProxy(xmlrpc_url)
> s.di("di_dial", "dial", "click2dial", ...)
> > Of course the args are different, and I do not understand how to passe > args to click2dial through di_dial like this ...
...and I wonder why you did not get
"Need 4 parameters, got 3" error. You need to use dial_auth_b2b to pass the callee_uri to click2dial.

Oh, sorry, I wasn't clear.
I do not need auth, so I used dial instead of auth version, and adjusted the params accordingly.
so did you change Click2Dial.cpp? dial_auth_b2b passes callee uri as extra parameter after the auth - probably it is just missing that extra parameter.


The Problem is this:
"ERROR: [40706960] startSessionUAC (AmSessionContainer.cpp:233):
unexpected exception." You have got an exception there, I can't see atm where it comes from.

Yes, I know this is the problem, just thought some context could help :-)
Let me retry and try to provide you with more infos ...

Strange though that it is then not able to reply...
I do not understand what you meant by that ...
it runs into that error when sending the Error reply (500 or so).

Stefan
FYI, no SIP packet ever left the machine (so ngrep says) ...

Kind Regards,

*Jérôme Martin **| **LongPhone*
*Responsable Architecture Réseau*
122, rue la Boetie | 75008 Paris
Tel :  +33 (0)1 56 26 28 44
Fax : +33 (0)1 56 26 28 45
Mail : *[email protected]
Web : www.longphone.com <http://www.longphone.com>



------------------------------------------------------------------------

_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

--
Stefan Sayer
VoIP Services

[email protected]
www.iptego.com

IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany

Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to