[reSIProcate] 503 Reason
Scott Godin
slgodin at icescape.com
Tue Jun 12 07:55:45 CDT 2007
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 at list.resiprocate.org
[mailto:resiprocate-devel-bounces at list.resiprocate.org] On Behalf Of
Volodymyr.Stepanov at aricent.com
Sent: Tuesday, June 12, 2007 2:27 AM
To: resiprocate-devel at list.resiprocate.org
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 at hotmail.com
ICQ : 272708933
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070612/8308169c/attachment.htm>
More information about the resiprocate-devel
mailing list