You might be able to use a Polycom Enhanced Feature Key (EFK) to do this.
On Wed, Feb 15, 2012 at 11:59 PM, Михаил Родионов ma...@siplabs.ru wrote:
The valet parking slot idea is what came to me first (the app can be
easily implemented in FS+Lua morover there are actual examples that can be
On 02/15/2012 06:48 PM, Tony Graziano wrote:
Restart call resolver.
I did a /etc/init.d/sipxecs restart, but the problem was still there.
Restarting only CDR solved the problem.
Plan to upgradeto4.4
ASAP. :-)
Thank you.
Massimo
--
Massimo Vignone
UniMORE - Servizi Informatici - Reti e
Yep, Polycoms rule. But when entering Russian market with their ip phones
they used high-end audiophilic audio gear price lists as a reference (which
is ok if you think they provide vynil-like sound quality with warm
tube-like middles :) ).
IP 560 is $420 with big discount.
Thanks for the reply!
Well, just have them use a code like 7 + ext when they transfer to an
extension for fire and forget and then you could route that to your FS app.
Just like transferring to voicemail is 8 + ext.
On Thu, Feb 16, 2012 at 6:46 AM, Михаил Родионов ma...@siplabs.ru wrote:
Yep, Polycoms rule. But
The template isn't a problem. In fact, there is no problem other than wanting
to have access to both port 5060 and 5080 by any ITSP. When we asked for test
trunks, we asked them to allow three IP's, one on each port.
Since they don't have a GUI, we have to specify which IP and which port so
I find when I gover over 25 the phone becomes problematic. This is a
phone/rls limitation in the 3.3 or earlier firmware. The 3.4 and later
firmware might address this but right now these versions are not directly
supported by sipx.
On Feb 15, 2012 10:36 AM, Marco Colaneri sipxm...@gmail.com
Hello,
We have been attacked again. the CDR report has so many Toll Fraud
attempts. The attacker uses extension numbers that are not even there in
the system like 100 and 101 .. Sometimes uses Unknown number. This also
seems to cause audio path issues as well as call dropping.
My question is, how
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: 1022e.4f3b2...@forum.sipfoundry.org
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 66121
Message-ID: 10249.4f3c8...@forum.sipfoundry.org
Hi Tony,
thank you for your reply.
I think
I think that will break RLS based on past history... I don't think anybody
knows for sure with those kinds of numbers. I'd put the master server on
as fast a server as you can get with a teaming GB network adapter.
Please report back, it sounds like you will test the limits!
Mike
On Wed, Feb
Thanks for this!
2012/2/16 Michael Picher mpic...@ezuce.com
Well, just have them use a code like 7 + ext when they transfer to an
extension for fire and forget and then you could route that to your FS app.
Just like transferring to voicemail is 8 + ext.
On Thu, Feb 16, 2012 at 6:46 AM,
Have a look at XX-9857. It seems that some NOTIFY messages over about 9K in
size get truncated. Unfortunately, I can't exactly pin down how many BLFs the
maximum would be because that would vary from system to system. Even something
as simple as the length of the domain part of the sip URIs
Does sipXecs support, or has anyone setup an fxs gateway at a remote location
without using VPN? Basically a ‘remote worker’ but the endpoint is an fxs
gateway providing dial tone to analog lines?
This message and any files transmitted with it are intended only
Is NAT involved? If not, I think this would be simple enough.
On Thu, Feb 16, 2012 at 4:12 PM, Nathaniel Watkins
nwatk...@garrettcounty.org wrote:
Does sipXecs support, or has anyone setup an fxs gateway at a remote
location without using VPN? Basically a ‘remote worker’ but the endpoint is
NAT would be involved. I think I have a few FXS gateways that aren't in use at
the moment, I might give it a try just to satisfy my own curiosity...
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Tony
I will look into the manual install instructions. Is there something that I
should backup, ie, existing keystore before doing so? Or do I simply
recovery by re-running the self-sign create your own certificate
instructions?
Thanks,
Jes
On Wed, Feb 15, 2012 at 9:05 PM, Dustin Roberts
All,
I was able to follow the manual instructions. Do wild card certificates
not cover sub zone/domains? Our wildcard is for *.sunyulster.edu. Our SipX
Server is ecs1.sipx.sunyulster.edu (sipx.sunyulster.edu being the domain).
I am getting the following error from the browser:
You attempted to
I don't see why it wouldn't work... No different from any other remote
phone.
On Feb 16, 2012 4:26 PM, Nathaniel Watkins nwatk...@garrettcounty.org
wrote:
NAT would be involved. I think I have a few FXS gateways that aren't in
use at the moment, I might give it a try just to satisfy my own
All,
I came up with a workaround, however, I wanted to double check that it was
OK.
I added a same as parent A record (sipx.sunyulster.edu) and set it to the
IP address of the sever. This allows web-access to the web interface using
sipx.sunyulster.edu instead of using the FQDN
Right sorry about that. I saw gateway and assumed fxo.
On Feb 16, 2012 5:03 PM, Michael Picher mpic...@ezuce.com wrote:
I don't see why it wouldn't work... No different from any other remote
phone.
On Feb 16, 2012 4:26 PM, Nathaniel Watkins nwatk...@garrettcounty.org
wrote:
NAT would be
Hi Everyone. I promise
I am not trying to be a troll. I have some serious questions that
I hope I can ask honestly and get some honest feedback about using
the free version of sipXecs as a commercial product.
I implemented sipXecs about a year ago. My
On Thu, Feb 16, 2012 at 9:02 PM, Tim Ingalls t...@sharedcom.net wrote:
Hi Everyone. I promise I am not trying to be a troll. I have some serious
questions that I hope I can ask honestly and get some honest feedback about
using the free version of sipXecs as a commercial product.
Tim, it's at
You should read the book.
On Feb 16, 2012 9:03 PM, Tim Ingalls t...@sharedcom.net wrote:
**
Hi Everyone. I promise I am not trying to be a troll. I have some serious
questions that I hope I can ask honestly and get some honest feedback about
using the free version of sipXecs as a commercial
I attempted to install centos 5 x86 Karoo Bridge and found the
installation package to be broken.
Thanks
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
cacct1odtx6ltmgrv3qvbxikjbyxw0o+kwy53r+x933zhklm...@mail.gmail.com
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 66139
Message-ID: 1025b.4f3d1...@forum.sipfoundry.org
The SipX is
1.4 is only packaged for Centos 6.
On 02/17/2012 10:40 AM, Roman Gelfand wrote:
I attempted to install centos 5 x86 Karoo Bridge and found the
installation package to be broken.
Thanks
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
Tim, This type of email is disappointing for me. They highlight negative
experiences that are experienced by a user, and do nothing to help this
project. I'm sure you are being open and honest, but all that it shows is
that you are struggling with the system, in your deployment, and it gives a
I would have to agree with Tim and state that most of your issues are most
likely ISTP related and/or network related. I am not one of the developers,
so I am not defensive, however, I will say that I have using and testing
SipX on and off since 2004 (going back to the Pingtel days). The one thing
Tim,
All I can say is that I have been running 4.04 (yes, I should upgrade to
the latest version) for over two years using Vitelity without a hitch.
Yes, on occasion I have experienced authentication issues with the ITSP
– all total about 15 times in the last two years – and in every case
I’ve
28 matches
Mail list logo
