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 :-)


> > 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.


> 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 ...
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


<<attachment: stock_smiley-1.png>>

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

Reply via email to