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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Internal SIP Phones
- Thread starter wpetilli
- Start date
Not really. I mean, if you're the army, sure. Do you have intranet websites that people log in to with their LDAP password, or do you offer to authenticate with and/or require identity certs on those too?
If you're using softclients, it's a lot easier. I've set up remote worker SBCs where the SBC requires client certs and trusts the domain controller authority. Then, in One-X you pick the identity cert in the personal trust store.
I think it'd be a lot of overhead. First, because I believe it's a global SM setting to require 2-way TLS everywhere, so you'd need identity certs on all your entities as well as endpoints, and because you'd have to squeeze in any non-Avaya SIP endpoints into using them too. It's easier when you can do it through the SBC and just on the SBC, but barring some compelling security argument you can't win, I wouldn't wish it on you!
If you're using softclients, it's a lot easier. I've set up remote worker SBCs where the SBC requires client certs and trusts the domain controller authority. Then, in One-X you pick the identity cert in the personal trust store.
I think it'd be a lot of overhead. First, because I believe it's a global SM setting to require 2-way TLS everywhere, so you'd need identity certs on all your entities as well as endpoints, and because you'd have to squeeze in any non-Avaya SIP endpoints into using them too. It's easier when you can do it through the SBC and just on the SBC, but barring some compelling security argument you can't win, I wouldn't wish it on you!
- Thread starter
- #3
- Thread starter
- #4
What I'm trying to solve is the issue around cm allowing 3 h.323 registrations/ endpoint. I have call center agents using a standard h.323 deskphone, 1-X Agent client and a call recorder. Because I have 2 recorders the 1-Agent fails or only 1 recorder can be registered onto. I was going to trial converting the deskphone to SIP. Will I be able to have a SIP hardphone with all the call center availability and then the one-x agent client, which I believe is h.323?
Smells like you're spending money on TSAPI or One-X Agent licenses.
You're using DMCC multi registration. The WFO docs say it uses 1 less TSAPI per call than single-step-conference - so, presumably 2 less TSAPI/call if you're using 2 recorders. If you are DMCC Multireg with 2 recorders, then yea... phone+1x+2recorders = 4.
Anyway, pg 13 of this doc spells it out: If nothing's logged in, you can get up to 3. If you have a phone or softphone, you can register 2 more, and if you have a phone and a softphone, then you register 1 more. I guess the answer is either drop either one-x or the physical phone if possible, or switch to single-step for 1 of the recorders.
With AES, you can record by DMCC via service observe or single step conference or multiple registration. With svc-obsv and ssc, your AES registers a range of emulated 4624 phones for recording ports. Via TSAPI it'll either invoke the service observe code from a recording port to an agent's station, or it'll TSAPI a single step conference from an agent's station to a recording port. You could conceivably have one recorder do it each way, but you'd need to rejig a recorder which is usually no treat and it'll cost you TSAPI.
I don't believe you can have one-x agent do shared-control a SIP station period. What you MIGHT be able to do is use One-X in telecommuter mode and route your call to an off-net telephone - which happens to be a different SIP station. It'd be similar to a home agent setup where you put a copper line at their house and One-X registers their H323 station but with talk path to an off-net telephone. The difference there is that One-X Agent for free (the 1xa_SC licenses) are included with elite agents, so you're more than welcome to to have a h323 phone call center use one-x agent to control the desk set. If you want to save on real estate and have them off-net, that costs money and you can then do voip to the client or route to an external number. If you've got spare licenses of those, then you could have another phone be the telecommuting endpoint. I'd caution against using SIP+H323 multiple device access and register a SIP instance of the extension with one-x in telecommuter mode. I don't think One-X would support shared control of a SIP extension who, by happening to not be registered to CM would get you down to 3 H323 registrations. Give it a shot I guess, but good luck getting support for finding a way around licenses!
You're using DMCC multi registration. The WFO docs say it uses 1 less TSAPI per call than single-step-conference - so, presumably 2 less TSAPI/call if you're using 2 recorders. If you are DMCC Multireg with 2 recorders, then yea... phone+1x+2recorders = 4.
Anyway, pg 13 of this doc spells it out: If nothing's logged in, you can get up to 3. If you have a phone or softphone, you can register 2 more, and if you have a phone and a softphone, then you register 1 more. I guess the answer is either drop either one-x or the physical phone if possible, or switch to single-step for 1 of the recorders.
With AES, you can record by DMCC via service observe or single step conference or multiple registration. With svc-obsv and ssc, your AES registers a range of emulated 4624 phones for recording ports. Via TSAPI it'll either invoke the service observe code from a recording port to an agent's station, or it'll TSAPI a single step conference from an agent's station to a recording port. You could conceivably have one recorder do it each way, but you'd need to rejig a recorder which is usually no treat and it'll cost you TSAPI.
I don't believe you can have one-x agent do shared-control a SIP station period. What you MIGHT be able to do is use One-X in telecommuter mode and route your call to an off-net telephone - which happens to be a different SIP station. It'd be similar to a home agent setup where you put a copper line at their house and One-X registers their H323 station but with talk path to an off-net telephone. The difference there is that One-X Agent for free (the 1xa_SC licenses) are included with elite agents, so you're more than welcome to to have a h323 phone call center use one-x agent to control the desk set. If you want to save on real estate and have them off-net, that costs money and you can then do voip to the client or route to an external number. If you've got spare licenses of those, then you could have another phone be the telecommuting endpoint. I'd caution against using SIP+H323 multiple device access and register a SIP instance of the extension with one-x in telecommuter mode. I don't think One-X would support shared control of a SIP extension who, by happening to not be registered to CM would get you down to 3 H323 registrations. Give it a shot I guess, but good luck getting support for finding a way around licenses!
- Thread starter
- #6
All the Call Center Agents use the One-X client for is to get screen pops from our ticketing system, nothing else. They don't use it for phone functionality, but one wouldn't work w/o the other. I'll have a play. Safe to assume there's no SIP version of that client like there was of One-X Comm and Equinox.
From a many year ago promotion I have so many AES licenses that I can probably supply my company 3X over. And sooner rather than later they will be deploying O365 and Teams, which will kiss my RCC environment integration goodbye. Resulting in having several thousand AES licenses for about 50 recorded folks.
From a many year ago promotion I have so many AES licenses that I can probably supply my company 3X over. And sooner rather than later they will be deploying O365 and Teams, which will kiss my RCC environment integration goodbye. Resulting in having several thousand AES licenses for about 50 recorded folks.
So long as they're open TSAPI and not specifically for MS or some other AES app specific integration, then yea, just record some by single step if you can. If you need 2 DMCC for 2 recorders, then switching to single step wont cost you much design-wise.
- Status
Similar threads
- Locked
- Question
- Question
