VOICE CHAT NOT WORKING

[Rothgar]

DJWolf5 wrote:

I just feel that a central issue is being ignored.

From the moment I log onto the game my voice chat service is trying to establish a connection.  Correct?  So whether I am swanning around the guild hall, on a raid, doing tradeskilling, changing my display resolution, or whatever, it is irrellevant to my problem.  I can accept that there is a pause between each voice service connection attempt but whether the error is in my modem, my sound card, my firewall or wherever, something is blocking that connectivity and that this would be happening continuously.  True?

So what's with 'Options'?  Why are most of us experiencing a freeze and unresponsiveness when we go near our voice chat selections?

If this lag is caused by Voiceservice.exe trying to get a connection why is it that I don't walk one pace, lag, one pace, lag, one pace, lag, etc?  My modem isn't listed in Options, nor is my ISP or anything to do with connectivity.  IF these were the problems then the symptoms they would cause would be game wide and show up from the moment I logged on.

Logically, the absense of voice is the result of the problem and the source of the problem is a conflict in Options.

The lag you're getting when you open options most likely has something to do with the voice service trying to query windows for your device information.  This is why it wouldnt happen any other time.

[Greyform]

Heya Rothgar,

If you could. could you let us in on why a lot of these problem happened after the last GU (my headset issue for example). I have a few guildmates who are getting pretty frustrated with the problem. I think if you could just outline where you're at troubleshooting this and why rolling back to before the last GU is not something you want to do.

It would help as far as knowing there is a plan in place. Seeing someone logout because they are unable to join chat is a bummer. I know you don't want to put a timetable on a fix but some idea as to why we can't go back to before the last GU would be helpful.

Thanks

[Gaelwyn]

Rothgar wrote:

DJWolf5 wrote:

I just feel that a central issue is being ignored.

From the moment I log onto the game my voice chat service is trying to establish a connection.  Correct?  So whether I am swanning around the guild hall, on a raid, doing tradeskilling, changing my display resolution, or whatever, it is irrellevant to my problem.  I can accept that there is a pause between each voice service connection attempt but whether the error is in my modem, my sound card, my firewall or wherever, something is blocking that connectivity and that this would be happening continuously.  True?

So what's with 'Options'?  Why are most of us experiencing a freeze and unresponsiveness when we go near our voice chat selections?

If this lag is caused by Voiceservice.exe trying to get a connection why is it that I don't walk one pace, lag, one pace, lag, one pace, lag, etc?  My modem isn't listed in Options, nor is my ISP or anything to do with connectivity.  IF these were the problems then the symptoms they would cause would be game wide and show up from the moment I logged on.

Logically, the absense of voice is the result of the problem and the source of the problem is a conflict in Options.

The lag you're getting when you open options most likely has something to do with the voice service trying to query windows for your device information.  This is why it wouldnt happen any other time.

Rothgar can you answer me this then.  Why do I "not" get the lag in Character Select, but I do when attempting to open options once I am further into the game and try to access it from that point?

[bigsigh]

Greyform wrote:

Heya Rothgar,

If you could. could you let us in on why a lot of these problem happened after the last GU (my headset issue for example). I have a few guildmates who are getting pretty frustrated with the problem. I think if you could just outline where you're at troubleshooting this and why rolling back to before the last GU is not something you want to do.

It would help as far as knowing there is a plan in place. Seeing someone logout because they are unable to join chat is a bummer. I know you don't want to put a timetable on a fix but some idea as to why we can't go back to before the last GU would be helpful.

Thanks

THIS is the central issue, the crux of the biscuit so to speak. I have asked this question several times in this thread and it has never been answered. SOE CAN fix this laughable situation, yet, for whatever reason, choose not to. I can only ask, WHY?

It is obvious they cannot fix this issue, so with that in mind, why doesn't someone make a decision and roll the [Removed for Content] thing back so we can get on with it? I can't help but feel a sense of deva vu here... cough...fighter revamp. Wonder how much that episode cost?

Please stop dancing around the issue Rothgar, tell us exactly why almost one MONTH after the disaster that was GU 52, SOE have decided that is preferable to have a broken voice system, that is upsetting what, 10%, 15% maybe of its player base to rolling back to a working pre-GU 52 version. I believe the last excuse was that it 'is not easy,' apparently losing players and accounts and whole guilds even is preferable? I think Sony have lost ANY shred of credibility or goodwill that they may have had.

Weirdly enough, voice worked for me for most of my gaming day yesterday. It survived half a dozen alt swaps. I foolishly felt that the fix was in. Of course, then it just stopped working again. bah The CANCEL button is getting closer by the day. Why the hell are we PAYING to be beta testers for software that is dodgy at best and pathetic at worst? Isn't that what the test server is for? Oh wait, it was tested on test and it failed the test, yet some clown gave the go ahead to release it, no doubt to stick to some artificial deadline. I am sick of paying for this buggy piece of junk. I am sick of the excuses. I am sick of TSR asking me if my mic is connected. I am sick of Rothgar not answering the real questions. What will it take for SOE to realise that this HAS to be rolled back NOW??

[Dreyco]

They can't just "roll it back" because they changed the way voice chat worked entirely.  Instead of being integrated into the game code itself, it is now a separate program that runs in the background, so Station launcher and the game itself can continue to manage your voice chat sessions even when you log off, or while you're patching.  This is why it's different, and that's why it's still buggy.  A rollback would mean going back and re-writing more code for ALL the game clients that now use the new Vivox voice service, meaning more work than it would probably take to just fix it.

That separate program, however, is not managed by SOE.  It is not coded by SOE.  It is not handled by SOE.  It is handled by Vivox.  SOE provides them information.  Vivox tries to fix it.  It won't be perfect.  But i'm sure they're trying.

Rothgar is trying his best to help here.  Threatening to cancel and insulting the man who is doing his best to help out here is hardly conducive to it getting fixed.  The more bug reports you file, the more information you give, that is above and beyond "OMG IT DOESN'T WORK" brings it closer to being resolved.  I would perhaps advise trying this instead of flaming a hard working developer over a service that SOE is paying out of pocket for you to enjoy.  It's free to us.  If it doesn't work, there are alternatives.  You just have to pay for them.  I'm thrilled that I get the option of chatting with my friends at no cost, buggy or not.  (Even though, admittedly, for me, it works fine right now, with few exceptions, but nothing devastating).

[DJWolf5]

The problem is that the majority of us here are way out of our depths.  I have no idea of what a DNS lookup tool is and I'm a little annoyed that I'm expected to.  I read MiKkahl's post relating comments from D-Link and wonder if what they are saying relates to every server on the path.  It's not just my modem, Vivox and my ISP.

This is a trace I was instructed to do.  I live in Perth West Australia, my ISP is IINET and my modem at 1ms is 10.1.1.1.  At number 4 the signal leaves Perth and goes to Sydney.  At number 7 (the second one at it reaches the USA where it bounces around for a while.

Tracing route to eqworld-126.everquest.com [199.108.3.101]over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  10.1.1.1   2    16 ms    16 ms    16 ms  nexthop.wa.ii.net [203.59.14.16]   3    17 ms    17 ms    17 ms  gi2-3.per-qv1-bdr2.ii.net [203.215.4.30]   4    75 ms    75 ms    76 ms  gi0-8-1-0.syd-mas-core1.iinet.net.au [203.215.20.64]   5    77 ms    76 ms    79 ms  static.net.reach.com [134.159.160.57]   6    85 ms    75 ms    74 ms  unknown.net.reach.com [202.84.220.149]   7   224 ms   223 ms   222 ms  i-2-1-1.wil-core02.bx.reach.com [202.84.140.38]   8   225 ms   225 ms   234 ms  i-1-1.tlot03.bi.reach.com [202.84.251.234]   9   258 ms   258 ms   258 ms  ge-6-21.car3.LosAngeles1.Level3.net [4.68.111.137]  10   255 ms   267 ms   254 ms  ae-61-60.ebr1.LosAngeles1.Level3.net [4.69.144.50]  11   257 ms   257 ms   257 ms  ge-6-2-0-99.bbr1.LosAngeles1.Level3.net [4.68.20.193]  12   261 ms   262 ms   261 ms  as-1-0.mp1.SanDiego1.Level3.net [64.159.1.29]  13   263 ms   261 ms   262 ms  so-10-0.hsa1.SanDiego1.Level3.net [4.68.113.38]  14   258 ms   258 ms   258 ms  vl861.sdtermswitch-1.sonyonline.net [63.215.251.130]  15   258 ms   260 ms   259 ms  vl831.sdkollsw-1.sonyonline.net [64.37.144.82]  16   264 ms   261 ms   261 ms  eqworld-126.everquest.com [199.108.3.101] Trace complete.Tracing route to eqworld-148.everquest.com [199.108.3.213]over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  10.1.1.1   2    16 ms    18 ms    16 ms  nexthop.wa.ii.net [203.59.14.16]   3    17 ms    17 ms    16 ms  gi2-3.per-qv1-bdr1.ii.net [203.215.4.28]   4    71 ms    72 ms    71 ms  203.215.20.6   5    74 ms    74 ms    75 ms  te0-6-1-0.syd-mas-core1.iinet.net.au [203.215.20.149]   6    74 ms    74 ms    74 ms  static.net.reach.com [134.159.160.57]   7    72 ms    71 ms    72 ms  unknown.net.reach.com [202.84.220.149]   8   221 ms   221 ms   221 ms  i-2-0-1.wil-core02.bx.reach.com [202.84.144.101]   9   222 ms   222 ms   368 ms  i-1-1.tlot03.bi.reach.com [202.84.251.234]  10   255 ms   256 ms   255 ms  ge-6-20.car3.LosAngeles1.Level3.net [4.68.111.133]  11   261 ms   255 ms   254 ms  ae-71-70.ebr1.LosAngeles1.Level3.net [4.69.144.114]  12   254 ms   254 ms   254 ms  ge-6-2-0-99.bbr1.LosAngeles1.Level3.net [4.68.20.193]  13   260 ms   318 ms   258 ms  as-1-0.mp1.SanDiego1.Level3.net [64.159.1.29]  14   259 ms   258 ms   260 ms  so-10-0.hsa1.SanDiego1.Level3.net [4.68.113.38]  15   257 ms   257 ms   256 ms  vl861.sdtermswitch-1.sonyonline.net [63.215.251.130]  16   256 ms   260 ms   256 ms  vl831.sdkollsw-1.sonyonline.net [64.37.144.82]  17   258 ms   256 ms   256 ms  eqworld-148.everquest.com [199.108.3.213] Trace complete.

Do each of these 16 or 17 servers send whatever is sent to them regardless or do they each filter would be hacker attacks or non-regulation packet sizes?

[Seiji-01]

My problem is the same as it ever was.  And it's curious, and very, very frustrating.

70% of the time, the voice service offered through the Station Launcher WORKS.  I can log onto my guild's voice chat from there, and chat just fine.  However, the rest of the time I get the EXACT SAME PROBLEM as I do when I try to run the voice chat service from IN-game:

When in-game, for all intents and purposes, voice chat is working.  I can log into it in the sense that I can see my available channels, join them, see who's in them, and broadcast.  People CAN HEAR ME when I'm in the various voice channels (Group, Guild, Raid).  But I CAN NOT HEAR THEM.  And it's curious in this way: for the first 3 seconds, I can hear everything fine.  It sounds great, and the quality is crystal clear.  However, after those initial few seconds, everything just gets quiet and stays that way.  That's it.  I have to leave/re-join to hear anything again, and it's a repeat of what happened before.  SOMETIMES, EVENTUALLY, consistently leaving/re-joining will have the voice chat work properly, and I can hear and chat just fine.  No problems.  But that's 1% of the time.

It is NOT my sound card.  Drivers are up to date, and other voice services work on top of the one offered by Vivox (when it chooses to work that 1% of the time).  When voices stop broadcasting after the initial few seconds, I do NOT see the speech-bubble when they do broadcast (and I've tested it, not a fluke of any kind).  My router is up-to-date.  All required ports are open.  Everything is allowed through what flimsy firewall I do have.  Finally, voice chat WAS WORKING BEFORE LU52!

What, if anything, can I do?!  Because of this, I can't raid.  I CAN'T.  I can barely group.  People don't want someone they can't reliably communicate things to.  Just tonight, I ruined an instance because I couldn't hear the commincation about NOT looting an item.  I looted it.  Then I crashed when trying to get voice to work, and when I logged back in, that item (which was required for the last boss) was gone from my inventory.  The crash WAS DUE TO TRYING TO GET VOICE TO WORK.

Please, SOE, get this fixed and working properly again.  And PLEASE, give us SOME kind of reimbursement!  WEEKS of group play have been RUINED for me!  I've been forced to solo practically ALL of my post-50 content because no one can play with me reliably.  This whole situation is totally disheartening, and every time I see a "fix" prepared only to see that it's done NOTHING for me and many others...

Ugh.

[Rothgar]

Greyform wrote:

Heya Rothgar,

If you could. could you let us in on why a lot of these problem happened after the last GU (my headset issue for example). I have a few guildmates who are getting pretty frustrated with the problem. I think if you could just outline where you're at troubleshooting this and why rolling back to before the last GU is not something you want to do.

It would help as far as knowing there is a plan in place. Seeing someone logout because they are unable to join chat is a bummer. I know you don't want to put a timetable on a fix but some idea as to why we can't go back to before the last GU would be helpful.

Thanks

I'm pretty sure I mentioned it in an earlier post, but basically the changes to our voice system were done as a company-wide initiative that had to be coordinated with other game teams like EQ and SWG as well as the team thats working on the Station Launcher.  The deadlines and timetables were not something we could really control at the team level.  Yes, we learned some things from this experience.  Hopefully the remaining issues will be solved very quickly so voice chat can return to the quality and reliability that it was before the game update.

[PhyroEQ]

I'm also experiencing the same problem. Jumped through all the hoops for Sony, did the whole delete files thing, reset my router (which I know isn't the problem). Then I did the whole trace thing to be told my signal slows down. Obviously the guy who said that has no idea how networking works. A signal doesn't slow down; the return latency time increases because the return of your signal is based on how far it needs to travel. Idiot!! Then I was told to do the whole port forwarding step. Did that too, even disabled my firewall and the router's firewall to see if that was the problem, and to no surprise, there was no change. VC still doesn't work; I receive either error code 1071, 1072, 1073. Being a software support guy I, the first thing I ask a client when something goes wrong is: "What was the last thing you did?" Well, the last thing I did before the VC stopped working was LU52. I think Sony should review the changes that were made in LU52 as obviously that was where it started. They need to accept responsibility and fix the mess. I really can't believe that everyone all of a sudden has hardware and firewall issues when everything was working fine before LU52.I would like to see how they respond to this.

[Kronick]

Continuing to have issues with VC. Today it again ran fine for about 30 minutes. When I first logged on the vc menu had the extra button saying I was not logged on vc on my toon, pushed that, played with the settings to select headset etc and vc ran fine.

About 30 mins later and mid raid I was abrubtly dropped from vc and the button came back saying I was not logged on vc on my toon - clearly not true as I had not logged or changed toons in the intervening 30 mins.

Anyhow I pushed the button but now nothing worked on vc, could not select headset could not enter channels etc. Camped out of game etc but vc refused to respond to any commands so raided in silence for next 3 hours which is not really very much fun...

[bumford007]

ok I just recieved this email this afternoon seems like they gotta find the bug first, which by this email looks like they havent found yet.

Thank you for contacting Sony Online Entertainment.At this point since your firmware is up to date and you've made the requested changes on your end then it's likely that this is being caused by a bug on our end or in the voice chat protocol which we're currently investigating. We expect to have a patch ready to correct this soon but I don't have an exact ETA at this time. I sincerely appreciate your patience so far in this matter and I apologize for any inconvenience this may have caused. If you have any other questions or issues please don't hesitate to contact us again and we'll be happy to assist you.

make of it what you will. I still demand a free month's play, and think you need to get your crap together. I dont care if your feelings got hurt rothgar really get over it, your getting paid arent you.

[Dethdlr]

Don't know if this will help or not but generally when trying to troubleshoot a problem, the more info the better.

I have voice issues as well but mine are really annoyances rather than complete failure to work.  It sometimes takes a while to get into guild voice chat.  I usually end up disabling voice and re-enabling it a few times before it works.  Sometimes I have to restart the game altogether.  Wife has the same problem on her machine.  

Last night while trying this, I decided to go into task manager and fiddle with the tasks themselves since my normal attempts weren't working.  I disabled voice in game with the checkbox.  I then killed the VivoxVoiceService process in task manager.  I then enabled voice in game.  I waited a few seconds and was then able to join guild chat.  I looked at task manager to see what process had started up and it was EQ2VoiceService.  Not VivoxVoiceService.  I launch the game with StationLauncher btw but don't join voice until I'm in game.

I thought it was interesting that there were two separate processes, VivoxVoiceService and EQ2VoiceService.  Don't know if it's the same thing being registered two different ways depending on how it's launched or if it's actually two separate files.  Looks like it's the same one but don't know.  Anyway, thought more info might help.  Sorry if this is old news and has been posted earlier.

[DJWolf5]

Decimatr@Kithicor wrote:

Don't know if this will help or not but generally when trying to troubleshoot a problem, the more info the better.

I have voice issues as well but mine are really annoyances rather than complete failure to work.  It sometimes takes a while to get into guild voice chat.  I usually end up disabling voice and re-enabling it a few times before it works.  Sometimes I have to restart the game altogether.  Wife has the same problem on her machine.  

Last night while trying this, I decided to go into task manager and fiddle with the tasks themselves since my normal attempts weren't working.  I disabled voice in game with the checkbox.  I then killed the VivoxVoiceService process in task manager.  I then enabled voice in game.  I waited a few seconds and was then able to join guild chat.  I looked at task manager to see what process had started up and it was EQ2VoiceService.  Not VivoxVoiceService.  I launch the game with StationLauncher btw but don't join voice until I'm in game.

I thought it was interesting that there were two separate processes, VivoxVoiceService and EQ2VoiceService.  Don't know if it's the same thing being registered two different ways depending on how it's launched or if it's actually two separate files.  Looks like it's the same one but don't know.  Anyway, thought more info might help.  Sorry if this is old news and has been posted earlier.

I would like to highlight this post.  While I don't have this problem, is this a clue?

[Mikkahl]

I've never seen VivoxVoiceService.exe, only EQ2VoiceService.exe process in Task Manager (sometimes 2, 3, or 4 copies of the process running!).  But I only use voice from inside of EQ2, and I've never used the Station Launcher - only the regular patcher.   (Isn't Station Launcher still in Beta?  If so, I wonder why anybody is using it who's not under Beta NDA?)

[Dethdlr]

Mikkahl wrote:

(Isn't Station Launcher still in Beta?  If so, I wonder why anybody is using it who's not under Beta NDA?)

Umm,  because it's been a publicly available download since like 2007?

http://launcher.station.sony.com/

[Seiji-01]

In light of the last several posts, thought I'd go ahead and add that the voice service .exe that's been running in the background recently has been VivoxVoiceService.exe.

To reiterate, the only voice chat service I can get working has been through "Station Voice" through the Station Launcher.  After connecting to the Friends Network on the Station Launcher, I get the option to Join Voice Channel under the same Friends tab that I connected under.  When I join my guild's voice channel with this service, I CAN VOICE CHAT.  However, when I try to join any voice channel in-game (Group, Guild, Raid), the voice service is flawed.  I CAN log-in, and I can see who's currently in the channel, but I can't hear anyone nor can I see who's talking after an initial 3-5 seconds of clear audio.

Out of curiousity:  is there any way I can further this work-around and join my guild's Raid channel with the out-of-game Station Voice?

[Nink]

Here is the info I got from SOE :-

Greetings,Vivox is now using packets that exceed the maximum size for most routers. That is causing many routers to block them or break them apart. Looks like yours is breaking it apart. Because of that, the only real solution would be to install firmware that increases the size limit(not always possible) or to bypass the router entirely. You can find updates from the router manufacturer. I hope this tid-bit helps.

Info from NetGear Site :-

1500. The largest Ethernet packet size; it is also the default value. This is the typical setting for non-PPPoE, non-VPN connections. The default value for NETGEAR routers, adapters and switches.

1492. The size PPPoE prefers.

1472. Maximum size to use for pinging. (Bigger packets are fragmented.)

1468. The size DHCP prefers.

1460. Usable by AOL if you don't have large email attachments, etc.

1430. The size VPN and PPTP prefer.

1400. Maximum size for AOL DSL.

576. Typical value to connect to dial-up ISPs.

[DJWolf5]

I've got a station account but I use the Everquest 2 icon on my desktop.  I'm confused.  Should I install the station launcher that Check has linked to?  Don't I use the station launcher already?  What should I be using?

[DJWolf5]

Nink wrote:

Here is the info I got from SOE :-

Greetings,Vivox is now using packets that exceed the maximum size for most routers. That is causing many routers to block them or break them apart. Looks like yours is breaking it apart. Because of that, the only real solution would be to install firmware that increases the size limit(not always possible) or to bypass the router entirely. You can find updates from the router manufacturer. I hope this tid-bit helps.

Info from NetGear Site :-

1500. The largest Ethernet packet size; it is also the default value. This is the typical setting for non-PPPoE, non-VPN connections. The default value for NETGEAR routers, adapters and switches.

1492. The size PPPoE prefers.

1472. Maximum size to use for pinging. (Bigger packets are fragmented.)

1468. The size DHCP prefers.

1460. Usable by AOL if you don't have large email attachments, etc.

1430. The size VPN and PPTP prefer.

1400. Maximum size for AOL DSL.

576. Typical value to connect to dial-up ISPs.

I'm not "happy" but perhaps "willing" is the word to spend money to get a modem that is ADSL2+ compliant and will run the packet size required by Vivox.  Unfortunately, my modem with updated firmware will not.  Can someone please confirm that ADSL2+ can transmit and use this larger packet size?  I'm not getting much useful feedback so far from Belkin.  An "I have an Australian ISP account and I get voice chat" would be a tremendous piece of news.

[Mikkahl]

The impression I get is that the 1500 MTU limit is not just in our routers or modems, but is also in all of the hundreds of switches along the way all through the Internet.  So for Sony/Vivox to continue to claim that the "only real solution" is to rework all of the Internet to accommodate the non-standard Vivox packets is ridiculous.  As DLink said, they are playing "fast and loose" with the rules.  The "real solution" is for Vivox to reword their packet content to fit within the 1500 standard limit.  If they are currently 1557 this is only about a 1% reduction.  Change a few words to bytes, byte flags to bit fields, etc.   (The kind of engineering that has been done for decades to accomodate limited space, by all of us programmers.)

Now of course I have no idea if this will solve the voice chat problems.  If their packets are always too long and getting broken up, then why do I have voice chat 80% of the time (with lots of disable/re-enable "fiddling")?

[Gaelwyn]

Doing a test on the EQ2VoiceService.exe and VivoxVoiceService in Task Master processes.

I. Turned off Enable Voice Chat ingame.

2. Turned Enable Voice Chat On Ingame - Record - Blue line runs to test

3. Playback button Grayed out.

4. Record button - Unresponsive.

5. Test Mic - Unresponsive

6. Test bar filled up with blue to the end of the bar, static, no yellow indicator just a deep blue color.

7. ONLY EQ2VoiceService.exe showing in Task Master.

This is the first time I have seen the blue bar once in the game, granted I have not done this test before.  There is no sign of VivoxVoiceService.exe in my task master.

Adding to DJWolf5's post, I downloaded Station Launcher this morning, I thought, give it a go.  I only knew of this because of the comments related to it here within these posts.  Do we need to have this programe to run voice chat?  I saw 4 gig of updates and thought "Your kidding me".  It is still sitting waiting for me to find the spare time to allocate to it. 

[Elcarp]

DJWolf5 wrote:

I've got a station account but I use the Everquest 2 icon on my desktop.  I'm confused.  Should I install the station launcher that Check has linked to?  Don't I use the station launcher already?  What should I be using?

I have tried using both Station Launcher and the standard EQ2 updater, neither of which seems to make any difference for me. I still can hear everyone else chatting, but am only able to be heard about 15% of the time, regardless of which method I use for launch.

[Damevako]

I hope this information proves useful in finding a solution to this problem...

 

I’ve been playing around with the Station Launcher and monitoring the log files to see if I can find a pattern to why the Voice Chat  aint working (I didn’t even attempt to try monitoring the voice chat logs from within the game – it would have been too hard to start the game up and shut it down every minute. FYI – my vc isn’t working in the game either).

Note

I’ve had the occasional times when vc would just randomly ‘fix’ itself whilst I’ve been playing for a few hours. This is a clear indication to me that this has nothing to do with my Firewall and/or Router – nothing would have changed on those whilst I’m playing.

Based on my experience above (i.e. the random fixing itself thing), and some of the information I’ve seen in the vivox logs, I’m suspecting that the issue is more than likely on Vivox’s end.

 

Here are some detailed steps that I went through to generate the provided logs:

1)      Browsed to the Station Launcher (AppData folder)

2)      Delete the following files (At this stage I make sure that I don’t have Station Launcher running before I delete these logs)

a.       StationServices.exe.log

b.      StationLauncher.dll.log

3)      Launch Station Launcher & Log in.

4)      Once logged on, the above-mentioned log files would have recreated itself.

5)      Within Station Launcher, I select the menu  option to ‘Connect to a Friends Network’

6)      The next step, I select the option ‘Join Voice Channel...’

7)      On the Station Voice window, I select a character.

      The Channel Name dropdown populates with a list of channels for this character – The default in my case is the Guild’s channel.

9)      When I click Join, the following Channel Activities are displayed:

a.       Changed character to Damevako

b.      Retrieved voice credentials for Damevako

c.       Succeeded retrieving channel uri for character 'Damevako': sip:[email protected]

d.      Connected to host

e.      https://www.e2p.vivox.com/api2

f.        Logged in user Lucan_DLere.Damevako-

g.       Logged in user Lucan_DLere.Damevako-

h.      Unknown error occurred

 

10)   At this stage, when I view the StationServices.exe.log file, the following error draws my attention:

2009-07-12 22:49:53 [58088] ERROR station::service::VivoxJoinChannelRequest - No Session Ports are available.

 

                What session ports is it looking for? I’m assuming this is server side and out of my control?

 

Log File (StationService.exe.log - On the next post)

[Damevako]

Log File (StationService.exe.log - Continue)

2009-07-12 22:48:59 [58088] INFO  station::service::Application - Starting application C:UsersNecromongerAppDataLocalLowSony Online EntertainmentStation LaunchermainStationServices.exe Release main-790318 2009-07-12 22:48:59 [58088] INFO  station::service::Application - Trying to start vivox voice service 2009-07-12 22:48:59 [58088] INFO  station::service::MessageQueue - Message queue 'voice_service' has been created 2009-07-12 22:48:59 [58088] INFO  station::service::ResponseManager - GetCurrentStateDump response received 2009-07-12 22:49:00 [58088] INFO  station::service::ConnectRequestExecutor - Executing request from Client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:00 [58088] INFO  station::service::ConnectionManager - Received connect request from 'StationLauncher.exe_57964' Client version: 1 2009-07-12 22:49:00 [58088] INFO  station::service::MessageQueue - Message queue 'voice_service_StationLauncher.exe_57964' has been created 2009-07-12 22:49:00 [58088] INFO  station::service::ConnectRequestExecutor - Executing request from Client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:00 [58088] INFO  station::service::ConnectionManager - Received connect request from 'StationLauncher.exe_57964' Client version: 1 2009-07-12 22:49:00 [58088] ERROR station::service::ConnectRequestExecutor - Connecting 'StationLauncher.exe_57964' failed. Already connected. 2009-07-12 22:49:00 [58088] INFO  station::service::GetRenderDevicesRequestExecutor - Executing get render devices request from client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:00 [58088] INFO  station::service::GetCaptureDevicesRequestExecutor - Executing get capture devices request from client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:00 [58088] INFO  station::service::ResponseManager - GetRenderDevices response received 2009-07-12 22:49:00 [58088] INFO  station::service::ResponseManager - GetCaptureDevices response received 2009-07-12 22:49:04 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:09 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:10 [58088] INFO  station::service::SetPushToTalkKeyRequestExecutor - Executing set push-to-talk key request from client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:10 [58088] INFO  station::service::ResponseManager - SetPushToTalkKey response received 2009-07-12 22:49:11 [58088] INFO  station::service::ResponseManager - MuteCaptureDevice response received 2009-07-12 22:49:14 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:19 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:21 [58088] INFO  station::service::LogoutRequestExecutor - Executing request from Client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:21 [58088] ERROR station::service::VivoxLogoutUserRequest - Tried to logout user but we are not even logged in 2009-07-12 22:49:24 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:25 [58088] INFO  station::service::LogoutRequestExecutor - Executing request from Client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:25 [58088] ERROR station::service::VivoxLogoutUserRequest - Tried to logout user but we are not even logged in 2009-07-12 22:49:29 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:31 [58088] INFO  station::service::ConnectServerRequestExecutor - Executing request from Client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:34 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:36 [58088] INFO  station::service::ResponseManager - Connector created: 2 2009-07-12 22:49:37 [58088] INFO  station::service::LoginRequestExecutor - Executing login request from client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:37 [58088] WARN  station::service::ResponseManager - evt_AccountLoginStateChange unhandled state: 2 2009-07-12 22:49:39 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:44 [58088] INFO  station::service::ResponseManager - AccountLogin response received: 3 2009-07-12 22:49:44 [58088] INFO  station::service::ResponseManager - evt_AccountLoginStateChange[ login_state_logged_in ] for: 3 2009-07-12 22:49:44 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:44 [58088] INFO  station::service::SwitchChannelRequestExecutor - Executing switch channel request from client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:44 [58088] INFO  station::service::ResponseManager - SessionGroupCreate response received: 4 2009-07-12 22:49:44 [58088] INFO  station::service::ResponseManager - evt_SessionGroupAdded: 4 2009-07-12 22:49:44 [58088] INFO  station::service::ResponseManager - SessionAdd response received: 7 2009-07-12 22:49:44 [58088] INFO  station::service::ResponseManager - evt_SessionAdded: 7 to 4 2009-07-12 22:49:44 [58088] INFO  station::service::ResponseManager - evt_SessionUpdated: 7 2009-07-12 22:49:44 [58088] WARN  station::service::ModelController - Cannot update channel because there is no current channel (null) 2009-07-12 22:49:44 [58088] INFO  station::service::ResponseManager - evt_MediaStreamUpdated for 4[7] 2009-07-12 22:49:44 [58088] INFO  station::service::ResponseManager - evt_TextStreamUpdated: 4[7] 2009-07-12 22:49:44 [58088] WARN  station::service::ModelController - Received text stream updated event for channel 7 but we haven't joined a channel yet 2009-07-12 22:49:49 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:53 [58088] INFO  station::service::ResponseManager - evt_MediaStreamUpdated for 4[7] 2009-07-12 22:49:53 [58088] INFO  station::service::ResponseManager - evt_MediaStreamUpdated for 4[7] 2009-07-12 22:49:53 [58088] WARN  station::service::ModelController - Cannot update channel because there is no current channel (null) 2009-07-12 22:49:53 [58088] ERROR station::service::VivoxJoinChannelRequest - No Session Ports are available. 2009-07-12 22:49:53 [58088] INFO  station::service::ResponseManager - evt_TextStreamUpdated: 4[7] 2009-07-12 22:49:53 [58088] WARN  station::service::ModelController - Received text stream updated event for channel 7 but we haven't joined a channel yet 2009-07-12 22:49:53 [58088] INFO  station::service::ResponseManager - evt_TextStreamUpdated: 4[7] 2009-07-12 22:49:53 [58088] WARN  station::service::ModelController - Received text stream updated event for channel 7 but we haven't joined a channel yet 2009-07-12 22:49:53 [58088] INFO  station::service::ResponseManager - evt_SessionRemoved: 7 from 4 2009-07-12 22:49:54 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:49:59 [58088] INFO  station::service::TouchRequestExecutor - Executing request from Client: StationLauncher.exe_57964 Version: 1 2009-07-12 22:49:59 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:50:04 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:50:09 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:50:14 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:50:19 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:50:24 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts 2009-07-12 22:50:29 [58088] INFO  station::service::ConnectionManager - Checking for client timeouts

[Romwar]

I've found  fix - sort of.  When I get kicked from vc i go to the vc options panel and uncheck enable voice chat.  I wait a minute, re-enable it.  This is usualy followed by the "connection failure 1072" message, I then just click  the talk button, and somehow it magicaly connects to whatever channel I select.

[seenya]

I had a reponse from my VC yeasterday whilst playing, has anybody got any idea what it means, "Voice Chat login failure: 1001", what does 1001 mean?

[DJWolf5]

I have Voice Chat connection failure 1004.

[Mikkahl]

Romwar wrote:

I've found  fix - sort of.  When I get kicked from vc i go to the vc options panel and uncheck enable voice chat.  I wait a minute, re-enable it.  This is usualy followed by the "connection failure 1072" message, I then just click  the talk button, and somehow it magicaly connects to whatever channel I select.

This is the "fiddling" I've mentioned countless times, disabling and re-enabling voice chat until I can get it to work (usually when I want to change channels, like to Group or Raid).  And after a few attempts I may be able to connect to a channel, and hear all the other people, but they can't hear me.  So then I have to "fiddle" a few more times to get my microphone working.

Sometimes I have to reboot EQ2 or my machine to get it working.

And sometimes it just never works at all, like in the pick up raid I had to drop out of last week, because voice was required by the raid leaders.

And of course all this time spent "fiddling" to get into raid voice chat, I should be listening to the raid leaders instructions (but, I can't hear them), putting my buffs on the right people, getting on the right gear or potions, setting up target macros, etc.  This is the most frustrating part of these voice chat problems - it should just work seemlessly, without any extra effort.

(I also keep checking Task Manager to be sure that the EQ2VoiceService.exe process goes away when I disable voice chat, and comes back when I re-enable voice chat.  If the process does not go away, I End Process on it.  Otherwise, I have sometimes ended up with 3-4 copies of the EQ2VoiceService.exe process running at the same time.)

[bigsigh]

So we fiddle, we cross our fingers, we bang our heads on the desk, and from SOE... we hear silence.

Rothgar tells us he is doing us a favour by giving us updates even though it is not his job. Ok, fair enough, so get the guy whose job it is to give us one please, preferably one where he tells us something constructive, like say, 'guys, we realise that this has gone on for far too long. We screwed up, and despite the hassle it will cause us, we are reverting back to the old system until such time that we can figure out why the new system is so flaky. We know now that releasing a product that those on test TOLD US didn't work was a bad move, so in the future, we will listen to the players and not some artificial deadline. This WILL be fixed within the week and we hope you can etc etc'

People are sick of this... very very sick.

[Pikard]

From all the evidence this seems to be happening to mostly people located far away from the SoE servers.

I myself am living in Thailand and have a ping of over 400 most of the time. I suspect this might be a simple tolerance issue with the Vivox servers. they simply cannot handle high pings.

and BTW, I must say.. This is a fine example of the complaints we have all been giving Sony over the years about unresolved issues and lack of communication.

Rothgar, just who IS responsible for keeping the user community updated on these issues and why haven't they been communicating with us?

Greg