On Wed, Oct 26, 2011 at 6:16 PM, Sébastien QUESSON
wrote:
> [SOLVED]
> bridge sends a reinvite 45 seconds before expiration
> Session-Expires: 1800;refresher=uac
> Min-SE: 90
Made a permanent fix so it will be available in next update. Please
retest if works as expected when rpms are published in
day, October 26, 2011 4:06:35 PM
> Subject: Re: [sipx-users] session expiry -> calls dropped
> to George and Joegen
> I haven't be trying 1800 with the new jar. Let's go...
> - Original Message -
> > From: "Joegen Baclor"
>
> > To: &quo
to George and Joegen
I haven't be trying 1800 with the new jar. Let's go...
- Original Message -
> From: "Joegen Baclor"
> To: "Discussion list for users of sipXecs software"
>
> Sent: Wednesday, October 26, 2011 3:25:57 PM
> Subject: Re:
On 10/26/2011 09:25 PM, Joegen Baclor wrote:
> On 10/26/2011 09:20 PM, George Niculae wrote:
>> On Wed, Oct 26, 2011 at 3:41 PM, Sébastien QUESSON
>> wrote:
>>> I just replaced the sipXbridge.jar and restarted sipxproxy,
>>> siptrunk,sipregistrar with debug mod.
>>> Calls were dropped again at 18
On 10/26/2011 09:20 PM, George Niculae wrote:
> On Wed, Oct 26, 2011 at 3:41 PM, Sébastien QUESSON
> wrote:
>> I just replaced the sipXbridge.jar and restarted sipxproxy,
>> siptrunk,sipregistrar with debug mod.
>> Calls were dropped again at 1800 whereas session timer is on 10800
>>
> What if yo
On Wed, Oct 26, 2011 at 3:41 PM, Sébastien QUESSON
wrote:
> I just replaced the sipXbridge.jar and restarted sipxproxy,
> siptrunk,sipregistrar with debug mod.
> Calls were dropped again at 1800 whereas session timer is on 10800
>
What if you set your timer to 1800, does it solve the problem?
Ge
-
> From: "Michael Picher"
> To: "Discussion list for users of sipXecs software"
>
> Sent: Wednesday, October 26, 2011 11:47:18 AM
> Subject: Re: [sipx-users] session expiry -> calls dropped
> On Wed, Oct 26, 2011 at 5:35 AM, George Niculae < geo...@ezuce
On Wed, Oct 26, 2011 at 5:35 AM, George Niculae wrote:
> On Wed, Oct 26, 2011 at 12:29 PM, George Niculae wrote:
> > On Tue, Oct 25, 2011 at 4:09 AM, Joegen Baclor
> wrote:
> >> Indeed, Please reopen the tracker and attach the logs you have provided
> >> here. The session timer still got cance
On Wed, Oct 26, 2011 at 12:29 PM, George Niculae wrote:
> On Tue, Oct 25, 2011 at 4:09 AM, Joegen Baclor wrote:
>> Indeed, Please reopen the tracker and attach the logs you have provided
>> here. The session timer still got cancelled.
>
> Per Joegen's request I created and attached to JIRA a sip
On Tue, Oct 25, 2011 at 4:09 AM, Joegen Baclor wrote:
> Indeed, Please reopen the tracker and attach the logs you have provided
> here. The session timer still got cancelled.
Per Joegen's request I created and attached to JIRA a sipXbridge.jar
with a potential fix for this. Please give it a try
Indeed, Please reopen the tracker and attach the logs you have provided
here. The session timer still got cancelled.
"2011-10-24T20:21:55.251000Z":325:JAVA:DEBUG:sipx.domain.al:Timer-1::DialogContext:"cancelSessionTimer
gov.nist.javax.sip.stack.SIPDialog@79b66b06"
"2011-10-24T20:21:55.
rsday, December 02, 2010 7:51 AM
> To: Discussion list for users of sipXecs software
> Subject: Re: [sipx-users] session expiry
>
> On Wed, Dec 1, 2010 at 8:55 PM, Kris Amy wrote:
> > When will this patch be integrated? Is it possible to patch the
> > current
> &g
On Wed, Dec 1, 2010 at 8:55 PM, Kris Amy wrote:
> When will this patch be integrated? Is it possible to patch the current
> 4.2.1 .jar (so I can rollback to stable as opposed to 4.3.2).
4.2.1 is latest stable, so yes, i can be applied to 4.2.1. may take
me a few days to get to it as there is no
Hi Joegen,
When will this patch be integrated? Is it possible to patch the current 4.2.1
.jar (so I can rollback to stable as opposed to 4.3.2).
Cheers,
Kris
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundr
the sipxbridge log.
>
> -Original Message-
> From: Joegen Baclor [mailto:jbac...@ezuce.com]
> Sent: Wednesday, 1 December 2010 1:24 PM
> To: Discussion list for users of sipXecs software
> Cc: Tony Graziano; Kris Amy
> Subject: Re: [sipx-users] session expiry
>
> T
: Wednesday, 1 December 2010 11:04 PM
To: Kris Amy
Cc: Discussion list for users of sipXecs software; Tony Graziano
Subject: Re: [sipx-users] session expiry
Based on the logs that i saw, it seems that sipXbridge is destroying the
sip timer when it gets a 407 and not start a fresh when when it sends
the re
gt;
> On 12/01/2010 12:38 PM, Kris Amy wrote:
>> Attached is the sipxbridge log.
>>
>> -Original Message-
>> From: Joegen Baclor [mailto:jbac...@ezuce.com]
>> Sent: Wednesday, 1 December 2010 1:24 PM
>> To: Discussion list for users of sipXecs software
log.
>
> -Original Message-
> From: Joegen Baclor [mailto:jbac...@ezuce.com]
> Sent: Wednesday, 1 December 2010 1:24 PM
> To: Discussion list for users of sipXecs software
> Cc: Tony Graziano; Kris Amy
> Subject: Re: [sipx-users] session expiry
>
> Tony,
>
> I thi
gt;>
>>>
>>> -Original Message-----
>>> From: sipx-users-boun...@list.sipfoundry.org
>>> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Tony
>>> Graziano
>>> Sent: Wednesday, 1 December 2010 12:24 PM
>>> To:
-- Original Message -
> From: sipx-users-boun...@list.sipfoundry.org
>
> To: Discussion list for users of sipXecs software
>
> Cc: Kris Amy
> Sent: Tue Nov 30 21:47:53 2010
> Subject: Re: [sipx-users] session expiry
>
> How can disconnecting the call after 14
rg] On Behalf Of Tony
>> Graziano
>> Sent: Wednesday, 1 December 2010 12:24 PM
>> To: sipx-users@list.sipfoundry.org
>> Subject: Re: [sipx-users] session expiry
>>
>> I can try tomorrow here but...
>>
>> If fs is sending 120 but sipx is set for 180, then
software
Cc: Kris Amy
Sent: Tue Nov 30 21:47:53 2010
Subject: Re: [sipx-users] session expiry
How can disconnecting the call after 148 seconds be RFC compliant if the
expiration is 180? If you will comply with the RFC, the call should
only be torn down after 180+1 has elapsed. See, I can pro
> From: sipx-users-boun...@list.sipfoundry.org
> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Tony Graziano
> Sent: Wednesday, 1 December 2010 12:24 PM
> To: sipx-users@list.sipfoundry.org
> Subject: Re: [sipx-users] session expiry
>
> I can try tomorrow here
-users-boun...@list.sipfoundry.org] On Behalf Of Tony Graziano
Sent: Wednesday, 1 December 2010 12:24 PM
To: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] session expiry
I can try tomorrow here but...
If fs is sending 120 but sipx is set for 180, then why don't you change the
timer in
for users of sipXecs software'
Sent: Tue Nov 30 16:37:09 2010
Subject: Re: [sipx-users] session expiry
Are you able to send me a trace of 4.2.1 with auth?
--
Kris Amy
Systems Administrator
NEXTDC
Level 4, 20 Wharf Street
BRISBANE QLD 4000
Direct: +61 7 3177 4716
Email: kris
-users-boun...@list.sipfoundry.org] On Behalf Of Tony Graziano
Sent: Wednesday, 1 December 2010 7:36 AM
To: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] session expiry
4.2.1, And 4.0.4 and 4.4-snapshot.
Tony Graziano, Manager
Telephone: 434.984.8430
Fax
://www.myitdepartment.net/gethelp/
- Original Message -
From: sipx-users-boun...@list.sipfoundry.org
To: 'Discussion list for users of sipXecs software'
Sent: Tue Nov 30 16:27:06 2010
Subject: Re: [sipx-users] session expiry
Hrmms OK.
What version are you running?
Ch
Subject: Re: [sipx-users] session expiry
I have done that on both auth/nonauth trunks without an issue.
On 11/30/10, Kris Amy wrote:
> I have rolled back to 3.1.3RevC and the issue still exists.
>
> Is anyone able to setup an authenticated trunk and see if the issue exists?
> Nikolay w
Why are you using Polycom 3.3.1 firmware (has not been tested yet,
> 3.1.3RevC is very safe right now).
> What codecs does the ITSP support?
> Does the ITSP support reinvites?
>
> On Tue, Nov 30, 2010 at 5:38 AM, Kris Amy
> mailto:kris@nextdc.com>> wrote:
>
&g
foundry.org<mailto:sipx-users@list.sipfoundry.org>"
mailto:sipx-users@list.sipfoundry.org>>
Date: Tue, 30 Nov 2010 05:03:24 -0500
To: "sipx-users@list.sipfoundry.org<mailto:sipx-users@list.sipfoundry.org>"
mailto:sipx-users@list.sipfoundry.org>>
Subject: Re: [sipx
nt:* Tuesday, 30 November 2010 5:15 PM
>
> *To:* 'sipx-users@list.sipfoundry.org'
> *Subject:* Re: [sipx-users] session expiry
>
>
>
> Hi All,
>
>
>
> Please ignore. Found this link….
>
>
>
>
> http://forum.sipfoundry.org/index.php?t=tr
...@list.sipfoundry.org] On Behalf Of Kris Amy
Sent: Tuesday, November 30, 2010 11:51 AM
To: 'Discussion list for users of sipXecs software'
Subject: Re: [sipx-users] session expiry
What is the easiest way to dump the siptrace out like that (I am looking at
a tcpdump)
Cheers,
Kris
t for users of sipXecs software'
Subject: Re: [sipx-users] session expiry
Kris,
i'm interested in the problem (though i'm not a developer).
I tried to replicate the problem at my site.
I set session timer interval to 180 like you.
And, as far as i understand, sipxbridge does send r
To: 'sipx-users@list.sipfoundry.org'
Subject: Re: [sipx-users] session expiry
Hi All,
Please ignore. Found this link
http://forum.sipfoundry.org/index.php?t=tree&th=14750&S=e2dbb4c4b44c81a1b206579d64510bd0#page_top
Cheers,
Kris
From: sipx-users-boun...@list.sipfoundry.org
sday, 30 November 2010 4:48 PM
To: 'sipx-users@list.sipfoundry.org'
Subject: [sipx-users] session expiry
Hi all,
It would seem that sipx is not abiding by the RFC for session-expire and
refresh timer.
I currently have Session Timer Interval set to 180.
According to the RFC the http://t
Hi all,
It would seem that sipx is not abiding by the RFC for session-expire and
refresh timer.
I currently have Session Timer Interval set to 180.
According to the RFC the http://tools.ietf.org/html/rfc4028#section-10
Similarly, if the side not performing refreshes does not receive a
sessi
36 matches
Mail list logo
