Don't know if it's a mistake of SIPatH or a faulty integration into DD-WRT, so:
I changed router's IP back to defaul 192.168.1.1 but this doesn't solve my problem
Status: Overview
SER Stats: Message type: Occurances
200: 0 202: 0 2xx: 0
300: 0 301: 0 302: 0 3xx: 0
400: 0 401: 0 403: 0 404: 0 407: 0 408: 0 483: 0 4xx: 0
500: 0 5xx: 0
6xx: 0
xxx: 0
failures: 0
SER processes: First Receiver Process per IP:Port
1 1223 receiver child=0 sock=0 @ 127.0.0.1:5060
3 1225 receiver child=0 sock=1 @ 192.168.1.1:5060
5 1227 receiver child=0 sock=2 @ 195.158.xxx.xxx:5060
RTPproxy: 192.168.1.1 195.158.xxx.xxx
lan address: 192.168.1.1
wan address:
Device Info: Boardtype: 0x0101, Boardnum: 42
SER Uptime: Please note: Automatic SER restarts may be due to changing network interface addresses
Now: Sun Jul 24 09:47:46 2005
Up Since: Sun Jul 24 09:44:55 2005
Up time: 171 [sec]
Router Uptime: 09:47:46 up 5 min, load average: 0.17, 0.18, 0.08
The outcome of cat /etc/ser/ser.cfg | grep fix is:
fix_nated_contact ("192.168.1.2);
fix_nated_contact ("192.168.1.2);
fix_nated_contact ("192.168.1.2);
The developer of SIPatH wrote me:
OK, the NAT fixing does not work properly. You are registering with the private address 192.168.1.2 and the named providers "don't want you to use private ip addresses". This address is the default one and should be updated with your ppp0 address when dialing in. In other words the command "cat /etc/ser/ser.cfg | grep fix" should print your current ppp0 address. In your case this doesn't work.
Maybe you have a problem with the ip-up script.
I'm wondering why you don't have an entry in the wan address section of the status page.