I believe this is a current bug.
On Tue, Apr 10, 2012 at 10:43 PM, Jimmy dimitri_mano...@yahoo.com wrote:
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
camgknjusahehseitn1kobdn1bdg8zs69nugi7rm4d0hegb+...@mail.gmail.com
But this is strange, since I recorded the new greeting via the sipxecs
voicemail menu
The setting in the webinterface doesn't change either.
Strange thing is, when I change the greeting using the web gui, it does work,
but changing via the voicemail menu does not...
From:
if it does not change via the webgui, sipxconfig should be throwing and
error in its log. you should capture that error and open a jira with it.
/var/log/sipxpbx/sipxconfig.log
On Wed, Apr 11, 2012 at 8:06 AM, Henry Dogger h.dog...@telecats.nl wrote:
But this is strange, since I recorded the
Well what I mean is this:
I change using voicemail menu (option 5) then I change voicemail greeting under
option 3. This does not work, no errors are in any logging... I also notice
that the option in the webgui is not changed to what I chose in the voicemail
menu (as it is supposed to be...)
actually you are saying there is no logging for the actio using the IVR
menu, even in the sipxivr log file? if so, a jira should still be opened
showing the erroneous successful set from the sipxivr log.
Normally that would happen if the user box has a permissions issue
(owner/group or rights)
Ah sipxivr.log how stupid of me :S
Must have forgotten to look at this one, sorry I feel ashamed...
2012-04-11T13:26:34.911000Z:103132:sipXivr:INFO:sipxecs1.voipxecs.eq.telecats.nl:Thread-3867::sipxivr:Mailbox::writeMailboxPreferences:change
Greeting 235 failed:
Melcon,
Thank you so much for the information and for the help. I am very grateful for
your assistance.
You were correct. I created the files (sipxplugin.beans.xml
myres.properties). I was sure that a value needed to be placed into the myres
document however I was unable to find the
There is a sample Quick reference guide in the book, but it only
mentions *78 for directed call pickup and *4 for picking up a parked call.
If you read through the TUI section in chapter 8, it mentions the following:
Directed Call Pickup: *78 + ext
Pickup a Parked Call: *4 + park orbit
Our current system has the ability for any ext to set Busy Call
Handling. We use this in a very limited case. It is simply the
forwarding of a call when the ext is busy. Does this exist in sipX? It
is not a hunt group per say because if there is no answer it goes
straight to v-mail and is not
This is dependent on the phone. For example, if you set the maximum number
of calls to 1 on a Polycom phone, then the phone will respond to an INVITE
that it is busy. At this point sipX will move to the next forwarding rule.
There is no specific option to set a busy-only forwarding rule however.
It is likely that you will not be able to change your PIN from the TUI
either. Certificates are tricky...
In later releases of 4.4 the certificate issues have been worked on and
should alleviate this issue.
On Wed, Apr 11, 2012 at 8:29 AM, Henry Dogger h.dog...@telecats.nl wrote:
Ah
With 4.6 you will need to unlearn some of what you have learned :-P
Seriously, big changes, in a good way.
On Tue, Apr 10, 2012 at 1:44 PM, Nathaniel Watkins
nwatk...@garrettcounty.org wrote:
Amazing that 42 fits into such a small paperback…
** **
*From:*
Those are the only feature codes...
Other features are phone specific.
Did you want a SIP Communications System or a TDM PBX? ;-)
Mike
On Wed, Apr 11, 2012 at 10:40 AM, Stiles Watson wat...@datatek-net.comwrote:
There is a sample Quick reference guide in the book, but it only
mentions *78
Just want to know where the differences are so I can communicate those
to the users. If I'm the sipX admin, I need to know more about the
system than anyone else in the company. If I'm asked a question, I need
to be able to answer it.
Thanks for the feedback.
Stiles
On 04/11/2012 12:07 PM,
What you won't find is a system that goes toe to toe with 20 year old Key
system functionality. It's pretty close but you'll be missing a few
things. Some users can live without them and some can't.
Mike
On Wed, Apr 11, 2012 at 12:12 PM, Stiles Watson wat...@datatek-net.comwrote:
Just want
Hello,
Since i've updated my sipxecs to 4.4.0- 2012-02-08 version i got error with
phonelogd:
[root@sipx ~]# service phonelogd start
rsyslog runtime error(-2066): could not load module
'/lib/rsyslog/lmnet.so', dlopen: /lib/rsyslog/lmnet.so: cannot open shared
object file: No such file or
Realize you are asking for a digital system to return a BUSY signal when
calling a user with a digital handset.
Yes you can dumb down the phone (with some) to handle a single call at a
time). Since the phones can handle more than 1 call, have voicemail and
such, it really centers on the reasoning
What version did you upgrade from? Since the phonelogd is compiled for
you and was originally introduced before 4.4, it might be the symlink for
lmnet.so is not pointing to the right place. Did you look for a symlink for
lmnset.so on your system and if so where it points?
On Wed, Apr 11, 2012 at
Thanks for the heads up :)
Fixed the problem with greeting, will soon check if I can change the pincode :)
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Josh Patten
Sent: woensdag 11 april 2012 17:48
To: Discussion list for users of
Exactly. I was pretty sure the answer was no on the busy call handling,
but I wanted to be sure before I started asking Why are we doing
this?. I really need to understand why we are doing what we are doing
and find out if it is really being used. It could be this was the
closest thing they
Perhaps for the time being an option for simply choosing TCP/UDP/both and
the port range would be sufficient. Other options could possibly be added
later.
On Wed, Mar 28, 2012 at 10:35 AM, Douglas Hubler dhub...@ezuce.com wrote:
On Wed, Mar 28, 2012 at 10:27 AM, Tony Graziano
Hi,
I just finished installing SipXecs on a new VM and when I go to the Service
page under Server I got 2 error. My Sip Trunking failed and my SipProxy
failed the configuration test. The more elaborate error are those :
Sip Trunking :
- SipXbridge : Exception caught while running
-
Yes, you didnt set up DNS. DNS is a requirement for the system to run.
Re-run sipxecs-setup-system and select the option to enable the DNS server,
or configure the records yourself:
http://wiki.sipfoundry.org/display/sipXecs/DNS+Concepts+for+sipXecs
On Wed, Apr 11, 2012 at 3:25 PM, Simon Brûlé
Than you for the quick answer. When I instaleed it I said that I had no DNS
in my network and I wanted my SipXecs server to be a DNS so it is install (
i have all the config file) I probably just need to configure them like
they should. When your are saying the record i assume you are talking
IF sipx was told to be the DNS server it should setup the zone file to be
AUTHORITIVE for the zone.
Until another device (softphone or hardware based phone) tries to connect
to it, it should be happy. If it is acting as an AUTHORITIVE DNS SERVER
for its own ZONE (which would be the sipdomain you
25 matches
Mail list logo
