Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007454opensim[GRID] Other Servicepublic2015-02-25 10:342015-02-27 09:05
Reportersteeno 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0007454: Vivox Voice "Ghosting" on identical regions
DescriptionI've duplicated a grid and changed its name on the duplicate, however both grids have a few regions that are identical in name, UUID, location, etc.

In these regions, you're able to use the Vivox spatially-aware voice service as if everyone was in the same region on the same grid. So one avatar on the original grid can stand 'in the same place' on the other grid and an avatar on the other grid can hear them talk and vice versa.

How do I indicate to Vivox that these are separate grids and not to communicate voice as if they are the same location? Is there an additional setting I need to change on the new grid to identify it as a different location? I've tried changing the HTTP listener ports and restarting the simulator without success.
Steps To ReproduceCreate a grid, clone its files and database, redirect database pointers to new database, rename new grid in config files, place user in same region in each grid and use Vivox voice service.
Tagsvivox, voice
Git Revision or version number
Run Mode Grid (1 Region per Sim)
Physics EngineBulletSim
Script Engine
EnvironmentMono / Linux64
Mono Version3.2
ViewerFirestorm
Attached Files

- Relationships

-  Notes
(0027600)
aiaustin (developer)
2015-02-25 11:50
edited on: 2015-02-25 11:54

Surely you should not be using the same region UUID in two instances? And that is what Vivox is using to see them as the same source for voice I think.

Region name and xloc,yloc can be same on different grids of course.

(0027601)
steeno (reporter)
2015-02-25 11:53

The regions have the same UUID as they're being copied back and forth as a development environment and production environment to improve stability. In this setup the development region will be used to build and script actively whereas the production region will have stable objects and scripting copied to it.
(0027602)
aiaustin (developer)
2015-02-25 11:56
edited on: 2015-02-25 11:57

Try gettng two different Vivox accounts for the test and deployment grids then maybe steeno?

(0027626)
steeno (reporter)
2015-02-27 09:05
edited on: 2015-02-27 09:14

We got a second account and the issue is persisting. We asked Vivox Support for additional support two days ago and are waiting for their response.

Any other ideas?


- Issue History
Date Modified Username Field Change
2015-02-25 10:34 steeno New Issue
2015-02-25 10:35 steeno Tag Attached: voice
2015-02-25 10:35 steeno Tag Attached: vivox
2015-02-25 11:50 aiaustin Note Added: 0027600
2015-02-25 11:51 aiaustin Note Edited: 0027600 View Revisions
2015-02-25 11:53 aiaustin Note Edited: 0027600 View Revisions
2015-02-25 11:53 aiaustin Note Edited: 0027600 View Revisions
2015-02-25 11:53 steeno Note Added: 0027601
2015-02-25 11:54 aiaustin Note Edited: 0027600 View Revisions
2015-02-25 11:56 aiaustin Note Added: 0027602
2015-02-25 11:57 aiaustin Note Edited: 0027602 View Revisions
2015-02-27 09:05 steeno Note Added: 0027626
2015-02-27 09:14 steeno Note Edited: 0027626 View Revisions


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker