Re: [reSIProcate] Here is a less verbose rendition of my problem.
On 2006.03.22, at 02:26 , John Draper wrote:
This is the problem...
/Volumes/TFKCrunch/Crunch/Development/newSipTestApp/resiprocate/
TransactionS
tate.cxx:357 | discarding stray response: SipResp: 200
tid=OnIn4420eef60913 cseq=INVITE
contact=213.167.79.25:5060 / 1 from(wire)
Why would resip consider my 200 OK response a stray and disgard it?
Could it be a timeout issue? If so, then how do I lengthen the time
I wait for the other party to answer?
Because the branch parameter does not match the original invite?
Check the top-most via's branch parameter in the INVITE you send. I
assure you it was NOT OnIn4420eef60913, as is shown here in the
response.
In fact it was magic-cookie-OnIn....., which is NOT a reSIProcate
generated branch parameter.
In sip, requests and responses are matched using the branch parameter.
(Except 2543bis9 devices, which are hopefully dying)
What SIP implementation is this 'test device'?
A