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

[reSIProcate-users] Why TransactionState set mDnsRestult as 0

From: 海滨 <lhb8859138@xxxxxxx>
Date: Sun, 19 Mar 2017 08:29:09 +0800 (CST)


Hi all,


Does anyone know why TransactionState set mDnsRestult as 0 when receive the 503 
response from wire if mIsReliable=false from release 1.8, instead of blacklist 
the last result(which is implemented in 1.7)? I can't see any information about 
this change in the release note.


Thanks

Follow-Ups:
- Re: [reSIProcate-users] [reSIProcate] Why TransactionState set mDnsRestult as 0
  - From: Scott Godin

Prev by Date: Re: [reSIProcate-users] Called UdpTransport::stunSendTest cause resip_assert triggered when no internet connection
Next by Date: Re: [reSIProcate-users] [reSIProcate] Why TransactionState set mDnsRestult as 0
Previous by thread: Re: [reSIProcate-users] Called UdpTransport::stunSendTest cause resip_assert triggered when no internet connection
Next by thread: Re: [reSIProcate-users] [reSIProcate] Why TransactionState set mDnsRestult as 0
Index(es):
- Date
- Thread