What I mean is acquire a public IP and put it on your Linux box. Then configure SER to listen on that IP! If you must run SER in private address space, you will need to use record_route_preset() and advertised_address to help. You also need port forwarding at your NAT router as well. However, this is not a recommended approach.
-----Original Message----- From: Freeman Sent: Thursday, 30 June 2005 5:49 PM To: Zeus Ng; serusers@lists.iptel.org Subject: RE: [Serusers] [Seruser] GettingStarted04 - RTPProxy Setting Problem !
I tried to change the config in ser.cfg , listen=192.168.10.1 ( private ip ) to listen=234.234.234.234 ( public ip ), but i get some error in "/var/log/messages" as below :
rtpproxy: Starting SER RTP Proxy server: rtpproxy rtpproxy: . rc: Starting rtpproxy: succeeded xfs: xfs startup succeeded xfs: ignoring font path element /usr/X11R6/lib/X11/fonts/cyrillic (unreadable) ser: WARNING: fix_socket_list: could not rev. resolve 234.234.234.234 ser: WARNING: fix_socket_list: could not rev. resolve 234.234.234.234 ser: Listening on ser: udp: 234.234.234.234 [234.234.234.234]:5060 ser: tcp: 234.234.234.234 [234.234.234.234]:5060 ser: Aliases: ser: Jun 30 15:41:03 localhost ser: ser startup succeeded Jun 30 15:41:03 localhost /usr/local/sbin/ser[2356]: Maxfwd module- initializing Jun 30 15:41:05 localhost /usr/local/sbin/ser[2356]: INFO: udp_init: SO_RCVBUF is initially 65535 Jun 30 15:41:05 localhost /usr/local/sbin/ser[2356]: INFO: udp_init: SO_RCVBUF is finally 131070 Jun 30 15:41:05 localhost /usr/local/sbin/ser[2356]: ERROR: udp_init: bind(5, 0x80fd674, 16) on 234.234.234.234: Cannot assign requested address
tks a lot ! Freeman
Zeus Ng zeus.ng@isquare.com.au 說：
Are you running SER in the private address space (10.x, 172.x or 192.168.x)? That does not run well unless you know how to use record_route_preset() and advertised_address. I recommend you move your SER to public address space.