Hello, o Jeremy A [07/07/08 11:29]: > Hello, > > I have encountered a problem with connecting a call to a web conference > via B2B > > My setup is as per the tutorial and has > > ser 10.1.39.11:5060 forwarding calls to localhost 127.0.0.1:10070 > ser 10.1.39.11:10070 / 127.0.0.1:10070 receives and processes calls for sems > sems hosts the usual collection of applications including my python ivr > application and webconference > > The call sequence: > > sip:[EMAIL PROTECTED] calls my ser-sems setup at 10.1.39.5060 and is > connected to my application > my application uses di methods to create a web conference > [EMAIL PROTECTED]:10070 and dial out to other attendees > my application then uses connectCallee to connect a B2B leg of the > original call to [EMAIL PROTECTED]:10070 > An SDP parsing error is then returned. > > The reason I want to use a B2B leg is so that when the originator > sip:[EMAIL PROTECTED] hangs up, my application can kick all the other users > out and close the conference. I think it would be simpler to add a function to ivr to connect the call itself to the conference, without creating a second leg (and the you get onBye callback).
> > The relevant log section is > [...] it looks like the INVITE sent out has empty body: > (15884) DEBUG: execute (AmInterfaceHandler.cpp:151): req.next_hop = <> > (15884) DEBUG: execute (AmInterfaceHandler.cpp:156): hdrs = <P-MsgFlags: 0 > > > (15884) DEBUG: execute (AmInterfaceHandler.cpp:161): body = <> > (15884) DEBUG: execute (AmInterfaceHandler.cpp:172): Request OK: > dispatch it! can you try to see why it does not carry the body from the caller leg? (put some DBG in e.g. AmB2BCalleeSession::onB2BEvent, and in AmB2BCallerSession::connectCallee look at invite_req.body) > > I should also point out that I get a python error in the script about > this time that is located shortly after connectCallee function call. It > seems that there may be a bit of corruption occurring during > ConnectCallee that is causing both problems. most interesting I find the self.SerProx.di, what is SerProx? how does it call di functions from ivr? are you using the code from xmlrpc2di? maybe there is an exception thrown in the SerProx.di method? Stefan -- Stefan Sayer VoIP Services [EMAIL PROTECTED] www.iptego.com iptego GmbH Am Borsigturm 40 13507 Berlin Germany Amtsgericht Charlottenburg, HRB 101010 Geschaeftsfuehrer: Alexander Hoffmann _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
