Search results for query: *

Yes, give me some time to make screenshots.

I made some modifications.

Hi Igman1969, Yes, I get it working 100%. You need just to configure SBCE for the primary IPO like a standalone IPO used for remote worker. Then, you do the same config for the second IPO. You need to create again everything on SBCE: - Another private and public IP - Another, signaling/media...

@Sizbut: good luck for you too.

@Sizbut: I suggest that your IPO release is not the latest one. VMPro failover is an issue on the latest release, I invite you to test on your own lab. I found another issue: when you reboot IPO, DNS IP address is changed on the first IP address enterred on the system at the first install. This...

This note is important !! ------ For Complete resiliency of voicemail (example if the primary server has an outage or network outage) then you require a) For solutions using IP Phones registered with the Primary server: at least one IP Phone must be located at Secondary server location and...

Yes synchronization is maked fine and tested. My modules created on VMPro (Prmiary) are replicated on the secondary. But, VMPro on the secondary still ask to manually activate the backup vmpro.

I found the issue but it's strange on the SP2: I need to activate manually the VMPro backup server (see screenshot). When I activate the backup VMPro, the secondary server change status from unknown to centralized and calls to VMPro works again !

Here is the trace with default settings on Monitor: ********** Warning: Logging to Screen Started ********** 12:19:38 436997mS SIP Rx: TLS 10.219.6.93:44225 -> 10.219.6.91:5061 INVITE sip:*17@mydomain.com SIP/2.0 From...

It doesn't work for local users too.

Hi team, I deployed 2 IPO Select with the latest release (SP2) (primary and secondary) and an SBCE cluster used only for remote workers. All is work fine for my remote workers. But, when the primary IPO fails, remote worker (registered correctly on the secondary IPO) cannot call the voicemail...

Presence works for me with my configuration. The issue is when I make tracesbc on HTTP (active traces), and I connect a Workplace, presence don't work. So I exit HTTP traces, I disconnect/reconnect the IX Workplace user and the presnece work again ! Strange that the traces block presence flow...

Using unsecure ports like 80 is dangerous from Internet ! Equinox worked fine for me with reverse proxy on 443 or 411 (preferred ports). It's a simple bug like many others on Avaya systems !

Of course on the local network it's working fine ! It's IX Workplace or SBCE 8.0 bug !

18:31:33 6596964mS HTTP: 10.176.0.240(42739)-(411) HTTPSession(Secure) (Total = 2) 18:31:33 6596964mS HTTP: 10.176.0.240(42739)-(411) HTTPSession: Operational 18:31:33 6596964mS HTTP: 10.176.0.240(42739)-(411) HTTPSession: TLSOperational Resumed=true 18:31:33 6596965mS HTTP...

Presence worked for 3 seconds and when I disconnect/reconnect, presence don't works

Same issue, 401 response from IPO

Hi team, I have an issue with presence and contact search for IX Workplace remote user registered on SBCE. Traces show that tpkt/mtcti get 401: 443 traffic is allowed on my firewall. And here is my Reverse-Proxy profile used: And my reverse proxy relay service: I authorize only...

TLS Client Profile must be NONE on my configuration, because my SIP Servers are (Call Server type) and DNS Query type is forced on NONE/A when you select Call Server Information from Avaya SBCE documentation : But I confirm that Ihave an issue on my certificate and TLS profiles...

Public certification authority don't provide certificates with IP addresses on the SAN.