Thanks for the input. I've been testing/using fax reception since we started
testing 4.4.0 but only with PRI/SIP audiocodes.
I just wasn't sure if T.38 was something which is built into sipx so that I
could use T.38 trunks directly to sipx.
On Fri, 14 Oct 2011 18:33:09 -0400, Tony Graziano wr
The release notes are always on the wiki.
http://wiki.sipfoundry.org/display/sipXecs/sipXecs+4.4
On Fri, Oct 14, 2011 at 6:13 PM, m...@grounded.net wrote:
> Features and specs mentions T.38 reception being added but I can't tell if
> it's included now.
> It appears that there was work on addin
Yes. If your provider or gateway supports t.38. You must map a DID number to
the user unified messaging screen. The fax sent to the fax DID number (must
also create a corresponding fax "box" first) will show up in their email if
successful. IM alerts also function. If you go to the unified messagin
Features and specs mentions T.38 reception being added but I can't tell if it's
included now.
It appears that there was work on adding T.38 to sipx but what is not clear to
me is if this is a patch or if it was added in one of the updates for 4.4.0?
Hello,
I am getting SIP "408 Request timeout" message with the Reason "Reason:
~~id~bridge;cause=213;text="Relayed Error Response" ". I captured SIP
packets on the server, what happens is: when sipx receives a call from the
IP phone to a number with prefix 1, it should route it to the gateway with
I think this is a
Kumaran question. In his use case it was a click-to-call use case. In all
cases it should still pass the full callerid.
If the + is not being handled by the click to call portal, that's more
likely a click-to-call issue, but I thought that had been fixed a long time
ago.
On Fri
On Fri, Oct 14, 2011 at 8:19 AM, Tony Graziano
wrote:
> I am going to suggest that: http://track.sipfoundry.org/browse/XX-5120
> Should be rolled back. If the callerid is +(whatever), it's a valid e.164
> format and should be dial-able. It should not be removed. It is correct the
> caller is an ou
Be sure to update your system to the most recent sipxecs 4.4, there
have been a number of memory leak fixes. One in particular with
sipXimbot that will grow w/o bounds if it cannot connect to registrar
plugin for any reason.
FYI: 4.4's internal database storage (IMDB) was used in anger in a lot
o
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <63997>
Message-ID:
So, the conclusion is that I've got to upgrade to 4GB RAM.
I'll give you feedback if still there is something
Thanks for advice! I wasn't aware of this issue.
John
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Michael Picher
Sent: Friday, October 14, 2011 4:08 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipxec
There's a mem leak
http://track.sipfoundry.org/browse/XX-9236
On Oct 14, 2011 8:56 AM, "Ioannis Pittaras" wrote:
> I'm using it manually. It's not configured to auto-backup. Why?
>
> John
>
>
> -Original Message-
> From: sipx-users-boun...@list.sipfoundry.org [mailto:
> sipx-users-boun.
I'm using it manually. It's not configured to auto-backup. Why?
John
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Matthew Kitchin
(usenet/public)
Sent: Friday, October 14, 2011 3:41 PM
To: Discussion list
Are you using the sipx backup program?
--Original Message--
From: John Pi
Sender: sipx-users-boun...@list.sipfoundry.org
To: sipx-users@list.sipfoundry.org
ReplyTo: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipxecs hardware specs
Sent: Oct 14, 2011 7:23 AM
Co
Thanks for the update Tony
Regards,
Kumaran T
On 10/14/2011 5:58 PM, Tony Graziano wrote:
Actually, the JIRA is correct, it says that the "+" and "-" characters
are ignored when interpeting the VM. That is the correct thing to do.
If you are stripping the "+" somewhere, you can optionally lea
On Fri, Oct 14, 2011 at 8:23 AM, John Pi wrote:
>
> Content-Type: text/plain;
> charset="utf-8"
> Content-Transfer-Encoding: 8bit
> Organization: SipXecs Forum
> In-Reply-To: ba...@mail.gmail.com>
> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <63988>
> Message-ID:
>
>
>
> Is it a good idea to
Actually, the JIRA is correct, it says that the "+" and "-" characters are
ignored when interpeting the VM. That is the correct thing to do. If you are
stripping the "+" somewhere, you can optionally leave it "unstripped". In
either case, it's a dialplan entry you need to be able to return the call
But in the issue http://track.sipfoundry.org/browse/XX-5120 if + is
not stripped means then in VM-Through TUI will play the name as "Outside
caller and not the number" So + is stripped then proper format was not
displayed.Either way its seem to be a issue..I think it would be nice
that de
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <63988>
Message-ID:
Is it a good idea to configure the system to restart every
few days at midnight to keep the memory usage in lo
I am going to suggest that: http://track.sipfoundry.org/browse/XX-5120
Should be rolled back. If the callerid is +(whatever), it's a valid e.164
format and should be dial-able. It should not be removed. It is correct the
caller is an outside caller. I think the JIRA case needs to be revisitied.
On Fri, Oct 14, 2011 at 3:07 PM, Tony Graziano
wrote:
> I typically see 2.8 - 3.3GB of memory use after 2 weeks in a new 4.4
> install. low AA use. 2GB is simply not enough. Does it matter what processes
> are swapping memory if you have "just not enough"? Inquiring minds want to
> now!
>
Agree,
We will soon be upgrading to 8 GB on our systems. After a week or two, the
system starts swapping and causes problems with phone calls. A reboot fixes it
temporarily, but we need more RAM.
The swapping only happens on our primary system. The backup server that runs
fewer processes is fine at
I typically see 2.8 - 3.3GB of memory use after 2 weeks in a new 4.4
install. low AA use. 2GB is simply not enough. Does it matter what processes
are swapping memory if you have "just not enough"? Inquiring minds want to
now!
On Fri, Oct 14, 2011 at 8:02 AM, George Niculae wrote:
> On Fri, Oct 1
On Fri, Oct 14, 2011 at 3:00 PM, Tony Graziano
wrote:
> 4GB ram is the real minimum. I always spec at 8 on all systems. When you
> start using swap, you will have issues, it means you need more ram. I expect
> you will use more than 4gb over a month or so, so more ram, is better, you
> dont want t
4GB ram is the real minimum. I always spec at 8 on all systems. When you
start using swap, you will have issues, it means you need more ram. I expect
you will use more than 4gb over a month or so, so more ram, is better, you
dont want to get into swap.
On Fri, Oct 14, 2011 at 7:55 AM, John Pi wro
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <63981>
Message-ID:
Hello everybody,
Which is the recommended hardware specs for sipxecs 4.4
with:
- 30 sip users with vm enabled
- 50 IM users
In that case, why is it being stripped? It's a valid e.164 attribute.
If it is unique enough: 91+10 digits can be changed to "whatever you need to
pass the call".
On Fri, Oct 14, 2011 at 7:48 AM, Kumaran T
wrote:
> **
> Hi Tony,
>What I meant was when outside caller from mobile or landline
What you are saying is: I need a way to call back numbers with a leading
"+".
http://www.myitdepartment.net/support/Three_things_I_really_like_about_sipXecs_4.pdf
Go to the section about dialplans.
Option: The thing to HAVE done was to simply use a dialplan rule to discard
the "+" when dialing o
Hi Todd,
Now I got the point what you are saying.Thanks for the update.So
what do you think whether it can be like this or solution should be
provided?
Regards,
Kumaran T
On 10/14/2011 1:28 PM, Todd Hodgen wrote:
> I understand the issue, from an engineering point, you want to resolve it
I understand the issue, from an engineering point, you want to resolve it
when a + is removed, in software.
What I am saying, which may not be a solution to the issue you describe, but
is a workaround for anyone that is dealing with this issue is to create a
dial plan that for instance has 9 as th
Yes,That to make outside calls.My concern is about displaying the caller
-id for outside caller.SipXecs will discard the +.So we cannot call
directly that number from miss call.Because the caller -id is not
proper.Then we want to enter the number with leading 00 or + followed by
the number to c
You should be able to create a custom dial plan to insert the 00 to make
that call.
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Kumaran T
Sent: Friday, October 14, 2011 12:00 AM
To: Discussion list for users o
Hi All,
When outsider caller calls or deposit a VM then leading + will be
discarded and display the number like 919986252763 instead of
+919986252763.The leading + symbol was discarded for fixing the issue
"http://track.sipfoundry.org/browse/XX-5120".So there should some work
around fix fo
32 matches
Mail list logo