[Serusers] Registrering trouble. Perhaps Fifo
Martin Kjeldsen
martin.kjeldsen at cuatro.dk
Wed Jun 1 12:26:29 CEST 2005
Sry guys for having troubled you with this problem!
It seems that SUSE wouldn't allow my UDP packets to pass through, only
the TCP. Even though both are allowed in the Firewall.
Thanks anyways for all the feedback.
Martin
Greger V. Teigre wrote:
> I cannot see anything wrong, the debug output is stopped.
> Try changing debug to 7 and fork=no and then start ser with: ser
> (no options).
> g-)
>
> Martin Kjeldsen wrote:
>
>> This is what I get out of the netstat command:
>>
>> osite1:~ # netstat -nlp | grep ser
>> Active Internet connections (only servers)
>> tcp 0 0 212.97.222.xxx:5060 0.0.0.0:*
>> LISTEN 22531/ser
>> udp 0 0 212.97.222.xxx:5060
>> 0.0.0.0:* 22531/ser
>> Active UNIX domain sockets (only servers)
>>
>>
>> So as far as I can see the SER should be listening on the port. Or am
>> I wrong?
>>
>>
>> The output from the command ser -d -d -d -E -D is:
>>
>>
>> ser at osite1:~/running/ser0.9.0/sbin> ser -d -d -d -E -D
>> 0(31063) read 2657387955 from /dev/urandom
>> 0(31063) seeding PRNG with 3774970933
>> 0(31063) test random number 849129338
>> Listening on
>> udp: 212.97.222.xxx [212.97.222.xxx]:5060
>> tcp: 212.97.222.xxx [212.97.222.xxx]:5060
>> Aliases:
>> tcp: osite1:5060
>> tcp: osite1.cuatro.dk:5060
>> udp: osite1:5060
>> udp: osite1.cuatro.dk:5060
>>
>> WARNING: no fork mode
>> stateless - initializing
>> 0(0) Maxfwd module- initializing
>> 0(0) INFO: udp_init: SO_RCVBUF is initially 111616
>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142
>> 2(31071) INFO: fifo process starting: 31071
>> 2(31071) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo... (stops
>> here)
>>
>>
>> Can this have anything to do with SER not recieving/replying to UA
>> messages?
>>
>> And using this ser.cfg:
>>
>> debug=3
>> fork=no
>> log_stderror=yes
>>
>> listen=212.97.222.xxx # put your server IP address here
>> port=5060
>> #children=4
>>
>> dns=no
>> rev_dns=no
>> fifo="/tmp/ser_fifo"
>> fifo_db_url="mysql://ser:password@localhost/ser"
>>
>> loadmodule "/home/ser/running/ser0.9.2/lib/ser/modules/sl.so"
>> loadmodule "/home/ser/running/ser0.9.2/lib/ser/modules/tm.so"
>> loadmodule "/home/ser/running/ser0.9.2/lib/ser/modules/rr.so"
>> loadmodule "/home/ser/running/ser0.9.2/lib/ser/modules/maxfwd.so"
>> loadmodule "/home/ser/running/ser0.9.2/lib/ser/modules/usrloc.so"
>> loadmodule "/home/ser/running/ser0.9.2/lib/ser/modules/registrar.so"
>>
>> modparam("usrloc", "db_mode", 0)
>> modparam("rr", "enable_full_lr", 1)
>>
>> route {
>>
>> #
>> ------------------------------------------------------------------------
>> # Sanity Check Section
>> #
>> ------------------------------------------------------------------------
>> if (!mf_process_maxfwd_header("10")) {
>> sl_send_reply("483", "Too Many Hops");
>> break;
>> };
>>
>> if (msg:len > max_len) {
>> sl_send_reply("513", "Message Overflow");
>> break;
>> };
>>
>> #
>> ------------------------------------------------------------------------
>> # Record Route Section
>> #
>> ------------------------------------------------------------------------
>> if (method!="REGISTER") {
>> record_route();
>> };
>>
>> #
>> ------------------------------------------------------------------------
>> # Loose Route Section
>> #
>> ------------------------------------------------------------------------
>> if (loose_route()) {
>> route(1);
>> break;
>> };
>>
>> #
>> ------------------------------------------------------------------------
>> # Call Type Processing Section
>> #
>> ------------------------------------------------------------------------
>> if (uri!=myself) {
>> route(1);
>> break;
>> };
>>
>> if (uri==myself) {
>>
>> if (method=="REGISTER") {
>> route(2);
>> break;
>> };
>>
>> lookup("aliases");
>> if (uri!=myself) {
>> route(1);
>> break;
>> };
>>
>> if (!lookup("location")) {
>> sl_send_reply("404", "User Not Found");
>> break;
>> };
>>
>> route(1);
>> };
>> }
>>
>> route[1] {
>> #
>> ------------------------------------------------------------------------
>> # Default Message Handler
>> #
>> ------------------------------------------------------------------------
>> if (!t_relay()) {
>> sl_reply_error();
>> };
>> }
>>
>> As simple as that.
>> Again all help is greatly appreciated.
>>
>>
>> Martin
>>
>>
>>
>> Greger V. Teigre wrote:
>>
>>> Ex. netstat -nlp | grep ser will show you at the network level
>>> whether ser is listening.
>>> If so, start ser in debug mode (i.e. stop it and then ser -d -d -d
>>> -E -D) g-)
>>>
>>> Martin Kjeldsen wrote:
>>>
>>>> Thanks.
>>>> Did a tcpdump and apparently the messages do reach the SER. But
>>>> still a very quiet SER :-(.
>>>>
>>>> 2005-05-31 14:29:26.533854 82.180.22.111 -> 212.97.222.xxx SIP
>>>> Request: REGISTER sip:test.cuatro.dk
>>>> 2005-05-31 14:29:28.183699 82.180.22.111 -> 212.97.222.xxx SIP
>>>> Request: REGISTER sip:test.cuatro.dk
>>>> 2005-05-31 14:29:31.194343 82.180.22.111 -> 212.97.222.xxx SIP
>>>> Request: REGISTER sip:test.cuatro.dk
>>>> 2005-05-31 14:29:37.216605 82.180.22.111 -> 212.97.222.xxx SIP
>>>> Request: REGISTER sip:test.cuatro.dk
>>>>
>>>>
>>>> Could the problem still have something to do with the FIFO, or might
>>>> it be some other dependency, as to why the SER never sends any
>>>> response, in this case a 401 Unauthorized?
>>>>
>>>>
>>>> Thanks in advance
>>>> Martin
>>>>
>>>>
>>>>
>>>> Greger V. Teigre wrote:
>>>>
>>>>> Use ngrep or tcpdump port 5060 to see if there is any traffic.
>>>>> g-)
>>>>> Martin Kjeldsen wrote:
>>>>>
>>>>>> Hi there
>>>>>>
>>>>>> I'm having trouble registrering with my SER build (0.9.2), and
>>>>>> using the auth_mysql ser.cfg from ONsip.org. It is as if SER isn't
>>>>>> recieving any of the messages from my UA, and I've been wondering
>>>>>> where I might have gone wrong. One thing I've found different
>>>>>> from a former build (0.8.14), I have up and running is the socks
>>>>>> which SER is listening on. When i do a serctl ps on the 0.9.2 i
>>>>>> get this:
>>>>>>
>>>>>> ser at sipsite:~/running/ser0.9.0/sbin> serctl ps
>>>>>> 200 ok
>>>>>> 0 22531 attendant
>>>>>> 1 22532 fifo server
>>>>>> 2 22533 receiver child=0 sock= 212.97.222.xxx:5060
>>>>>> 3 22534 receiver child=1 sock= 212.97.222.xxx:5060
>>>>>> 4 22535 receiver child=2 sock= 212.97.222.xxx:5060
>>>>>> 5 22536 receiver child=3 sock= 212.97.222.xxx:5060
>>>>>> 6 22537 timer
>>>>>> 7 22538 tcp receiver
>>>>>> 8 22539 tcp receiver
>>>>>> 9 22540 tcp receiver
>>>>>> 10 22541 tcp receiver
>>>>>> 11 22542 tcp main process
>>>>>>
>>>>>>
>>>>>> And as far as I can see the same command on 0.8.14 yields almost
>>>>>> the same output, except that the sock has a number like '0' and a
>>>>>> @ sign is between scok and ip (eg: sock=0 @ ip-adress)! Can this
>>>>>> be the cause of my troubles?
>>>>>> I'm afraid that I'm not that much into Unix and Sockets!
>>>>>>
>>>>>> Any and all help will be greatly appreciated!
>>>>>>
>>>>>>
>>>>>> Kind regards
>>>>>> Martin
>>>>>>
>>>>>> _______________________________________________
>>>>>> Serusers mailing list
>>>>>> serusers at lists.iptel.org
>>>>>> http://lists.iptel.org/mailman/listinfo/serusers
>>>>>
>
--
Med venlig hilsen / Kind Regards
Martin Kjeldsen
Cuatro-Group P/S (4G)
Hindegade 3, DK-1303 København K
Tel: (+45) 82 35 65 00
Fax: (+45) 82 35 65 65
Mob: (+45) 60 64 65 87
Url: http://www.cuatro.dk
More information about the sr-users
mailing list