RE: [reSIProcate] bug in StatelessHandler::process() ?
The stateless proxy has probably undergone some bit rot. Can you run your
test and post the output with the log level set at Log::Stack.
e.g.
./stateless-proxy -l cout -v STACK ...
You should be cautious about using a stateless proxy in a real application.
It is a good example of how to use the stack. However, there are only a
handful of real world situations where a stateless proxy can be used.
Thanks,
Jason
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of
> martin.van.den.berg@xxxxxxxxxxx
> Sent: Thursday, July 29, 2004 1:13 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] bug in StatelessHandler::process() ?
>
>
>
> Hi All,
>
> I would like to use the stateless-proxy example as a base for a
> new application. It compiles and runs on my w2k platform. When
> the stateless-proxy succesfully receives messages (INVITE) from
> my client (RTCSampleVB - a MS RTC client example) it posts the
> request to the transaction controller (in
> StatelessProxy::forwardRequest() - SipStack::sendTo() -
> TransactionController::send() ).
>
> This message is then handled in StatelessHandler::process() where
> it ends in the following "if" branch:
> if (sip->getDestination().transport)
> {
> ...
> }
> else
> {
> ** the message is handled here... **
> DebugLog (<< "Processing request from TU : " <<
> msg->brief());
> StatelessMessage* stateless = new
> StatelessMessage(mController.mTransportSelector, sip);
> mController.mTransportSelector.dnsResolve(sip, stateless);
> }
>
> The strange thing is that no message is sent here. Only the DNS
> resolve is executed, the sip message, stateless message and
> dnsResolve() result are not used anymore... I would expect a
> fourth line where the message is forwarded e.g.:
> mController.mTransportSelector.transmit( ... )
>
> Any ideas?
>
> Martin.