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!
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!
-
Congratulations Mike Lewis 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
- Thread starter BTI09
- Start date
- Thread starter
- #21
Yes, can you receive the 46xxsettings.txt from remote using the same URL the app uses?
If yes, check the settings for SIP server.
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
If yes, check the settings for SIP server.
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
And check if the SBC IP is in the blacklisted IPs
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
- Thread starter
- #24
SET SIP_CONTROLLER_LIST must be set
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
- Thread starter
- #26
proxy1 and proxy2 are no valid public reachable FQDN. You have to set it in LAN - SIP FQDN.
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
And since you use an SBC I guess you will also not want to use unencrypted connection.
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
- Thread starter
- #29
Not using an SBC, all my users have VPN to local LAN? Was just logging into client with
Thank you so much for your help on this. This is new to me so I am not sure what to put in the SIP Domain name or the SIP Registrar FQDN? I assume that whatever we put in here needs to be resolved to the IP Office IP address?
Thank you so much for your help on this. This is new to me so I am not sure what to put in the SIP Domain name or the SIP Registrar FQDN? I assume that whatever we put in here needs to be resolved to the IP Office IP address?
Oh sorry. I didn't figure out that the SBC pictures were from another user.
If they connect via VPN you can just enter the IP address as SIP FQDN and SIP domain.
I can assist you remotely if necessary.
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
If they connect via VPN you can just enter the IP address as SIP FQDN and SIP domain.
I can assist you remotely if necessary.
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
- Thread starter
- #31
You can contact me through my website.
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
- Thread starter
- #33
-
1
- #34
Got it resolved.
Issues were:
- a uploaded 46xxsettings.txt instead of autogenerated
- missing softphone option/Teleworker profile in the user
- we entered a valid SIP domain
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
Issues were:
- a uploaded 46xxsettings.txt instead of autogenerated
- missing softphone option/Teleworker profile in the user
- we entered a valid SIP domain
IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN
JazzWizzard
Technical User
Anybody using Namecheap for their domain and certs and having issues with the SIP domain not being valid in IX Workplace when TLS is activated?
From my experience, they don't support addind URI:sip:example.com in the Subject Alternative Name.
If in the CSR, I have stuff like:
commonName = iposrv.example.com
emailAddress = admin@example.com
[v3_req]
keyUsage = nonRepudiation, digitalSignature, keyEncipherment, dataEncipherment
extendedKeyUsage = serverAuth, clientAuth
subjectAltName = @alt_names
[alt_names]
DNS.1 = iposrv.example.com
DNS.2 = example.com
URI.1 = sip:mtl-lab.com
When they generate the cert, and I open it with Windows, I see the cert as valid, but now the SAN looks like this:
DNS=iposrv.example.com
DNS=
Why does it automatically add front of example.com?! Also don't know why they removed DNS:example.com and URI:sip:example.com, so now IX Workplace complains the SIP domain is invalid.
From my experience, they don't support addind URI:sip:example.com in the Subject Alternative Name.
If in the CSR, I have stuff like:
commonName = iposrv.example.com
emailAddress = admin@example.com
[v3_req]
keyUsage = nonRepudiation, digitalSignature, keyEncipherment, dataEncipherment
extendedKeyUsage = serverAuth, clientAuth
subjectAltName = @alt_names
[alt_names]
DNS.1 = iposrv.example.com
DNS.2 = example.com
URI.1 = sip:mtl-lab.com
When they generate the cert, and I open it with Windows, I see the cert as valid, but now the SAN looks like this:
DNS=iposrv.example.com
DNS=
Why does it automatically add front of example.com?! Also don't know why they removed DNS:example.com and URI:sip:example.com, so now IX Workplace complains the SIP domain is invalid.
phonemanager
Programmer
Hello,
We have a client what is using the APP and it works good on cellular data, however it doesn't work on WIFI at all. I know on the older versions you could force it to use cellular but I don't see any choice for that on the new version. Any help will be greatly appreciated
We have a client what is using the APP and it works good on cellular data, however it doesn't work on WIFI at all. I know on the older versions you could force it to use cellular but I don't see any choice for that on the new version. Any help will be greatly appreciated
You need a multidomain cert. You have to have example.com and iposrv.example.com SSL certs usually add the even on a single name cert
JazzWizzard
Technical User
I'm trying to create one with Let's Encrypt, but it's a total pain in the ass.
For the DNS-01 validation, you gotta create a TXT record on your DNS like _acme-challenge.example.com with some gibberish string of caracters like dj38fnskkvwmdqwidqndnwuindmmgfe039i3_2ee in the content.
Simple on the surface, yet I don't know what I'm doing wrong but the record is clearly not showing up and because of this, the validation is not working. I even changed nameservers to Cloudflare, thinking this may help, but nope.
All I want to do is generate a wildcard cert to run some tests....
For the DNS-01 validation, you gotta create a TXT record on your DNS like _acme-challenge.example.com with some gibberish string of caracters like dj38fnskkvwmdqwidqndnwuindmmgfe039i3_2ee in the content.
Simple on the surface, yet I don't know what I'm doing wrong but the record is clearly not showing up and because of this, the validation is not working. I even changed nameservers to Cloudflare, thinking this may help, but nope.
All I want to do is generate a wildcard cert to run some tests....
- Status