Hi,
See XX-8499. I tightened up error handling on the 4.2 and main
branches. If you are using 4.0.4, you can look at the diff
corresponding to this issue and apply and rebuild sipxbridge.jar.
Regards,
Ranga
On Tue, Jun 1, 2010 at 2:10 PM, Sven Evensen wrote:
> Ranga, Dale
>
> The same thing h
Ranga, Dale
The same thing happened when I used IP addresses.
1 REGISTER-287
2 REGISTER-287
3 401-287
4 REGISTER-288 w/nonce
5 401-288
6 200-288
I believe there are three faults.
1. The ITSP (Asterisk) should not send cseq 288 in line 5.
2. sipX should not disregard the 200 OK
On Tue, Jun 1, 2010 at 2:03 PM, WORLEY, Dale R (Dale) wrote:
>
> From: Sven Evensen [sven.even...@onrelay.com]
>
> should be cseq=2 in line 5, which is a fault from the ITSP?:
>
> sipX sends REGISTER cseq=1.
> after 500ms sipX resends REGISTER cseq=1.
> a f
From: Sven Evensen [sven.even...@onrelay.com]
should be cseq=2 in line 5, which is a fault from the ITSP?:
sipX sends REGISTER cseq=1.
after 500ms sipX resends REGISTER cseq=1.
a few ms later 401 cseq=1 is received for first REGISTER.
sipX sends new REGIST
I see I have a typo in my scenario below.
should be cseq=2 in line 5, which is a fault from the ITSP?:
sipX sends REGISTER cseq=1.
after 500ms sipX resends REGISTER cseq=1.
a few ms later 401 cseq=1 is received for first REGISTER.
sipX sends new REGISTER with nonce cseq=2.
sipX receives 401 cseq=
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of Sven Evensen
[sven.even...@onrelay.com]
The problem is a little more subtle, I will try to explain. And I will send you
a snapshot too.
sipX sends REGISTE
To: Sven Evensen; mra...@gmail.com
> Cc: sipx-users@list.sipfoundry.org
> Subject: Re: [sipx-users] SIP trunk stops registering
>
> portahk.cordiaip.netx
>
> It can't resolve the A record for the above entry. If it can't find it, it
> can't register to it. Check the DNS resolv
net]
Sent: 01 June 2010 00:38
To: Sven Evensen; mra...@gmail.com
Cc: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] SIP trunk stops registering
portahk.cordiaip.netx
It can't resolve the A record for the above entry. If it can't find it, it
can't register to it. Check
My conclusion regarding 401 being ignored is the fact that two 401 are received
on same trunk, then a 200 OK is received, but the trunk is still disabled.
And why does the trunk not try to register again, ever. Until sipXBridge
restarted?
I will try to use IP addresses like you suggest, see if
On Mon, May 31, 2010 at 6:15 PM, Sven Evensen wrote:
> Hi Ranga,
>
> I did not quite understand the conclusion. Where is the DNS fault? In sipX?
> And what is it actually causing?
>
> Why does sipX ignore 200 OK after two 401?
How do you conclude that it is being ignored?
> Why does sipX sto
sipx-users-boun...@list.sipfoundry.org
To: M. Ranganathan
Cc: sipx-users@list.sipfoundry.org
Sent: Mon May 31 18:15:17 2010
Subject: Re: [sipx-users] SIP trunk stops registering
Hi Ranga,
I did not quite understand the conclusion. Where is the DNS fault? In sipX?
And what is it actually causing?
Why does sip
Hi Ranga,
I did not quite understand the conclusion. Where is the DNS fault? In sipX? And
what is it actually causing?
Why does sipX ignore 200 OK after two 401?
Why does sipX stop registration of that trunk?
Regards,
Sven
-Original Message-
From: M. Ranganathan [mailto:mra...@gmail.co
On Mon, May 31, 2010 at 2:33 PM, M. Ranganathan wrote:
> On Mon, May 31, 2010 at 1:55 PM, Sven Evensen
> wrote:
>> Hi Ranga,
>>
>> The problem is a little more subtle, I will try to explain. And I will send
>> you a snapshot too.
>>
>> sipX sends REGISTER cseq=1.
>> after 500ms sipX resends REG
On Mon, May 31, 2010 at 1:55 PM, Sven Evensen wrote:
> Hi Ranga,
>
> The problem is a little more subtle, I will try to explain. And I will send
> you a snapshot too.
>
> sipX sends REGISTER cseq=1.
> after 500ms sipX resends REGISTER cseq=1.
> a few ms later 401 cseq=1 is received for first REGI
Hi Ranga,
The problem is a little more subtle, I will try to explain. And I will send you
a snapshot too.
sipX sends REGISTER cseq=1.
after 500ms sipX resends REGISTER cseq=1.
a few ms later 401 cseq=1 is received for first REGISTER.
sipX sends new REGISTER with nonce cseq=2.
sipX receives 401 c
If sipxbridge sees two 401 or 407 for two successive REGISTER
transactions that implies it tired to authenticate, failed, tried
again, failed and hence there is a problem with the credentials. If
such is the case, then sipxbridge will retry again in 60 sec.
This has nothing to do with the 500 ms.
16 matches
Mail list logo
