Trevor,
Found out what's causing this. Some freeswitch integration files turned out to
be missing. Fixing this on the next RPM of openacd.
Jan Vincent Liwanag
jvliwa...@ezuce.com
On Nov 29, 2012, at 12:19 AM, Alan Worstell wrote:
> On 11/28/12 7:44 AM, Melcon Moraes wrote:
>> Do you really
At last, I am now able to turn the problem incoming call audio problem on and
off repeatably and reliably: it has something to do with XMPP. Below are the
repeatable steps. Does anyone have an idea what I should do with this... put in
a bug report? I don't want to do that without someone's advic
The MoH issue is related to Bria: I've now figured out that the MoH issue only
occurs happens with the Mac OS X Bria client. Same for the hold/resume issue -
works properly on Windows, can't resume on Mac. Both exhibit the main problem
of no audio in/out for external received calls.
What I fin
Another day and yet a bit closer: the Polycom SoundPoint I managed to provision
for this server has no problems whatsoever. MoH, inbound, outbound - all are no
problem!
So I think I can only conclude that it is a Bria-specific problem. That's a
relief - I think I now can conclude the server I've
That all looks good Joegen:
Pretty much the same from all three sites I'm testing from.
From: Joegen Baclor [mailto:jbac...@ezuce.com]
Sent: November-28-12 1:10 AM
To: Nicholas Drayer
Cc: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipx 4.6 inbound ivr-->extension alwa
In 4.2-4.4 you should use the same hostname/IP/sip domain before doing your
restore.
Did you take those steps?
On Nov 28, 2012 7:31 AM, "Daniel Peinado" wrote:
> Hello,
>
> I have installed the sipxecs 4.2.1. My setup has 1 master Sipxecs and one
> slave. I try to restore the backup and I do the
Daniel,
Are you trying to do 4.2.1 in a virtual?
If so, here's what I'd do.
Get 4.2.1 installed in one virt with same IP and same host name as the
master.
Restore configuration and voicemail.
In the GUI, remove the second server.
Send profiles.
Now, do an in-place upgrade of a single server syst
Even when "other phones" are from an ITSP call coming through the
sipXbridge setup to play MoH?
-
MM
On Wed, Nov 28, 2012 at 7:07 AM, Kumaran <
thiru.venkateshwa...@ttplservices.com> wrote:
> Bria won't support MoH..If Bria put on Hold other phones won't hear MoH..
>
> Regards,
> Kumaran T
>
>
since your call forwarding for is set to 20 seconds it should pull it
back and move to .
try setting the initial forward on to 40 seconds and see what happens.
you may run into call timeout issues with ringing this long...
mike
On Wed, Nov 28, 2012 at 6:57 AM, Melcon Moraes wrot
On 11/28/12 7:44 AM, Melcon Moraes wrote:
> Do you really have literally {SERVERNAME} on the output or you just
> "masked" the server name? You're supposed to have your FQDN in place.
>
> -
> MM
>
Hello,
This is just the masked FQDN of our server.
Regards,
Alan Worstell
A1 Networks - Systems Adm
Do you really have literally {SERVERNAME} on the output or you just
"masked" the server name? You're supposed to have your FQDN in place.
-
MM
On Wed, Nov 28, 2012 at 1:08 PM, Trevor L Benson
wrote:
> Jan,
>
> Response Inline:
>
>
>
>
> On Nov 28, 2012, at 2:39 AM, Jan Vincent Liwanag
> wrot
Jan,
Response Inline:
On Nov 28, 2012, at 2:39 AM, Jan Vincent Liwanag wrote:
> Hi Trevor,
>
> See inline
>
> Jan Vincent Liwanag
> jvliwa...@ezuce.com
>
>
>
> On Nov 28, 2012, at 3:44 AM, Trevor L Benson wrote:
>
>> Hello,
>>
>> We have been in the process of testing openUC 4.6 wi
Not sure if that helps, but this option has been "always" present, even
back to the 3.10.X.
-
MM
On Wed, Nov 28, 2012 at 8:20 AM, Joegen Baclor wrote:
> look for SIP_REGISTRAR.MWI.UA.CISCO : ^(CSCO|Cisco) in
> /etc/sipxpbx/sipxregistrar/registrar-config.vm. Change it to
> SIP_REGISTRAR.MWI.U
Hello,
I have installed the sipxecs 4.2.1. My setup has 1 master Sipxecs and one
slave. I try to restore the backup and I do the next.
1) install sipxecs (1 master) 4.2.1 and yum update
2) install sipxecs (2 slave) 4.2.1 and yum update
3) add slave server in sipxecs interface and send profiles.
Have you tried to wait for more than 20 seconds on and see if that
goes to ? I believe that is what is going to happen.
-
MM
On Wed, Nov 28, 2012 at 9:11 AM, Elwin Formsma wrote:
> Hi,
>
> I've got a question about Call forwarding in SipXecs. The following
> situation occurs:
>
> User
It's working now. Thanks.
openacd-0.9.5-741.gd7f6.x86_64
sipxopenacd-4.6.0-890.ge4ca9.x86_64
are the ones I have installed yesterday.
-
MM
On Tue, Nov 27, 2012 at 10:23 AM, George Niculae wrote:
> On Tue, Nov 27, 2012 at 6:54 AM, Kumaran <
> thiru.venkateshwa...@ttplservices.com> wrote:
>
>>
Hi,
I've got a question about Call forwarding in SipXecs. The following situation
occurs:
User has the following call forwardings
1. Call for 20 seconds
2. Call for 20 seconds
3. Call for 20 seconds
4. Go to voicemail
User has the following call forwardings:
1. Call 222
Hi Trevor,
See inline
Jan Vincent Liwanag
jvliwa...@ezuce.com
On Nov 28, 2012, at 3:44 AM, Trevor L Benson wrote:
> Hello,
>
> We have been in the process of testing openUC 4.6 with plans to migrate off
> of our 4.4. The last functional test for internal use was migrating our ACD
> to
look for SIP_REGISTRAR.MWI.UA.CISCO : ^(CSCO|Cisco) in
/etc/sipxpbx/sipxregistrar/registrar-config.vm. Change it to
SIP_REGISTRAR.MWI.UA.CISCO : ^(DISABLED). Resend profiles and see if
you still get the error. I'm not sure if Cisco now supports solicited
notify. This config change disables
also below are a summary of wireshark traces connnected to
mirrored ports of both live and test servers.
Live server v4.2.1 - Good MWI trace - message left, light
on
6129 - 10.203.105.50 > 161.2.128.24 - Request: INVITE
6131 - 161.2.128.24 > 10.203.105.50 - Status: 100 Trying
6153 - 161.2.128.2
Hi,
sipstatus file attached...look at the time around
06:51.805014
Cheers,
Paul
sipstatus_test.log
Description: Binary data
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Without the logs, it's any one's guess. Debug elvel log of from sip
status would be nice.
On 11/28/2012 05:51 PM, Paul Sander wrote:
>
> I am upgrading our voicemail to v4.4 and everything is ok
> apart from no MWI. I see when debugging and error message
> within sipstatus that says '481 Subscr
I am upgrading our voicemail to v4.4 and everything is ok
apart from no MWI. I see when debugging and error message
within sipstatus that says '481 Subscription doesn't exist.'
The current server with v4.2.1 is fine with no issues.
We are only using voice mail with a SIP trunk into Cisco
Call
I was wrong. It's no sipXnonat that you should be looking for but to
make sure your registrations has x-sipX-privcontact. Can you verify
this for all your NATed registrations?
On 11/28/2012 04:35 PM, Nicholas Drayer wrote:
Thank you Joegen,
Yes, it's registered and sipXnonat is not visible o
Bria won't support MoH..If Bria put on Hold other phones won't hear MoH..
Regards,
Kumaran T
On 11/28/2012 2:29 PM, Joegen Baclor wrote:
I'm not sure if Bria supports MoH. Can someone verify this?
On 11/28/2012 04:35 PM, Nicholas Drayer wrote:
Thank you Joegen,
Yes, it's registered and sipX
I'm not sure if Bria supports MoH. Can someone verify this?
On 11/28/2012 04:35 PM, Nicholas Drayer wrote:
Thank you Joegen,
Yes, it's registered and sipXnonat is not visible on the registration
(on the web portal). And yes, I put the Bria logging on and it
receives keep-alive (I think I'm a
Thank you Joegen,
Yes, it's registered and sipXnonat is not visible on the registration (on the
web portal). And yes, I put the Bria logging on and it receives keep-alive (I
think I'm able to make out that is says every 30 seconds). I ran "tcpdump -v
host sipx.mydomain.com", which is showing th
27 matches
Mail list logo
