30 Jun
2005
30 Jun
'05
7:48 a.m.
Hi,
I tried to follow the manual "GettingStarted 04 - 2005-05-26" to create
ser.cfg ( for RTPProxy ), i found some error in "/var/log/messages",
rtpproxy: Starting SER RTP Proxy server: rtpproxy
rtpproxy: .
rc: Starting rtpproxy: succeeded
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: Listening on
ser: udp: 192.168.10.1 [192.168.10.1]:5060
ser: tcp: 192.168.10.1 [192.168.10.1]:5060
ser: Aliases:
ser:
ser: ser startup succeeded
/usr/local/sbin/ser[2353]: Maxfwd module- initializing
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is initially 65535
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is finally 131070
/usr/local/sbin/ser[2373]: INFO: fifo process starting: 2373
/usr/local/sbin/ser[2373]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2373]: SER: open_uac_fifo: fifo server up at /tmp/ser_fifo...
/usr/local/sbin/ser[2375]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2380]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2381]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2382]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2377]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2383]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2389]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2353]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2388]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2387]: rtpp_test: RTP proxy found, support for it enabled
/usr/local/sbin/ser[2379]: rtpp_test: RTP proxy found, support for it enabled
I tried to test the ser in some case : ( using Windows Messenger 5.1 and released all port
for ser )
1. "User A ( outside with NAT ) call User B ( same network with ser )"
- User A can't call User B.
2. "User B ( same network with ser ) call User A ( outside with NAT )"
- User B can call User B but No Voice and auto hangup.
3. "User A ( outside with NAT ) call User C ( outside with NAT )"
- User A can't call User C.
I found some information in MySQL ( Database : ser , Table : location )
username contact received
user_a sip:192.168.1.1:7700 sip:234.234.234.234:1568 ( public ip )
user_b sip:192.168.10.11:7446 sip:192.168.10.1.3112 ( private ip )
user_c sip:192.168.2.1:15647 sip:123.123.123.123:21144 ( public ip )
I tried many times, but the problem is same !
Please help !
tks a lot !
Freeman
_______________________________________
想即時收到新 email 通知？
下載 Yahoo! Messenger http://messenger.yahoo.com.hk
30 Jun
30 Jun
11:34 a.m.
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.
-----Original Message-----
From: serusers-bounces(a)lists.iptel.org On Behalf Of Freeman
Sent: Thursday, 30 June 2005 12:49 PM
To: serusers(a)lists.iptel.org
Hi,
I tried to follow the manual "GettingStarted 04 -
2005-05-26" to create ser.cfg ( for RTPProxy ), i found some
error in "/var/log/messages",
rtpproxy: Starting SER RTP Proxy server: rtpproxy
rtpproxy: .
rc: Starting rtpproxy: succeeded
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: Listening on
ser: udp: 192.168.10.1 [192.168.10.1]:5060
ser: tcp: 192.168.10.1 [192.168.10.1]:5060
ser: Aliases:
ser:
ser: ser startup succeeded
/usr/local/sbin/ser[2353]: Maxfwd module- initializing
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is
initially 65535
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is finally 131070
/usr/local/sbin/ser[2373]: INFO: fifo process starting: 2373
/usr/local/sbin/ser[2373]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2373]: SER: open_uac_fifo: fifo server up
at /tmp/ser_fifo...
/usr/local/sbin/ser[2375]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2380]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2381]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2382]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2377]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2383]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2389]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2353]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2388]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2387]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2379]: rtpp_test: RTP proxy found,
support for it enabled
I tried to test the ser in some case : ( using Windows
Messenger 5.1 and released all port for ser )
1. "User A ( outside with NAT ) call User B ( same network with ser )"
- User A can't call User B.
2. "User B ( same network with ser ) call User A ( outside with NAT )"
- User B can call User B but No Voice and auto hangup.
3. "User A ( outside with NAT ) call User C ( outside with NAT )"
- User A can't call User C.
I found some information in MySQL ( Database : ser , Table :
location )
username contact received
user_a sip:192.168.1.1:7700
sip:234.234.234.234:1568 ( public ip )
user_b sip:192.168.10.11:7446
sip:192.168.10.1.3112 ( private ip )
user_c sip:192.168.2.1:15647
sip:123.123.123.123:21144 ( public ip )
I tried many times, but the problem is same !
Please help !
tks a lot !
Freeman
12:48 p.m.
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(a)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.
-----Original Message-----
From: serusers-bounces(a)lists.iptel.org On Behalf Of Freeman
Sent: Thursday, 30 June 2005 12:49 PM
To: serusers(a)lists.iptel.org
Hi,
I tried to follow the manual "GettingStarted 04 -
2005-05-26" to create ser.cfg ( for RTPProxy ), i found some
error in "/var/log/messages",
rtpproxy: Starting SER RTP Proxy server: rtpproxy
rtpproxy: .
rc: Starting rtpproxy: succeeded
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: Listening on
ser: udp: 192.168.10.1 [192.168.10.1]:5060
ser: tcp: 192.168.10.1 [192.168.10.1]:5060
ser: Aliases:
ser:
ser: ser startup succeeded
/usr/local/sbin/ser[2353]: Maxfwd module- initializing
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is
initially 65535
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is finally 131070
/usr/local/sbin/ser[2373]: INFO: fifo process starting: 2373
/usr/local/sbin/ser[2373]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2373]: SER: open_uac_fifo: fifo server up
at /tmp/ser_fifo...
/usr/local/sbin/ser[2375]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2380]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2381]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2382]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2377]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2383]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2389]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2353]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2388]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2387]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2379]: rtpp_test: RTP proxy found,
support for it enabled
I tried to test the ser in some case : ( using Windows
Messenger 5.1 and released all port for ser )
1. "User A ( outside with NAT ) call User B ( same network with ser )"
- User A can't call User B.
2. "User B ( same network with ser ) call User A ( outside with NAT )"
- User B can call User B but No Voice and auto hangup.
3. "User A ( outside with NAT ) call User C ( outside with NAT )"
- User A can't call User C.
I found some information in MySQL ( Database : ser , Table :
location )
username contact received
user_a sip:192.168.1.1:7700
sip:234.234.234.234:1568 ( public ip )
user_b sip:192.168.10.11:7446
sip:192.168.10.1.3112 ( private ip )
user_c sip:192.168.2.1:15647
sip:123.123.123.123:21144 ( public ip )
I tried many times, but the problem is same !
Please help !
tks a lot !
Freeman
相片電郵測試版一個郵件就可以傳送過百張相片！
1:44 p.m.
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(a)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(a)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.
1:09 p.m.
New 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(a)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.
-----Original Message-----
From: serusers-bounces(a)lists.iptel.org On Behalf Of Freeman
Sent: Thursday, 30 June 2005 12:49 PM
To: serusers(a)lists.iptel.org
Hi,
I tried to follow the manual "GettingStarted 04 -
2005-05-26" to create ser.cfg ( for RTPProxy ), i found some
error in "/var/log/messages",
rtpproxy: Starting SER RTP Proxy server: rtpproxy
rtpproxy: .
rc: Starting rtpproxy: succeeded
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: Listening on
ser: udp: 192.168.10.1 [192.168.10.1]:5060
ser: tcp: 192.168.10.1 [192.168.10.1]:5060
ser: Aliases:
ser:
ser: ser startup succeeded
/usr/local/sbin/ser[2353]: Maxfwd module- initializing
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is
initially 65535
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is finally 131070
/usr/local/sbin/ser[2373]: INFO: fifo process starting: 2373
/usr/local/sbin/ser[2373]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2373]: SER: open_uac_fifo: fifo server up
at /tmp/ser_fifo...
/usr/local/sbin/ser[2375]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2380]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2381]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2382]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2377]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2383]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2389]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2353]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2388]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2387]: rtpp_test: RTP proxy found,
support for it enabled
/usr/local/sbin/ser[2379]: rtpp_test: RTP proxy found,
support for it enabled
I tried to test the ser in some case : ( using Windows
Messenger 5.1 and released all port for ser )
1. "User A ( outside with NAT ) call User B ( same network with ser )"
- User A can't call User B.
2. "User B ( same network with ser ) call User A ( outside with NAT )"
- User B can call User B but No Voice and auto hangup.
3. "User A ( outside with NAT ) call User C ( outside with NAT )"
- User A can't call User C.
I found some information in MySQL ( Database : ser , Table :
location )
username contact received
user_a sip:192.168.1.1:7700
sip:234.234.234.234:1568 ( public ip )
user_b sip:192.168.10.11:7446
sip:192.168.10.1.3112 ( private ip )
user_c sip:192.168.2.1:15647
sip:123.123.123.123:21144 ( public ip )
I tried many times, but the problem is same !
Please help !
tks a lot !
Freeman
有即時通知，收艂
12:38 p.m.
To add to Zeus' comment:
rtpproxy *cannot* run on a private IP without a patch I posted a while back. Search the
archives (warning: the patch is outdated and must now be manually applied).
g-)
---- Original Message ----
From: Freeman
To: serusers(a)lists.iptel.org
Sent: Thursday, June 30, 2005 04:48 AM
Subject: [Serusers] [Seruser] GettingStarted04 - RTPProxy Setting
Problem !
Hi,
I tried to follow the manual "GettingStarted 04 - 2005-05-26"
to create ser.cfg ( for RTPProxy ), i found some error in
"/var/log/messages",
rtpproxy: Starting SER RTP Proxy server: rtpproxy
rtpproxy: .
rc: Starting rtpproxy: succeeded
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: Listening on
ser: udp: 192.168.10.1 [192.168.10.1]:5060
ser: tcp: 192.168.10.1 [192.168.10.1]:5060
ser: Aliases:
ser:
ser: ser startup succeeded
/usr/local/sbin/ser[2353]: Maxfwd module- initializing
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is initially
65535
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is finally 131070
/usr/local/sbin/ser[2373]: INFO: fifo process starting: 2373
/usr/local/sbin/ser[2373]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2373]: SER: open_uac_fifo: fifo server up at
/tmp/ser_fifo...
/usr/local/sbin/ser[2375]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2380]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2381]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2382]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2377]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2383]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2389]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2353]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2388]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2387]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2379]: rtpp_test: RTP proxy found, support for it
enabled
I tried to test the ser in some case : ( using Windows Messenger 5.1
and released all port for ser )
1. "User A ( outside with NAT ) call User B ( same network with ser )"
- User A can't call User B.
2. "User B ( same network with ser ) call User A ( outside with NAT )"
- User B can call User B but No Voice and auto hangup.
3. "User A ( outside with NAT ) call User C ( outside with NAT )"
- User A can't call User C.
I found some information in MySQL ( Database : ser , Table : location
)
username contact received
user_a sip:192.168.1.1:7700
sip:234.234.234.234:1568 ( public ip )
user_b sip:192.168.10.11:7446
sip:192.168.10.1.3112 ( private ip )
user_c sip:192.168.2.1:15647
sip:123.123.123.123:21144 ( public ip )
I tried many times, but the problem is same !
Please help !
tks a lot !
Freeman
_______________________________________
想即時收到新 email 通知？
下載 Yahoo! Messenger http://messenger.yahoo.com.hk
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
12:54 p.m.
New subject: 標題： Re: [Serusers] [Seruser] GettingStarted04 - RTPProxy Setting Problem !
Greger,
Sorry ! Where i can find the rtpproxy patch ????
tks a lot !
Freeman
"Greger V. Teigre" <greger(a)teigre.com> 說：
To add to Zeus' comment:
rtpproxy *cannot* run on a private IP without a patch I posted a while back. Search the
archives (warning: the patch is outdated and must now be manually applied).
g-)
---- Original Message ----
From: Freeman
To: serusers(a)lists.iptel.org
Sent: Thursday, June 30, 2005 04:48 AM
Subject: [Serusers] [Seruser] GettingStarted04 - RTPProxy Setting
Problem !
Hi,
I tried to follow the manual "GettingStarted 04 - 2005-05-26"
to create ser.cfg ( for RTPProxy ), i found some error in
"/var/log/messages",
rtpproxy: Starting SER RTP Proxy server: rtpproxy
rtpproxy: .
rc: Starting rtpproxy: succeeded
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: Listening on
ser: udp: 192.168.10.1 [192.168.10.1]:5060
ser: tcp: 192.168.10.1 [192.168.10.1]:5060
ser: Aliases:
ser:
ser: ser startup succeeded
/usr/local/sbin/ser[2353]: Maxfwd module- initializing
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is initially
65535
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is finally 131070
/usr/local/sbin/ser[2373]: INFO: fifo process starting: 2373
/usr/local/sbin/ser[2373]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2373]: SER: open_uac_fifo: fifo server up at
/tmp/ser_fifo...
/usr/local/sbin/ser[2375]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2380]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2381]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2382]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2377]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2383]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2389]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2353]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2388]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2387]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2379]: rtpp_test: RTP proxy found, support for it
enabled
I tried to test the ser in some case : ( using Windows Messenger 5.1
and released all port for ser )
1. "User A ( outside with NAT ) call User B ( same network with ser )"
- User A can't call User B.
2. "User B ( same network with ser ) call User A ( outside with NAT )"
- User B can call User B but No Voice and auto hangup.
3. "User A ( outside with NAT ) call User C ( outside with NAT )"
- User A can't call User C.
I found some information in MySQL ( Database : ser , Table : location
)
username contact received
user_a sip:192.168.1.1:7700
sip:234.234.234.234:1568 ( public ip )
user_b sip:192.168.10.11:7446
sip:192.168.10.1.3112 ( private ip )
user_c sip:192.168.2.1:15647
sip:123.123.123.123:21144 ( public ip )
I tried many times, but the problem is same !
Please help !
tks a lot !
Freeman
_______________________________________
想即時收到新 email 通知？
下載 Yahoo! Messenger http://messenger.yahoo.com.hk
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
有即時通知，收艂
1:47 p.m.
New subject: 標題： Re: [Serusers] [Seruser] GettingStarted04 - RTPProxy Setting Problem !
It's attached. I would have posted it to bugs.sip-router.org, but rtpproxy is a
separate module and should thus be created as a separate project in the bug tracking
system...
g-)
---- Original Message ----
From: Freeman
To: Greger V. Teigre ; serusers(a)lists.iptel.org
Sent: Thursday, June 30, 2005 09:54 AM
Subject: 標題： Re: [Serusers] [Seruser] GettingStarted04 - RTPProxy
Setting Problem !
Greger,
Sorry ! Where i can find the rtpproxy patch ????
tks a lot !
Freeman
"Greger V. Teigre" <greger(a)teigre.com> 說：
To add to Zeus' comment:
rtpproxy *cannot* run on a private IP without a patch I posted a
while back. Search the archives (warning: the patch is outdated and
must now be manually applied).
g-)
---- Original Message ----
From: Freeman
To: serusers(a)lists.iptel.org
Sent: Thursday, June 30, 2005 04:48 AM
Subject: [Serusers] [Seruser] GettingStarted04 - RTPProxy Setting
Problem !
Hi,
I tried to follow the manual "GettingStarted 04 - 2005-05-26"
to create ser.cfg ( for RTPProxy ), i found some error in
"/var/log/messages",
rtpproxy: Starting SER RTP Proxy server: rtpproxy
rtpproxy: .
rc: Starting rtpproxy: succeeded
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: Listening on
ser: udp: 192.168.10.1 [192.168.10.1]:5060
ser: tcp: 192.168.10.1 [192.168.10.1]:5060
ser: Aliases:
ser:
ser: ser startup succeeded
/usr/local/sbin/ser[2353]: Maxfwd module- initializing
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is initially
65535
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is finally
131070 /usr/local/sbin/ser[2373]: INFO: fifo process starting: 2373
/usr/local/sbin/ser[2373]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2373]: SER: open_uac_fifo: fifo server up at
/tmp/ser_fifo...
/usr/local/sbin/ser[2375]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2380]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2381]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2382]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2377]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2383]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2389]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2353]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2388]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2387]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2379]: rtpp_test: RTP proxy found, support for it
enabled
I tried to test the ser in some case : ( using Windows Messenger 5.1
and released all port for ser )
1. "User A ( outside with NAT ) call User B ( same network with ser
)" - User A can't call User B.
2. "User B ( same network with ser ) call User A ( outsid! e with
NAT )" - User B can call User B but No Voice and auto hangup.
3. "User A ( outside with NAT ) call User C ( outside with NAT )"
- User A can't call User C.
I found some information in MySQL ( Database : ser , Table : location
)
username contact received
user_a sip:192.168.1.1:7700
sip:234.234.234.234:1568 ( public ip )
user_b sip:192.168.10.11:7446
sip:192.168.10.1.3112 ( private ip )
user_c sip:192.168.2.1:15647
sip:123.123.123.123:21144 ( public ip )
I tried many times, but the problem is same !
Please help !
tks a lot !
Freeman
_______________________________________
想即時收到新 email 通知？
下載 Yahoo! Messenger http://messenger.yahoo.com.hk
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
有即時通知，收艂
1:52 p.m.
New subject: 標題： Re: 標題： Re: [Serusers] [Seruser] GettingStarted04 - RTPProxy Setting Problem !
Greger,
How can i do with this patch ????
Can you tell me more detail ?
Can the patch help me to make ser behind NAT ?
tka a lot !
Freeman
"Greger V. Teigre" <greger(a)teigre.com> 說：
It's attached. I would have posted it to bugs.sip-router.org, but rtpproxy is a
separate module and should thus be created as a separate project in the bug tracking
system...
g-)
---- Original Message ----
From: Freeman
To: Greger V. Teigre ; serusers(a)lists.iptel.org
Sent: Thursday, June 30, 2005 09:54 AM
Subject: 標題： Re: [Serusers] [Seruser] GettingStarted04 - RTPProxy
Setting Problem !
Greger,
Sorry ! Where i can find the rtpproxy patch ????
tks a lot !
Freeman
"Greger V. Teigre" <greger(a)teigre.com> 說：
To add to Zeus' comment:
rtpproxy *cannot* run on a private IP without a patch I posted a
while back. Search the archives (warning: the patch is outdated and
must now be manually applied).
g-)
---- Original Message ----
From: Freeman
To: serusers(a)lists.iptel.org
Sent: Thursday, June 30, 2005 04:48 AM
Subject: [Serusers] [Seruser] GettingStarted04 - RTPProxy Setting
Problem !
***
../rtpproxy_orig/main.c 2004-08-13 21:04:23.000000000 +0200
--- ./main.c 2004-11-17 18:30:32.000000000 +0100
***************
*** 215,220 ****
--- 215,221 ----
static int umode = 0; /* UDP control mode */
static const char *cmd_sock = CMD_SOCK;
static const char *pid_file = PID_FILE;
+ static char *public_ip = NULL;
/*
* The first address is for external interface, the second one - for
***************
*** 916,924 ****
}
if (lia[0] == NULL || ishostnull(lia[0]))
len += sprintf(cp, "%d\n", lport);
! else
! len += sprintf(cp, "%d %s%s\n", lport, addr2char(lia[0]),
! (lia[0]->sa_family == AF_INET) ? "" : " 6");
doreply:
if (umode == 0) {
write(controlfd, buf, len);
--- 917,931 ----
}
if (lia[0] == NULL || ishostnull(lia[0]))
len += sprintf(cp, "%d\n", lport);
! else {
! if(!public_ip) {
! len += sprintf(cp, "%d %s%s\n", lport, addr2char(lia[0]),
! (lia[0]->sa_family == AF_INET) ? "" : " 6");
! } else {
! len += sprintf(cp, "%d %s%s\n", lport, public_ip,
! (lia[0]->sa_family == AF_INET) ? "" : " 6");
! }
! }
doreply:
if (umode == 0) {
write(controlfd, buf, len);
***************
*** 999,1009 ****
dmode = 0;
! while ((ch = getopt(argc, argv, "vf2Rl:6:s:t:r:p:")) != -1)
switch (ch) {
case 'f':
nodaemon = 1;
break;
case 'l':
bh[0] = optarg;
--- 1006,1020 ----
dmode = 0;
! while ((ch = getopt(argc, argv, "vf2Rl:6:s:t:r:p:i:")) != -1)
switch (ch) {
case 'f':
nodaemon = 1;
break;
+ case 'i':
+ public_ip=(char*) malloc(strlen(optarg)+1);
+ strcpy(public_ip,optarg);
+ break;
case 'l':
bh[0] = optarg;
***************
*** 1014,1020 ****
bmode = 1;
}
break;
-
case '6':
bh6[0] = optarg;
bh6[1] = strchr(bh6[0], '/');
--- 1025,1030 ----
芺笛戙菑穻
Hi,
I tried to follow the manual "GettingStarted 04 - 2005-05-26"
to create ser.cfg ( for RTPProxy ), i found some error in
"/var/log/messages",
rtpproxy: Starting SER RTP Proxy server: rtpproxy
rtpproxy: .
rc: Starting rtpproxy: succeeded
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: Listening on
ser: udp: 192.168.10.1 [192.168.10.1]:5060
ser: tcp: 192.168.10.1 [192.168.10.1]:5060
ser: Aliases:
ser:
ser: ser startup succeeded
/usr/local/sbin/ser[2353]: Maxfwd module- initializing
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is initially
65535
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is finally
131070 /usr/local/sbin/ser[2373]: INFO: fifo process starting: 2373
/usr/local/sbin/ser[2373]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2373]: SER: open_uac_fifo: fifo server up at
/tmp/ser_fifo...
/usr/local/sbin/ser[2375]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2380]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2381]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2382]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2377]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2383]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2389]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2353]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2388]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2387]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2379]: rtpp_test: RTP proxy found, support for it
enabled
I tried to test the ser in some case : ( using Windows Messenger 5.1
and released all port for ser )
1. "User A ( outside with NAT ) call User B ( same network with ser
)" - User A can't call User B.
2. "User B ( same network with ser ) call User A ( outsid! e with
NAT )" - User B can call User B but No Voice and auto hangup.
3. "User A ( outside with NAT ) call User C ( outside with NAT )"
- User A can't call User C.
I found some information in MySQL ( Database : ser , Table : location
)
username contact received
user_a sip:192.168.1.1:7700
sip:234.234.234.234:1568 ( public ip )
user_b sip:192.168.10.11:7446
sip:192.168.10.1.3112 ( private ip )
user_c sip:192.168.2.1:15647
sip:123.123.123.123:21144 ( public ip )
I tried many times, but the problem is same !
Please help !
tks a lot !
Freeman
_______________________________________
想即時收到新 email 通知？
下載 Yahoo! Messenger http://messenger.yahoo.com.hk
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
有即時通知，收艂
1:09 p.m.
Greger,
Sorry ! Where i can find the rtpproxy patch ????
tks a lot !
Freeman
"Greger V. Teigre" <greger(a)teigre.com> 說：
To add to Zeus' comment:
rtpproxy *cannot* run on a private IP without a patch I posted a while back. Search the
archives (warning: the patch is outdated and must now be manually applied).
g-)
---- Original Message ----
From: Freeman
To: serusers(a)lists.iptel.org
Sent: Thursday, June 30, 2005 04:48 AM
Subject: [Serusers] [Seruser] GettingStarted04 - RTPProxy Setting
Problem !
Hi,
I tried to follow the manual "GettingStarted 04 - 2005-05-26"
to create ser.cfg ( for RTPProxy ), i found some error in
"/var/log/messages",
rtpproxy: Starting SER RTP Proxy server: rtpproxy
rtpproxy: .
rc: Starting rtpproxy: succeeded
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: WARNING: fix_socket_list: could not rev. resolve 192.168.10.1
ser: Listening on
ser: udp: 192.168.10.1 [192.168.10.1]:5060
ser: tcp: 192.168.10.1 [192.168.10.1]:5060
ser: Aliases:
ser:
ser: ser startup succeeded
/usr/local/sbin/ser[2353]: Maxfwd module- initializing
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is initially
65535
/usr/local/sbin/ser[2353]: INFO: udp_init: SO_RCVBUF is finally 131070
/usr/local/sbin/ser[2373]: INFO: fifo process starting: 2373
/usr/local/sbin/ser[2373]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2373]: SER: open_uac_fifo: fifo server up at
/tmp/ser_fifo...
/usr/local/sbin/ser[2375]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2380]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2381]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2382]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2377]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2383]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2389]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2353]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2388]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2387]: rtpp_test: RTP proxy found, support for it
enabled
/usr/local/sbin/ser[2379]: rtpp_test: RTP proxy found, support for it
enabled
I tried to test the ser in some case : ( using Windows Messenger 5.1
and released all port for ser )
1. "User A ( outside with NAT ) call User B ( same network with ser )"
- User A can't call User B.
2. "User B ( same network with ser ) call User A ( outside with NAT )"
- User B can call User B but No Voice and auto hangup.
3. "User A ( outside with NAT ) call User C ( outside with NAT )"
- User A can't call User C.
I found some information in MySQL ( Database : ser , Table : location
)
username contact received
user_a sip:192.168.1.1:7700
sip:234.234.234.234:1568 ( public ip )
user_b sip:192.168.10.11:7446
sip:192.168.10.1.3112 ( private ip )
user_c sip:192.168.2.1:15647
sip:123.123.123.123:21144 ( public ip )
I tried many times, but the problem is same !
Please help !
tks a lot !
Freeman
_______________________________________
想即時收到新 email 通知？
下載 Yahoo! Messenger http://messenger.yahoo.com.hk
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
有即時通知，收艂
6895
days inactive
6895
days old
9 comments
3 participants
participants (3)
-
Freeman -
Greger V. Teigre -
Zeus Ng