Well, with the help of this great group, I got the 5 minute drop problem fixed
by putting an internal SBC in front of our sip gateways and it fixed
everything! Now.our cisco crashes on every incoming call. Without fail, a
call comes inbound on the cisco and immediately crashes it. We remove
the open internet, can exist perpetually. These "Bye" messages
>>> arent random. But I think the issue is not "Bye" messages, but rather the
>>> media disappearing after 5 minutes. Again, this is happening from all
>>> providers including a AS5350 that is on the sam
sources on the list that can
> probably identify where the issue is very quickly for you.
>
> From: sipx-users-boun...@list.sipfoundry.org
> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Trevor Francis
> Sent: Thursday, February 04, 2010 12:29 PM
> To: Dale W
>
> From: sipx-users-boun...@list.sipfoundry.org
> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Trevor Francis
> Sent: Thursday, February 04, 2010 12:29 PM
> To: Dale Worley
> Cc: sipx-users@list.sipfoundry.org
> Subject: Re: [sipx-users] Dropped Calls
>
>
Feb 4, 2010, at 2:18 PM, Dale Worley wrote:
> On Thu, 2010-02-04 at 13:39 -0600, Josh Patten wrote:
>> Same thing happened to me. Random BYE from various devices. Only
>> happened when using sipXbridge.
>
> In Trevor Francis' case, the device generating the BYE calls itself
On Feb 4, 2010, at 1:38 PM, Dale Worley wrote:
> On Thu, 2010-02-04 at 11:37 -0600, Trevor Francis wrote:
>> Attached are call traces for calls that went silent.
>
> In both cases, the signaling looks normal; the device at
> 67.152.1.202:5060 terminated the call by sendi
Interesting to note that after the 5 minute drop, a few of the sip providers
dial the extension back and the call continues as normal..for another 5
minutes or so
--
Trevor G. Francis
President
trevor.fran...@tgrahamcapital.com
Ph. +1 888.616.0662
Fx. +1 214.722.1318
4608 Abbott Ave,
We are having a very strange problem. We cannot hold more than 5 minutes or so
on a few different calling methods on SipX. We are running the latest version
from ISO.
We have tested the following configuration.
Inbound Call (E1) --> Cisco AS5350 --> SipX --Local Extension ---Fails After 5
min
addressed to: tfran...@fas.harvard.edu
--
On Feb 4, 2010, at 11:35 AM, Dale Worley wrote:
> On Thu, 2010-02-04 at 11:17 -0600, Trevor Francis wrote:
>> We just identified the calls dont drop. They go silent on both ends of
>> the call.
>
> That usually indicates a problem w
to: tfran...@fas.harvard.edu
--
On Feb 4, 2010, at 10:46 AM, Dale Worley wrote:
> On Thu, 2010-02-04 at 10:36 -0600, Trevor Francis wrote:
>> Thank you. We will do tracing on the calls. I am very unfamiliary with
>> SipX as far as a platform. Do I need to enable more verbosity on
I am in the process of having a few custom Jasper reports produced to parse
CDR's into a format useful for billing. Is there a guide on where to actually
publish these reports on the SipXecs server? I am unfamiliar with how Jasper
Reporting works in SipXecs. Is there a directly under which I can
emails should be addressed to: tfran...@fas.harvard.edu
--
On Feb 4, 2010, at 10:28 AM, Dale Worley wrote:
> On Thu, 2010-02-04 at 10:18 -0600, Trevor Francis wrote:
>> I am running the latest release and having serious problems with
>> dropped calls. [...] Do you guys have a suggesti
I am running the latest release and having serious problems with dropped calls.
We have tried using different endpoint equipment and adjusted QOS on our router
to prioritize voice traffic. Neither of these have resolved any of our issues.
Today, I noticed a post about proxying media through the
13 matches
Mail list logo
