On Tue, Feb 8, 2011 at 8:41 AM, pscheep...@epo.org wrote:
Not really a solution to the problem IMHO. TCP should work as well.
(.and as old SNA and ATM guy I like connections...)
Anyhow, I wanted to get to the bottom of this and found the following:
(this is all on SipX 4.2.1
I think that if Bria is doing everything according to standards when
Firewall traversal is on Automatic then SipX should be able to cope with
it.
BTW: The patch was mine... I will put it in place myself now.
Regards, Paul
From:
Tony Graziano tgrazi...@myitdepartment.net
To:
Discussion list
its opening a tls connection (port 5061)?
frame 21 (capture b) shows the source port for the invite to come from sipx
on port 5061, and i (also) don't understand why it would do that.
On Mon, Feb 7, 2011 at 5:34 AM, pscheep...@epo.org wrote:
Maybe someone can look at the traces attached.
The
Sorry, some extra info:
10.1.248.31 is the GW (patton).
The Patton doesn't like to use the same port (5060) to 2 different SipX
clusters.
So I configured it to use port 5061 as source port for my second SipX
HA-pair.
See part of the Patton config below:
context sip-gateway gssipx02
Made myself floating again.
rport was enabled on Bria by accident.
Disabled it and now it seems to be OK again..
Still weird that this happened.
rport was invented for UDP, not for TCP, and I cant really find in the RFC
http://www.faqs.org/rfcs/rfc3581.html what the behaviour
If it matters (or not) but I thought I saw in the 3.2 beta that you could
force bria to use udp? Or was that my imagination?
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: tgrazi...@myitdepartment.net
LAN/Telephony/Security and Control
For the second time in a looong time I have the problem that only 50% of
the calls from a GW to a SIP-phone come through, the other 50% go to
voicemail directly.
I have an HA setup and the GW is distributing the calls round-robin to the
2 SipX servers that form an HA-cluster.
Also calls from
