Messages

1

General discussion forum / Re: modem exchange issue

« on: 2013-02-12, 21:14:31 »

Hi guys,
try another modem, thats what im going to do anyway, because with this one i already try everyhing. I will let you know here of the result after my holiday

rgds Petr

2

General discussion forum / Re: modem exchange issue

« on: 2013-02-12, 09:41:16 »

Dear Mikael, Mitch,
Your answers sounds logically, but you probably miss the point. Behavior what i was describing, is not seen on WAN interface behind the modem, but on LAN what means this is going from the RRC, yet before modem(router) got chance for any modification of the traffic.

To Mitch - correct, the modem is combined with router, namely it’s Zyxel P-870HN-53b. Of course, first what i set was NAT/PAT, but no sucess neither when trying DMZ. I already switch all enhanced functionalities off, even including firewall, but still without any change. Believe me, i has beeen playing with this setup more than one month wihout success.

As you can see on enclosed printscreens, RRC sending SIP INFO later than RTP STREAM, whac causes that remote answers ICMP destination unreachable. Do you have any explanation, why RRC is sending packets in such order?

3

General discussion forum / modem exchange issue

« on: 2013-02-07, 16:37:46 »

Hi everybody
I have interesting issue. After several years of usage RRC-1258II, i upgraded my home conectivity from ADSL to VDSL. Unfortunately i'm now not able to connect to the remote. I bring the modem back to the operator, but it seems that with modem everything is ok and problem is in RRC.
As the opertator technician dicvovered, RRC connected to the new modem turns over the sequence of the session opening packets and the server side simply rejects the connection than. Technician tested everything with both, previous and new modem on the same line, with the same RRC, and result is that packets order with old and new modem is reversed. Traces were done on local LAN interface. Is there any reason why RRC behaves so? Any idea how to fix? I tried the latest firmware, but no change.

I have trace logs available, so i can send them by e-mail for deeper investigation if reasonable.

tnx Petr