Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IX Workspace 1

Status
Not open for further replies.
BTI09

BTI09

Technical User
Jul 15, 2009
28
0
0
US
Hello, we are in need of setting up remote users (Teleworkers). IPO R11, Preferred, with Teleworker licensing. Are there any documents that explain how to set this up? I see a lot of Client installation material but this client must interface with something to get to the IPO? Sorry, this is a first for us and any help is appreciated. Thank you!
 
Sort by date Sort by votes
There is a document called "IP Office SIP Extension" but I'm not sure if it covers remote workers.

But it's not too hard...
- set up SIP FQDN and SIP domain
- enter public I in IPO config
- get a matching certificate
- install the root certificate on the client device
- define remote ports for SIP and RTP
- forward the SIP/RTP ports and 443/411
- configure Avaya Spaces or enter the string to the settings file within the app.
- login with extension and password.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
 
Upvote 0 Downvote
I just got this all working after years of trying. We had issues with our firewall and settings in the IP office
You really need a valid SSL cert installed on your Ip office. We tried installing the self signed cert and had all kinds of issues. Iphone would not work
We had all kinds of issues getting the cert to install on older builds of IP office
Make sure your system is fully updated to the latest build of 11 FP4.
Get a multi domain SSL cert. You only two domains. ipoffice.domain.com and a sip domain "domain.com"
You can get multi domain SSL for two years with Commodo for 26 dollars
Now generating that is hard. Follow instructions on this link.
You do not need a SIP url and most SSL sites where you buy them don't support that
You need to add a DNS record for ipoffice.domain name and open up the correct ports on your firewall
I also had to choose Static port block. On Lan voip settings. Otherwise we could call and no speech. I searched many hours looking for answer and never found it
Finally after many attempts it is all working
Oh and setup Avaya Spaces to sync to your IP office and have every user login using email address.
It will auto configure their settings. It is crazy there are no clear instructions anywhere

There are all kinds of instructions but none of them work without doing all these things
 
Upvote 0 Downvote
HI there.

So I am suffering big time trying to get this to work, but with a dreaded and hated ASBCE.

I need a 3rd party cert, which I have created many times over and still cannot get it to work, and the response from Avaya is we do not support 3rd party certs.

The docs they provide are all for using the self signed, I have followed the doc to the letter, but cannot get it to give out the 3rd party cert.

Any suggestions or hail Mary's would be greatly appreciated, this Covid thing has now aged me.

Thanks in advance
 
Upvote 0 Downvote
Thanks for the feedback.

I generate a CSR on the SBC, and send the req file off, I then get a .crt file and a CA cert back from Gandi. Should I maybe not create this on the SBC, and generate it online? Also should I put the IP in the cert?

I have seen a few ports that refer to making the req in openssl, but have had no success with that either.

Thanks for the response
 
Upvote 0 Downvote
So I have for example the below:

CN - phone.mycompany.com
FQDN - phone.mycompany.com
sip Domain - phone.mycompany.com (this is set on the IPO and OneX)
SIP URI - SIP:phone.mycompany.com

So my Subject alternative would be like this? DNS:phone.mycompany.com (Do I put an IP Address in here?)
Would that look correct?
 
Upvote 0 Downvote
So this is what I am going to create:

The Subject alternative format will be: DNS:phone.mycompany.com, IP:123.123.123.123, URI:sip:phone.mycompany.com
The next question is according to the docs, this needs to be on the IPO as well, the reason I say this this is because all my attempts thus far have always passed the self signed cert to the IX client, so if I only get a CA and a crt file back, will it work?

Certificates_-_Avaya_Session_Border_Controller_for_qby3tc.png
 
Upvote 0 Downvote
Cool, will give this 10th version a try and hopefully come right, thanks so much for your time.
 
Upvote 0 Downvote
I then assume the below relates to that step:

3rd party Certificate
NOTE: This is needed only when 3rd party Certificate Authority is used for generating Identity Certificates for SBCE and IP Office
The procedure to generate such certificate is out of scope of this doc, it is customer’s responsibility, but we give an example how to bring it to a format that can be installed on IPO or SBCE.
1. Make sure you have the ID certificate from the 3rd party CA in PEM format.
2. Make sure you have the certificates of all Intermediate CA and the Root CA. These can be requested or even publicly downloaded from the 3rd party CA.
3. Make sure you have the private key
4. Upload all files to a linux box (IPO or SBCE for example) using WinSCP
5. Verify if all files are present:
[root@sipp cert]# ls
idcert.pem IssuingCA.pem key.pem RootCA.pem
6. Verify you have all files for the full trust chain:
[root@sipp cert]# openssl x509 -in idcert.pem -text|grep "Subject:\|Issuer:"
Issuer: C=HU, L=Budapest, O=Avaya, OU=IPO, CN=Issuing CA - Agardi
Subject: C=HU, ST=Hungary, L=Budapest, O=Avaya, OU=IPO, CN=ipo11.example.com
[root@sipp cert]# openssl x509 -in IssuingCA.pem -text|grep "Subject:\|Issuer:"
Issuer: C=HU, L=Budpest, O=Avaya, OU=IPO, CN=Root CA - Agardi
Subject: C=HU, L=Budapest, O=Avaya, OU=IPO, CN=Issuing CA - Agardi
[root@sipp cert]# openssl x509 -in RootCA.pem -text|grep "Subject:\|Issuer:"
Issuer: C=HU, L=Budpest, O=Avaya, OU=IPO, CN=Root CA - Agardi
Subject: C=HU, L=Budpest, O=Avaya, OU=IPO, CN=Root CA - Agardi
7. Verify ID certificate has proper Subject Alternative Name:
[root@sipp cert]# openssl x509 -in idcert.pem -text|grep "Subject Alternative" -A 1
X509v3 Subject Alternative Name:
DNS:ipo11.example.com, DNS:example.com, IP Address:135.124.242.20, IP Address:10.1.1.60
NOTE: Subject Alternative Name field has to contain the followings depending on the product
 SBCE: SIP Domain, SIP registrar FQDN, external IP address of the IP Office
 IPO: SIP Domain, SIP registrar FQDN, external and internal IP address of the IP Office
8. Create a PEM file that contains the whole chain starting from the ID cert till the Root CA:
[root@sipp cert]# cat idcert.pem IssuingCA.pem RootCA.pem > certchain.pem
9. Create a PKCS12 file that contains the whole chain starting from the ID cert till the Root CA and the private key:
[root@sipp cert]# openssl pkcs12 -export -out cert.p12 -in certchain.pem -inkey key.pem
 
Upvote 0 Downvote
I had the IX client working with the remote users VPN back to the local LAN. Now for some reason the IX client is saying:

"No SIP Servers configured" and they can't login to the client?

Any help is much appreciated, thank you!
 
Upvote 0 Downvote
Should I just remove it and copy it in again? Thank you for your help!
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

dsm600rr
  • Locked
  • Question
IX Workplace, SMS?
Replies
0
Views
53
dsm600rr
dsm600rr
ChiefPriest Abrantie
  • Question
Avaya Workspace - No voice capability
Replies
1
Views
71
sizbut
sizbut
teletechman
  • Locked
  • Question
IX Workplace
Replies
1
Views
73
Westi
Westi
NYSTECH
  • Question
IX Workplace and Desk Phones RTP issue 2
Replies
3
Views
132
NYSTECH
NYSTECH
dsm600rr
  • Locked
  • Question
IX Workplace - "Your messages may not be up to date"
Replies
4
Views
130
sizbut
sizbut

Part and Inventory Search

Sponsor

Back
Top