Custom settings file for IX Workplace

[JazzWizzard]

Hi everyone,

We're trying to make IX Workplace work with an ASBCE and a third party certificate so the remote workers can acces the settings files using HTTPS. We have a lot of issues with this, mostly with Avaya's documentation being vague and subpar, as usual. Frustrating experience...

Long story short...

We have to modify the 46XXSETTINGS file to get TLSSRVID to 0 instead of 1. We already use the 46SPECIALS file for this purpose on J179 phones, but IX Workplace doesn't read that file and I'm trying to avoid modifying the 46SETTINGS for this. I prefer having it auto-generate.

So basically, I wanted to make a settings file exclusively for IX Workplace, say IXSETTINGS.txt, but it's not exactly clear what stuff needs to be in there to make it work.

Any of you guys made such a file and know what to include in it?

Thanks a lot!

 

[derfloh]

Copy the autogenerated 46xxsettings.txt and save it as ixsettings.txt. Then modify what you need and let the IX Workplace client load that new file.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[JazzWizzard]

Thanks derfloh!

That's what I was planning on doing, but wondered if all the other stuff that's on there for phones would create conflict/issues.

 

[derfloh]

No. It doesn't create any issues if you only use the autogenerated file.

You can also add FNE settings in that file and dial plan rules.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[JazzWizzard]

What is FNE settings?

 

[derfloh]

The opposite side of mobile twinning. Dialing in to get dial tone. Then dial out with your office number. No data connection needed, only voice.

Good for bad data coverage or during car driving.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[JazzWizzard]

Thanks derfloh!

 

[jamie77]

There should be no need for what you are doing for ASBCE and IX. We have many using TLS for J1XX, Communicator and IX using 3rd Party Certs without an issue.

From an Avaya Slide: Certificate content checking is not performed when TLSSRVRID = 0 in the settings file (not recommended)

Get the cert right and you are golden. How the cert needs to be built and loaded in the ASBCE is different between SBC R7 and R8. Avaya get very confused with this having raised it to Tier IV a few times.

Also if the firewall (if there is one in front) isn't sending the right ports etc can cause confusing results.

What are the problems you face?

Is your 3rd Party cert a UCC/Multi SAN with both SIP FQDN and SIP Domain listed?

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[telecomtekperson]

Did i miss this in documentation somewhere?

I dont see any reference to IXSettings.txt...

 

[derfloh]

You can create your own file with individual settings. Then point the client to this file.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[JazzWizzard]

@jamie77: we redid the cert with a wildcard one and it's working now.

By the way, is there somethign specific to configure in the SBC for video calls in IX Worplace?