Bringing this discussion to the list. Thanks.
On 05/09/2011 01:17 PM, Onur Erişgen wrote:
Ok Joegen,
Thanks, I will open a tracker,
Bye
Onur
*From:*Joegen Baclor [mailto:[email protected]]
*Sent:* Monday, May 09, 2011 2:18 AM
*To:* onur.erisgen
*Cc:* Michael Picher; Douglas Hubler; George Niculae
*Subject:* Re: Fwd: SIP TCP issue
Onur,
Ok I am able to get my wireshark functional and is able to see the
messages. Reviewing RFC 3261 it says:
While in the "Proceeding" state, if the TU passes a response with
status code from 300 to 699 to the server transaction, the response
MUST be passed to the transport layer for transmission, and the state
machine MUST enter the "Completed" state. For unreliable transports,
timer G is set to fire in T1 seconds, and is not set to fire for
reliable transports.
Thus, this looks like a bug in our transport layer for TCP. it must
NOT retransmit error responses when sent over a reliable transport.
Please open a tracker for this and assign it to me for 4.6
Joegen
On 05/02/2011 08:34 PM, Michael Picher wrote:
Could you take a peek at this?
---------- Forwarded message ----------
From: *Onur Erişgen* <[email protected]
<mailto:[email protected]>>
Date: 2011/5/2
Subject: SIP TCP issue
To: Michael Picher <[email protected] <mailto:[email protected]>>
Hi Mike,
I need your help; you now, we are playing for a long time with Yealink
phones and we have some issues that try to solve.
We saw that sometimes Yealink phones can't make call during a couple
of minutes. We asked this issue and they said that the server sent to
the phone device two 407 messages and sometimes this process make
problems on phone devices.
I saw that if the phones registered to the system with TCP transport
type, in invite messages, openuc send two 407 messages. If udp used,
then only one 407 messages is received from the server side and the
phones are working really fine.
Then I tried different phone devices using TCP protocol and I saw same
situation.
Do you guess why the system sent two 407 messages?
At this point I use priority for UDP transport on my DNS-SRV records,
and working with yealink phones successfully.
Attached you can find a wireshark log file about this issue (I used
eyebeam while taking log).
Best regards,
*Onur Erisgen*
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
