Google Search:

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

[reSIProcate] 503 Reason

From: Volodymyr.Stepanov@xxxxxxxxxxx
Date: Tue, 12 Jun 2007 09:26:59 +0300

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

Follow-Ups:
- Re: [reSIProcate] 503 Reason
  - From: Scott Godin

Prev by Date: [reSIProcate] How to implement Three-way calling and call wait features with Resiprocate
Next by Date: Re: [reSIProcate] 503 Reason
Previous by thread: [reSIProcate] How to implement Three-way calling and call wait features with Resiprocate
Next by thread: Re: [reSIProcate] 503 Reason
Index(es):
- Date
- Thread