[SR-Users] strange behavior when trying to reach PSTN gateway via TCP

Dmitry Petrakoff dimon at dprs-consulting.com
Wed Nov 16 09:15:16 CET 2011


 Hi Daniel-Constantin!

Many thanks for your reply
Sorry for the wrong output from DEBUG.
I took it when such directives were set in config:

#disable_tcp=yes
udp_mtu=1300
udp_mtu_try_proto=TCP

Actually, that host 10.198.3.100 works just fine via UDP.

But when those directives were enabled, next INVITE has gone there via
TCP and the error was the same as with Lync.

More over. Today I run dispatcher module as "stupid" pinger. And again,
faced with the same error.

Now it is output from   kamctl ps:

Process::  ID=0 PID=40677 Type=attendant
Process::  ID=1 PID=40678 Type=udp receiver child=0 sock=1.2.3.4:5060
Process::  ID=2 PID=40679 Type=udp receiver child=1 sock=1.2.3.4:5060
Process::  ID=3 PID=40680 Type=udp receiver child=2 sock=1.2.3.4:5060
Process::  ID=4 PID=40681 Type=udp receiver child=3 sock=1.2.3.4:5060
Process::  ID=5 PID=40682 Type=udp receiver child=0 sock=127.0.0.1:5060
Process::  ID=6 PID=40683 Type=udp receiver child=1 sock=127.0.0.1:5060
Process::  ID=7 PID=40684 Type=udp receiver child=2 sock=127.0.0.1:5060
Process::  ID=8 PID=40685 Type=udp receiver child=3 sock=127.0.0.1:5060
Process::  ID=9 PID=40686 Type=udp receiver child=0 sock=10.200.245.250:5060
Process::  ID=10 PID=40687 Type=udp receiver child=1
sock=10.200.245.250:5060
Process::  ID=11 PID=40688 Type=udp receiver child=2
sock=10.200.245.250:5060
Process::  ID=12 PID=40689 Type=udp receiver child=3
sock=10.200.245.250:5060
Process::  ID=13 PID=40690 Type=slow timer
Process::  ID=14 PID=40691 Type=timer
Process::  ID=15 PID=40692 Type=MI FIFO
Process::  ID=16 PID=40693 Type=ctl handler
Process::  ID=17 PID=40694 Type=TIMER NH
Process::  ID=18 PID=40695 Type=tcp receiver child=0
Process::  ID=19 PID=40696 Type=tcp receiver child=1
Process::  ID=20 PID=40697 Type=tcp receiver child=2
Process::  ID=21 PID=40698 Type=tcp receiver child=3
Process::  ID=22 PID=40699 Type=tcp main process

As you can see, TCP is present and working for receiving. And we were
able to receive INVITE from Lync via TCP.


Now, part of newly added dispatcher functionality:

loadmodule "dispatcher.so"
modparam("dispatcher", "db_url", DBURL);
modparam("dispatcher", "ds_ping_from", "sip:openser at 10.200.245.250");
modparam("dispatcher", "ds_ping_interval", 5);
modparam("dispatcher", "ds_probing_mode", 1);

and table:

mysql> select * from dispatcher;
+----+-------+---------------------------------------+-------+----------+-------+-------------+
| id | setid | destination                           | flags | priority
| attrs | description |
+----+-------+---------------------------------------+-------+----------+-------+-------------+
|  1 |     1 | sip:10.200.253.186:5068;transport=tcp |     0 |        0
|       | Lync-Test   |
+----+-------+---------------------------------------+-------+----------+-------+-------------+



corresponding tcp options are:

#disable_tcp=yes
tcp_children=4

and another, probably important, option which I forgot to inform about:

mhomed=1

And what I'm getting.



More information about the sr-users mailing list