< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate] 503 Reason


The answer was posted yesterday:

 

>You can just check if getReceivedTransport returns 0 (NULL) in order to determine if a message is internally generated.

> 

>Scott

 

Cheers,

Scott

 

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Volodymyr.Stepanov@xxxxxxxxxxx
Sent: Tuesday, June 12, 2007 2:27 AM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] 503 Reason

 


I saw previous topic about this problem,but there was no answer...
So ,is it possible to recognize 503 and other errors source (generated internally by stack or from the wire).
Thanks!

Best regards,

Volodymyr Stepanov
Junior Software Engineer

A R I C E N T

03040 Kyiv, Ukraine
Vasyl'kivska 14
Office: +38044-494-26-00 Ext 514
Mobile: +38067-427-85-95
MSN : stepanov_v_m@xxxxxxxxxxx
ICQ : 272708933