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@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@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@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@lists.iptel.org
>>
http://lists.iptel.org/mailman/listinfo/serusers
>
有即時通知,收艂