Yup, the firmware update fixed all party chat issues.
No port forwarding is set up -- we have two PS4s in the house, so explicit port forwarding wouldn't be possible. UPnP is enabled on our router so the PS4s figure out what ports they want themselves. (ASUS router; the CGN modem itself is in bridge mode) Works fine now, whereas before the firmware update it was almost completely unusable.
There is a post which indicated that the latest firmware update for the CGN3ACSMR resolved that issue for another user. If you are having problems with the CGN3, maybe a switch to the CGN3ACSMR will resolve the issue. It will arrive with Firmware Version 126.96.36.199 which is problematic and not conducive to gaming. Firmware Version 188.8.131.52 should be loaded on the modem within 48 hours of it going active on the network. If you have the modem beyond 48 hours and the firmware has not updated it can be requested from CommunityHelps.
Have a look at message # 121 of 138, which is the top post.
i had it in may but i want to know if it resolves the gaming problems because i dont want to go back to a rogers store to pick it up and have the same issues and have to go back to get the cgn3rog again
There are mixed comments, good and bad for both the PS3 and PS4 and the CGN3ACSMR. I don't think that there is enough user feedback to determine if the update is 100% successful in addressing all of the issues with both consoles. Your comment would seem to suggest that it didn't work for the PS4 in your case. Maybe there are specific game issues that need to be addressed, in terms of additional changes to the modem firmware, and there is always the possibility of gaming server issues. Can you indicate what games you play, detail the problems that you have when playing them and indicate if the problems are game specific or global, as in every game. The only way to resolve these issues is to look at these details to see what is common, if anything and what might be a stand-alone issue. It won't be easy to determine when for example, party chat works for one person but not the other. Is that a game specific issue, a server issue, or something else that I'm not thinking about?
@RogersAsif appears to be the point guy on staff for PS3 and PS4 issues as he has both and both appear to work without any issue. He should see this thread at some point and might post additional comments.
well i mostly play destiny and i know that it is internet sensitive wich cng3acmr is not good for at all wich is why i discconect alot and i use party chat for that and cant talk at all
Thats interesting. The update solved issues with Destiny and Party Chat for others, but not for you. So, given that, do you play via wired or wireless connection to the modem. Can you log into the modem, navigate to the STATUS.... DOCSIS WAN page, copy the downstream and upstream tables and paste them into this thread. Those are the cable signal levels and signal to noise ratios which might be worth checking out.
Have you set the ports required for port forwarding, or have UPNP turned on, which should do it all for you?
i play wireless and wired but issue persits with both but heres the docsis
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Signal noise ratio (dB)||Channel ID|
|Port ID||Frequency (MHz)||BandWidth||Modulation Type||Signal Strength (dBmV)||Channel ID|
The downstream levels are slightly low but thats no issue. Signal to noise on the downstream is good. The upstream signal levels are fine. Forwarded ports set manually or is UPNP turned on to do this? If you have the CGN3, it should have Firmware Version 184.108.40.206 loaded. UPNP on the CGN3 wasnt' working until that version was or is loaded.
Not at all. Its typical to see signal levels on the downstream slightly below or above the 0 dBmV median value. The range is + 15 dBmV down to - 15 dBmV. They should normally be at or very near 0 dBmV. Mine have wandered from + 3 down to - 3 and back up again during the last year. So, they tend to wander slightly. That won't affect your data rate considering that the indicated signal to noise is very good.
I have to admit that I'm stumped as to why this works for one PS4 user and not the next. I'm still thinking that its game or game server specific. Maybe, the node performance comes into this. The neighborhood node is the next upstream device in the network. If that is overloaded you would see latency issues with it. That might just be enough to cause gaming issues.
Doing a little searching, it looks like there is some history behind the party chat issue:
If you log into the modem when the PS4 is up and running in a game do you see all of the ports and TCP / UDP type data set for forwarding as indicated here:
Is there anything missing from that list that the UPNP isn't properly setting?
Yep, with the PS4 fired up and running a game, if you login to the modem and navigate to BASIC.... PORT FORWARDING, you should be able to see the various ports that have been set by UPNP. In fact, they are probably there already as it appears that UPNP doesn't clean up after itself. It might be worth checking without the game running to see if they are already there. If they are not, or some are missing, I'd check again with the game running. A page refresh would probably be required if you left the port forwarding page up and then started the PS4 and a selected game.
So the port forwarding list in the modem is empty? That doesn't make any sense. There have been comments made by others who have seen the ports set due to the fact that UPNP was finally working. Ok, if the port forward page is empty and UPNP is enabled, the thing to do is to disable UPNP, restart the modem, create a static (DHCP reserved) IP address for the PS4, and then set the port forwarding as required. Save the settings and restart the modem.
Now, if you have already manually set the ports in the past this is all a moot point, especially if you used a static IP address at that point. Been there, done that, so to speak. If thats the case, I'll have to think about this one.....