[reSIProcate] assert in TransactionState::sendToWire under load

[John Draper]

Sandeep Sharma wrote:

>Hello,
>
>I am still seeing this assert fire under a load test.. The assert is in
>TransactionState::sendToWire (for a client non-invite). In the following
>code, the assert that fires is "assert(mTarget.getType() !=
>UNKNOWN_TRANSPORT);"
>
>Poking into the core, I found this in the mDnsResult:
>mTarget = "dev5.corp.jabber.com"
>mSRVKey = "_sip."
>mTransport = TLS
>mPort = -1
>pType = Pending
>
>Of course this->mTarget is some default value, with type =
>UNKNOWN_TRANSPORT. Looks like it has not been assigned any value after
>the object was constructed.
>
>It appears that a DNS query for dev5.corp.jabber.com is still getting
>resolved when a second message is sent on the same TransactionState.
>Under what conditions can this happen?
>
I don't know if this is related, but when i try to register as 
sip:u354@<host>
it would try and register to the web server instead of the sip server.

Wouldn't the sip part of the uri be used to properly query the DNS to get
the IP address of the sip server at that domain?   Sip server is on a 
different
machine.

I mentioned somthing like this in an earlier posting, which I have yet 
to get
a reponse.

John