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!
Avaya Spaces Calling 1
- Thread starter AgilityMM
- Start date
-
1
- #2
Travis Harper
Technical User
Yes, I have it working. Very simple.
Log into Avaya Spaces as Admin.
Click on your Company
Click on Domain
Apps, Add App.
Scroll down and select Avaya Spaces Calling
Enter the following JSON Code.
{
"IP_Office_Server_Profile":[
{
"Name":"Lab",
"Address":"your_IPO_SIP_DOMAIN",
"AccountToken":false,
"AttendedTransfer":true,
" MergeCall":true,
" IpoSearch":true
}
]
}
Then save.
Download the Avaya Spaces Calling Extension and login with your Avaya Spaces Credentials.
BOOM! You have a web phone.
Travis
Log into Avaya Spaces as Admin.
Click on your Company
Click on Domain
Apps, Add App.
Scroll down and select Avaya Spaces Calling
Enter the following JSON Code.
{
"IP_Office_Server_Profile":[
{
"Name":"Lab",
"Address":"your_IPO_SIP_DOMAIN",
"AccountToken":false,
"AttendedTransfer":true,
" MergeCall":true,
" IpoSearch":true
}
]
}
Then save.
Download the Avaya Spaces Calling Extension and login with your Avaya Spaces Credentials.
BOOM! You have a web phone.
Travis
- Thread starter
- #3
Travis Harper
Technical User
AgilityMM - I do not have an SBCE in my solutions.
However, if you can register Workplace through your SBCE, then this should be no different, unless you have your SBCE restricting devices by type. If that is the case, check the SBCE logs and see what the "identifier" is for Avaya Calling for Spaces, and include that in your white/accept list.
Did your JSON validate without errors?
When you launched the plugin, did it ask for you to login?
If yes, then were you asked to enter your extension and password?
At what point did the failure occur?
Travis
However, if you can register Workplace through your SBCE, then this should be no different, unless you have your SBCE restricting devices by type. If that is the case, check the SBCE logs and see what the "identifier" is for Avaya Calling for Spaces, and include that in your white/accept list.
Did your JSON validate without errors?
When you launched the plugin, did it ask for you to login?
If yes, then were you asked to enter your extension and password?
At what point did the failure occur?
Travis
Travis Harper
Technical User
AgilityMM - Also you need to have a business or power spaces account for the user that wants to use the plugin.
Does not work with the free spaces account.
Does not work with the free spaces account.
- Thread starter
- #6
Travis Harper
Technical User
Do you have the WebRTC gateway configured in IP Office?
- Thread starter
- #8
Travis Harper
Technical User
Can you direct message me in Avaya Spaces?
travis@tharper.ca
travis@tharper.ca
- Thread starter
- #10
Travis Harper
Technical User
I don't think you need that port open (3478).
You need to have WebRTC enabled not the IP Office.
I was already using Avaya Communicator for Web previously, so my migration to Avaya Calling for Spaces was very simple.
WebRTC configuration is critical.
You need to have WebRTC enabled not the IP Office.
I was already using Avaya Communicator for Web previously, so my migration to Avaya Calling for Spaces was very simple.
WebRTC configuration is critical.
Travis Harper
Technical User
My Spaces account for direct message is travis@tharper.ca , but I can not receive emails on that address.
Travis
Travis
- Thread starter
- #13
Travis Harper
Technical User
Send me your email.
I wil invite you.
I wil invite you.
Travis Harper
Technical User
Travis Harper
Technical User
Join my spaces room.
It's easier, and I have documentation I can share.
It's easier, and I have documentation I can share.
- Status
Similar threads