14 Dec
2005
14 Dec
'05
11:54 a.m.
This is one of those times, when UA started working properly... When
it fails again I'll post the traces from xx.xx.32.38 machine..
Anyway, I print out every message in the console, when it comes (even
before it gets to checking)... When SUBSCRIBE is "stuck", no output
comes in the console of the remote UA... Meaning that , if there is a
problem, then this problem is within NIST-SIP stack... And then I
start wondering again: how come eyeBeam has the same problem? Cause it
definitely doesn't use a NIST-SIP stack...
On 12/14/05, Vaclav Kubart <vaclav.kubart(a)iptel.org> wrote:
May be, that the client is expected other AOR - the
forwarded message from
SER has other than the original.
original: sip:12345@sip.interlab.ait.ac.th
forwarded: sip:12345@203.159.32.38:5060
It is strange, that the UA is not respoding (I expect at leass some 4xx
response). Could you try to catch packets on the 203.159.32.38 too?
You said, that it works if you subscribe to yourself (i.e. the user which
is logged from the xxx.32.38 machine)? May be, that the client reacts only
to SUBSCRIBE request, which is for it, no?
Vaclav
On Wed, 14 Dec 2005, Andrey Kouprianov wrote:
I have just tried eyeBeam... Same result... maybe
it's the network
fault... Our net is connected through the proxy... However, i dont
think this is the problem, cause every other request is patched
through w/o any glitch...
Our net <--> net with proxy <--> sip server net
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers