Hello everyone, I am trying without success to use click2dial ...
Here is my setup :
- debian etch 64 bits
- libxmlrpc++ 0.7+cvs20040713-2
- sems 1.1.0 final tarball from iptel website
I compiled sems 1.1.0 and am using it without a glitch with other
modules (without di or xmlrpc2di).
I then compiled and installed the xmlrpc2di, di_dial and click2call
modules.
xmlrpc is compiled with the debian xmlrpc++ library, without patching
(as suggested in a previous thread).
I tried both with and without XMLRPCPP_SUPPORT_STRUCT_ACCESS, am using
-DHAVE_XMLRPCPP_SSL.
Now, I took a look at the example in apps/click2dial, which suggest
using this :
s = ServerProxy(xmlrpc_url)
s.dial_auth_b2b("click2dial", ....)
When I do that, here is what I get :
dial_auth_b2b: unknown method name
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 ...
Still, no luck :
DEBUG: [40706960] execute (XMLRPC2DI.cpp:446): XMLRPC2DI: factory
'di_dial' function 'dial'.
DEBUG: [40706960] dialout (DIDial.cpp:153): dialout application
'click2dial', user 'default_en', from 'sip:xxxx...@xxxxxxx', to
'sip:yyyyyy...@yyyyyyyyyy'.
DEBUG: [40706960] getAnnounceFile (Click2Dial.cpp:87): trying
'/usr/lib/sems/audio//default_en.wav'
(which exists and is there)
ERROR: [40706960] startSessionUAC (AmSessionContainer.cpp:233):
unexpected exception.
ERROR: [40706960] send (SipCtrlInterface.cpp:352): Invalid transaction
key: invalid bucket ID
So I have two questions :
1/ What do I miss / did wrong not to be able to use the example file ?
Grepping the source for the method name yields no result, where is it
defined and how does it work ? The args mapping seems different from
di_dial dial or dial_auth methods, and enable passing args to the
factory that dial will call subsequently (click2dial in my case).
2/ Could the "Invalid transaction key: invalid bucket ID" in
SipCtrlInterface.cpp be a bug in the embeded SIP parser ? Should I setup
an external kamailio server to be used a SIP parser and try that
instead ?
BTW, other that this, I do not have any other problems with that
release, and am pretty impressed overall !
I currently try to port a homebuild app that used to run on sems cvs
changeset 328 (pretty old, if not ancient) and I am suffering a bit, but
heck, it is for the best I guess (I had custom patched parts of the core
at the time, now forward porting it is a pain, so I will probably just
rewrite from scratch) :-)
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
