That's pretty much the end of startup, actually :-). The rest starts jamming when you get connections to port 5060. You could debug = 4 to see more output if you'd like.. Keep in mind that SER is by no means "intelligent", especially without modules, *you* tell it what to listen for and what to say via the config file. ie: without a routing statement the proxy will literally do nothing.
I would recommend starting out with nathelper.cfg located in the src sample directory, that actually works from default for local user routing. Forwarding to Asterisk (,etc..) is another story, see if you get all that working first and then move on. I made the mistake of trying to do too much without knowing how the config worked, the result I had was often infinite loops that would crash SER and Asterisk.
Matt
-----Original Message----- From: Tareq Siraj [mailto:to_tareq@yahoo.com] Sent: Thursday, December 02, 2004 8:38 AM To: serusers@lists.iptel.org Subject: [Serusers] SER stops after connecting to RTP Proxy
Hi all, Its me again ... I got the RTP proxy thing working ... SER connects to RTPProxy ... then its stuck there ... doesnt proceed. the console log i get is like this:
Listening on 192.168.1.21 [192.168.1.21]:5060 Aliases: machinename.localdomain:5060 machinename:* WARNING: no fork mode stateless - initializing Maxfwd module- initializing 0(8908) mod_init(): Database connection opened successfuly textops - initializing 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 0(0) INFO: udp_init: SO_RCVBUF is finally 221184 2(0) INFO: fifo process starting: 8912 1(8910) rtpp_test: RTP proxy found, support for it enabled 2(8912) rtpp_test: RTP proxy found, support for it enabled 2(8912) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo... 0(8908) rtpp_test: RTP proxy found, support for it enabled 1(8910) 2(8912) INFO: signal 15 received
Thanks in advance. Any pointer would be appreciated.
- Tareq
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Thanks man... i am writing from home.. so cant test it right now ... i'll look @ nathelper.cfg and also the debug level is a good idea... I'll try that. Thanks again.
- tareq
--- Matt Schulte mschulte@netlogic.net wrote:
That's pretty much the end of startup, actually :-). The rest starts jamming when you get connections to port 5060. You could debug = 4 to see more output if you'd like.. Keep in mind that SER is by no means "intelligent", especially without modules, *you* tell it what to listen for and what to say via the config file. ie: without a routing statement the proxy will literally do nothing.
I would recommend starting out with nathelper.cfg located in the src sample directory, that actually works from default for local user routing. Forwarding to Asterisk (,etc..) is another story, see if you get all that working first and then move on. I made the mistake of trying to do too much without knowing how the config worked, the result I had was often infinite loops that would crash SER and Asterisk.
Matt
-----Original Message----- From: Tareq Siraj [mailto:to_tareq@yahoo.com] Sent: Thursday, December 02, 2004 8:38 AM To: serusers@lists.iptel.org Subject: [Serusers] SER stops after connecting to RTP Proxy
Hi all, Its me again ... I got the RTP proxy thing working ... SER connects to RTPProxy ... then its stuck there ... doesnt proceed. the console log i get is like this:
Listening on 192.168.1.21 [192.168.1.21]:5060 Aliases: machinename.localdomain:5060 machinename:* WARNING: no fork mode stateless - initializing Maxfwd module- initializing 0(8908) mod_init(): Database connection opened successfuly textops - initializing 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 0(0) INFO: udp_init: SO_RCVBUF is finally 221184 2(0) INFO: fifo process starting: 8912 1(8910) rtpp_test: RTP proxy found, support for it enabled 2(8912) rtpp_test: RTP proxy found, support for it enabled 2(8912) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo... 0(8908) rtpp_test: RTP proxy found, support for it enabled 1(8910) 2(8912) INFO: signal 15 received
Thanks in advance. Any pointer would be appreciated.
- Tareq
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
__________________________________ Do you Yahoo!? All your favorites on one personal page � Try My Yahoo! http://my.yahoo.com
If you have rtpproxy behind a NAT, rtpproxy will send its private address to nathelper for rewriting. I wrote an rtpproxy patch for a test setup running behind NAT. I just recently posted it to this forum. ser should work fine behind NAT, as long as you make sure to have both private and public IPs as aliases (you can into loops...) g-)
Tareq Siraj wrote:
Thanks man... i am writing from home.. so cant test it right now ... i'll look @ nathelper.cfg and also the debug level is a good idea... I'll try that. Thanks again.
- tareq
--- Matt Schulte mschulte@netlogic.net wrote:
That's pretty much the end of startup, actually :-). The rest starts jamming when you get connections to port 5060. You could debug = 4 to see more output if you'd like.. Keep in mind that SER is by no means "intelligent", especially without modules, *you* tell it what to listen for and what to say via the config file. ie: without a routing statement the proxy will literally do nothing.
I would recommend starting out with nathelper.cfg located in the src sample directory, that actually works from default for local user routing. Forwarding to Asterisk (,etc..) is another story, see if you get all that working first and then move on. I made the mistake of trying to do too much without knowing how the config worked, the result I had was often infinite loops that would crash SER and Asterisk.
Matt
-----Original Message----- From: Tareq Siraj [mailto:to_tareq@yahoo.com] Sent: Thursday, December 02, 2004 8:38 AM To: serusers@lists.iptel.org Subject: [Serusers] SER stops after connecting to RTP Proxy
Hi all, Its me again ... I got the RTP proxy thing working ... SER connects to RTPProxy ... then its stuck there ... doesnt proceed. the console log i get is like this:
Listening on 192.168.1.21 [192.168.1.21]:5060 Aliases: machinename.localdomain:5060 machinename:* WARNING: no fork mode stateless - initializing Maxfwd module- initializing 0(8908) mod_init(): Database connection opened successfuly textops - initializing 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 0(0) INFO: udp_init: SO_RCVBUF is finally 221184 2(0) INFO: fifo process starting: 8912 1(8910) rtpp_test: RTP proxy found, support for it enabled 2(8912) rtpp_test: RTP proxy found, support for it enabled 2(8912) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo... 0(8908) rtpp_test: RTP proxy found, support for it enabled 1(8910) 2(8912) INFO: signal 15 received
Thanks in advance. Any pointer would be appreciated.
- Tareq
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Do you Yahoo!? All your favorites on one personal page - Try My Yahoo! http://my.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Greger V. Teigre -
Matt Schulte -
Tareq Siraj