sr-users November 2007

sr-users@lists.kamailio.org

138 participants
248 discussions

Start a nNew thread

[Serusers] Please join me @ Sarfu

by Sarfaraz Chougule

16 years, 5 months

[Serusers] Please join me @ Sarfu

by Sarfaraz Chougule

16 years, 5 months

Re: [Serusers] nathelper doesn't ping registered users

by Jiri Kuthan

Hi Tomasz, well it could be that reusing an existing config and commiting than your specific changes to it would save you quite some laborous exercises rather than writing it from scratch.... http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/etc/ser-oob.cfg?re… The lines in question are (out of which I think you are missing the registrar params) FLAG_NAT : 3, # the UAC is behind a NAT ... # identify natted contacts using a flag modparam("registrar", "load_nat_flag", "FLAG_NAT") modparam("registrar", "save_nat_flag", "FLAG_NAT") ... modparam("rr", "cookie_filter", "(account|uac_nat)") ... modparam("nathelper", "ping_nated_only", 1 ) # if this option is not set, simple 4-bytes ping is sent modparam("nathelper", "natping_method", "OPTIONS" ) #temporary statefull natping test (only in future versions) #modparam("nathelper", "natping_stateful", 1) ... setflag(FLAG_NAT); -jiri At 22:20 24/11/2007, Tomasz Zieleniewski wrote: >I'm sorry for the CC >here is my config: > >debug=3 # debug level (cmd line: -dddddddddd) >memdbg=5 >memlog=5 >log_facility=LOG_LOCAL0 >fork=yes >log_stderror=no >check_via=yes # (cmd. line: -v) >dns=no # (cmd. line: -r) >rev_dns=no # (cmd. line: -R) >port=5060 >tls_port_no=5061 >children=4 >user=ser >group=ser >mhomed=yes >disable_tcp=no >tcp_accept_aliases=yes >enable_tls=no >sip_warning=0 >reply_to_via=no >alias="voip.touk.pl" > >dns_retr_time=1 >dns_retr_no=1 >dns_servers_no=1 >dns_use_search_list=no >dns_try_ipv6=no ># dns cache & failover >use_dns_cache=on >use_dns_failover=on ># dns_cache_flags=0 >dns_cache_negative_ttl=300 >dns_cache_min_ttl=60 >dns_cache_max_ttl=86400 # 1 day >dns_cache_mem=2048 # 2 MB >dns_cache_gc_interval=60 > >tcp_connection_lifetime=3600 >tcp_max_connections=2048 >tcp_connect_timeout=1 > >loadmodule ... >.... > ># specify the path to you database here >modparam("acc_db|auth_db|avp_db|domain|gflags|usrloc|uri_db|speeddial|msilo|lcr", >"db_url", "mysql://ser:ser@localhost/ser") > ># -- usrloc params -- >modparam("usrloc", "db_mode", 1) > ># -- registrar params -- >modparam("registrar", "default_expires", 300) >modparam("registrar", "min_expires", 60) >modparam("registrar", "max_expires", 300) >modparam("registrar", "append_branches", 1) >modparam("registrar", "received_param", "rcv") >modparam("registrar", "max_contacts", 2) > ># -- auth params -- >modparam("auth_db", "calculate_ha1", yes) >modparam("auth_db", "password_column", "password") > ># -- rr params -- >modparam("rr", "enable_full_lr", 1) >modparam("rr", "cookie_filter", "uac_nat") >modparam("rr", "cookie_secret", "secret") >modparam("rr", "user_part_avp", "route_user") >modparam("rr", "next_route_avp", "route_next") > ># -- gflags params -- >modparam("gflags", "load_global_attrs", 1) > ># -- domain params -- >modparam("domain", "load_domain_attrs", 1) > ># -- ctl params -- >modparam("ctl", "binrpc", "unixs:/tmp/ser-bsp_ctl") >modparam("ctl", "fifo", "fifo:/tmp/ser-bsp_fifo") ># modparam("ctl", "binrpc", "tcp:localhost:2046") >modparam("ctl", "mode", 0777) > ># -- tm params -- >modparam("tm", "restart_fr_on_each_reply", 1) > ># -- auth_radius params -- >modparam("auth_radius", "radius_config", >"/usr/local/etc/radiusclient-ng/radiusclient.conf") >modparam("auth_radius", "service_type", 15) > ># -- options params -- >modparam("options", "accept", "*/*") >modparam("options", "accept_encoding", "") >modparam("options", "accept_language", "en") > ># -- ratelimit params -- >modparam("ratelimit","timer_interval", 10) >modparam("ratelimit","invite_limit", 100) >modparam("ratelimit","register_limit", 100) >modparam("ratelimit","subscribe_limit", 100) > ># -- xmlrpc params -- >modparam("xmlrpc", "route","RPC") > ># -- nathelper params -- >modparam("nathelper", "natping_interval", 20) >modparam("nathelper", "ping_nated_only", 0) >modparam("nathelper", "rtpproxy_disable", 1) >modparam("nathelper", "tcpping_crlf", 1) > ># -- tls params -- >modparam("tls", "config", "/home/ser/ser/ca/tls-bsp.cfg") >modparam("tls", "tls_force_run", 0) >modparam("tls", "tls_log",3) >modparam("tls", "handshake_timeout", 10) >modparam("tls", "send_timeout", 10) >modparam("tls", "tls_disable_compression", 0) >#modparam("tls", "private_key", "/etc/certs/key.pem") >#modparam("tls", "certificate", "/etc/certs/cert.pem") >#modparam("tls", "ca_list", "/etc/certs/ca_list.pem") >#modparam("tls", "require_certificate", 0) >#modparam("tls", "verify_certificate", 1) >#modparam("tls", "tls_method", "TLSv1") > >route{ >... >} > >On Nov 24, 2007 9:35 PM, Atle Samuelsen <clona(a)cyberhouse.no> wrote: >> Hi, >> >> Always CC the list. >> >> then I dont know.. post your full config so people can see if they see >> something >> -A >> >> * Tomasz Zieleniewski <tzieleniewski(a)gmail.com> [071124 20:38]: >> >> > Hi, >> > >> > I had that parameter set to 0, but still no udp packets... >> > >> > On Nov 24, 2007 6:43 PM, Atle Samuelsen <clona(a)cyberhouse.no> wrote: >> > > * Tomasz Zieleniewski <tzieleniewski(a)gmail.com> [071124 16:50]: >> > > >> > > > HI, >> > > > >> > > > I have the following nathelper settings: >> > > > modparam("nathelper", "natping_interval", 20) >> > > > modparam("nathelper", "ping_nated_only", 1) >> > > > modparam("nathelper", "rtpproxy_disable", 1) >> > > > modparam("nathelper", "tcpping_crlf", 1) >> > > > >> > > > But i cant see any udp packets being sent to registered users. >> > > > Please point me what did I miss. >> > > >> > > Hi, >> > > >> > > without seeing any more of your config, I'm guessing that you do not set >> > > the natflag, so if you change ping_nated_only to 0, I think you will see >> > > some udp packets. >> > > >> > > - Atle >> > > (shot in the whild world of sip) >> > > >> > > >> > > > >> > > > Best >> > > > Tomasz >> > > > _______________________________________________ >> > > > Serusers mailing list >> > > > Serusers(a)lists.iptel.org >> > > > http://lists.iptel.org/mailman/listinfo/serusers >> > > >> >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

16 years, 5 months

Re: [Serusers] nathelper doesn't ping registered users

by Atle Samuelsen

Hi, Always CC the list. then I dont know.. post your full config so people can see if they see something -A * Tomasz Zieleniewski <tzieleniewski(a)gmail.com> [071124 20:38]: > Hi, > > I had that parameter set to 0, but still no udp packets... > > On Nov 24, 2007 6:43 PM, Atle Samuelsen <clona(a)cyberhouse.no> wrote: > > * Tomasz Zieleniewski <tzieleniewski(a)gmail.com> [071124 16:50]: > > > > > HI, > > > > > > I have the following nathelper settings: > > > modparam("nathelper", "natping_interval", 20) > > > modparam("nathelper", "ping_nated_only", 1) > > > modparam("nathelper", "rtpproxy_disable", 1) > > > modparam("nathelper", "tcpping_crlf", 1) > > > > > > But i cant see any udp packets being sent to registered users. > > > Please point me what did I miss. > > > > Hi, > > > > without seeing any more of your config, I'm guessing that you do not set > > the natflag, so if you change ping_nated_only to 0, I think you will see > > some udp packets. > > > > - Atle > > (shot in the whild world of sip) > > > > > > > > > > Best > > > Tomasz > > > _______________________________________________ > > > Serusers mailing list > > > Serusers(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serusers > >

16 years, 5 months

[Serusers] nathelper doesn't ping registered users

by Tomasz Zieleniewski

HI, I have the following nathelper settings: modparam("nathelper", "natping_interval", 20) modparam("nathelper", "ping_nated_only", 1) modparam("nathelper", "rtpproxy_disable", 1) modparam("nathelper", "tcpping_crlf", 1) But i cant see any udp packets being sent to registered users. Please point me what did I miss. Best Tomasz

16 years, 5 months

Re: [Serusers] Can SER support 3-way Conference

by roayu

Hi Stefan, The following are the output I got after re-run the 'make install' on SEMS. [root@localhost sems-0.10.0-rc2]# make install make[1]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ann_b2b' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ann_b2b' make[3]: Nothing to be done for `deps'. make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ann_b2b' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ann_b2b' g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"' -DOS='"linux"' -c AnnounceB2B.cpp -o AnnounceB2B.o make[3]: g++: Command not found make[3]: *** [AnnounceB2B.o] Error 127 make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ann_b2b' make[2]: [all] Error 2 (ignored) mkdir -p /usr/local/lib/sems/audio/ann_b2b mkdir -p /usr/local/lib/sems/plug-in/ touch /usr/local/lib/sems/plug-in//ann_b2b.so ; \ install -m 755 ann_b2b.so /usr/local/lib/sems/plug-in/ install: cannot stat `ann_b2b.so': No such file or directory make[2]: *** [install] Error 1 make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ann_b2b' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/announcement' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/announcement' make[3]: Nothing to be done for `deps'. make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/announcement' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/announcement' g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"' -DOS='"linux"' -c Announcement.cpp -o Announcement.o make[3]: g++: Command not found make[3]: *** [Announcement.o] Error 127 make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/announcement' make[2]: [all] Error 2 (ignored) mkdir -p /usr/local/lib/sems/audio/announcement mkdir -p /usr/local/lib/sems/plug-in/ touch /usr/local/lib/sems/plug-in//announcement.so ; \ install -m 755 announcement.so /usr/local/lib/sems/plug-in/ install: cannot stat `announcement.so': No such file or directory make[2]: *** [install] Error 1 make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/announcement' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/announce_transfer' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/announce_transfer' make[3]: Nothing to be done for `deps'. make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/announce_transfer' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/announce_transfer' g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"' -DOS='"linux"' -c AnnounceTransfer.cpp -o AnnounceTransfer.o make[3]: g++: Command not found make[3]: *** [AnnounceTransfer.o] Error 127 make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/announce_transfer' make[2]: [all] Error 2 (ignored) mkdir -p /usr/local/lib/sems/audio/announce_transfer mkdir -p /usr/local/lib/sems/plug-in/ touch /usr/local/lib/sems/plug-in//announce_transfer.so ; \ install -m 755 announce_transfer.so /usr/local/lib/sems/plug-in/ install: cannot stat `announce_transfer.so': No such file or directory make[2]: *** [install] Error 1 make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/announce_transfer' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/conf_auth' find . -iname "*\.pyc" -o -iname "*\.py~" | xargs rm -f rm -f sems-app-conf_auth*.tar.gz python2.4 ../ivr/py_comp -q . install -d /"/usr/local/lib/sems/ivr" install -m "644" -o "root" -g "root" *.pyc /"/usr/local/lib/sems/ivr" install -d /"/usr/local/lib/sems/ivr"/. install -m "644" -o "root" -g "root" ./*.pyc /"/usr/local/lib/sems/ivr"/. make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/conf_auth' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/conference' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/conference' make[3]: Nothing to be done for `deps'. make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/conference' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/conference' g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"' -DOS='"linux"' -c AmRingTone.cpp -o AmRingTone.o make[3]: g++: Command not found make[3]: *** [AmRingTone.o] Error 127 make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/conference' make[2]: [all] Error 2 (ignored) mkdir -p /usr/local/lib/sems/audio/conference mkdir -p /usr/local/lib/sems/plug-in/ touch /usr/local/lib/sems/plug-in//conference.so ; \ install -m 755 conference.so /usr/local/lib/sems/plug-in/ install: cannot stat `conference.so': No such file or directory make[2]: *** [install] Error 1 make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/conference' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/early_announce' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/early_announce' make[3]: Nothing to be done for `deps'. make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/early_announce' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/early_announce' g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"' -DOS='"linux"' -c EarlyAnnounce.cpp -o EarlyAnnounce.o make[3]: g++: Command not found make[3]: *** [EarlyAnnounce.o] Error 127 make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/early_announce' make[2]: [all] Error 2 (ignored) mkdir -p /usr/local/lib/sems/plug-in/ touch /usr/local/lib/sems/plug-in//early_announce.so ; \ install -m 755 early_announce.so /usr/local/lib/sems/plug-in/ install: cannot stat `early_announce.so': No such file or directory make[2]: *** [install] Error 1 make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/early_announce' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr' python2.4 py_comp -l -q py &&\ cp py/*.pyc ../../core/lib make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr' g++ -MM IvrDialogBase.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"' -DOS='"linux"' -I/usr/include/python2.4 -fno-strict-aliasing > IvrDialogBase.d /bin/sh: g++: command not found make[3]: *** [IvrDialogBase.d] Error 127 make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr' make[2]: [all] Error 2 (ignored) echo "Installing Python object files..." Installing Python object files... for f in log.pyc ; do \ if [ -n "py/$f" ]; then \ touch /usr/local/lib/sems/plug-in//$f; \ install -m 755 py/$f /usr/local/lib/sems/plug-in//$f; \ fi ; \ done mkdir -p /usr/local/lib/sems/plug-in/ touch /usr/local/lib/sems/plug-in//ivr.so ; \ install -m 755 ivr.so /usr/local/lib/sems/plug-in/ install: cannot stat `ivr.so': No such file or directory make[2]: *** [install] Error 1 make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/mailbox' find . -iname "*\.pyc" -o -iname "*\.py~" | xargs rm -f rm -f sems-app-mailbox*.tar.gz python2.4 ../ivr/py_comp -q . install -d /"/usr/local/lib/sems/ivr" install -m "644" -o "root" -g "root" *.pyc /"/usr/local/lib/sems/ivr" install -d /"/usr/local/lib/sems/ivr"/imap_mailbox install -m "644" -o "root" -g "root" imap_mailbox/*.pyc /"/usr/local/lib/sems/ivr"/imap_mailbox make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/mailbox' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/pin_collect' find . -iname "*\.pyc" -o -iname "*\.py~" | xargs rm -f rm -f sems-app-pincollect*.tar.gz python2.4 ../ivr/py_comp -q . install -d /"/usr/local/lib/sems/ivr" install -m "644" -o "root" -g "root" *.pyc /"/usr/local/lib/sems/ivr" install -d /"/usr/local/lib/sems/ivr"/. install -m "644" -o "root" -g "root" ./*.pyc /"/usr/local/lib/sems/ivr"/. make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/pin_collect' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/py_sems' make[2]: *** No rule to make target `python_files', needed by `all'. Stop. make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/py_sems' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/registrar_client' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/registrar_client' make[3]: Nothing to be done for `deps'. make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/registrar_client' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/registrar_client' g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"' -DOS='"linux"' -c ContactInfo.cpp -o ContactInfo.o make[3]: g++: Command not found make[3]: *** [ContactInfo.o] Error 127 make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/registrar_client' make[2]: [all] Error 2 (ignored) mkdir -p /usr/local/lib/sems/plug-in/ touch /usr/local/lib/sems/plug-in//registrar_client.so ; \ install -m 755 registrar_client.so /usr/local/lib/sems/plug-in/ install: cannot stat `registrar_client.so': No such file or directory make[2]: *** [install] Error 1 make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/registrar_client' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/voicemail' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/voicemail' make[3]: Nothing to be done for `deps'. make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/voicemail' make[3]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/voicemail' g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"' -DOS='"linux"' -c AnswerMachine.cpp -o AnswerMachine.o make[3]: g++: Command not found make[3]: *** [AnswerMachine.o] Error 127 make[3]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/voicemail' make[2]: [all] Error 2 (ignored) mkdir -p /usr/local/etc/sems/ touch /usr/local/etc/sems/default.template.sample install -m 644 default.template.sample /usr/local/etc/sems/ if [ ! -f /usr/local/etc/sems/default.template ]; then \ cp -f /usr/local/etc/sems/default.template.sample \ /usr/local/etc/sems/default.template; \ fi mkdir -p /usr/local/lib/sems/audio/voicemail mkdir -p /usr/local/lib/sems/plug-in/ touch /usr/local/lib/sems/plug-in//voicemail.so ; \ install -m 755 voicemail.so /usr/local/lib/sems/plug-in/ install: cannot stat `voicemail.so': No such file or directory make[2]: *** [install] Error 1 make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/voicemail' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ann_b2b' mkdir -p /usr/local/etc/sems/etc installing etc/ann_b2b.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ann_b2b' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/announcement' mkdir -p /usr/local/etc/sems/etc installing etc/announcement.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/announcement' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/announce_transfer' mkdir -p /usr/local/etc/sems/etc installing etc/announce_transfer.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/announce_transfer' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/conf_auth' mkdir -p /usr/local/etc/sems/etc installing etc/conf_auth.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/conf_auth' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/conference' mkdir -p /usr/local/etc/sems/etc installing etc/conference.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/conference' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/early_announce' mkdir -p /usr/local/etc/sems/etc installing etc/early_announce.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/early_announce' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr' mkdir -p /usr/local/etc/sems/etc installing etc/ivr.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/mailbox' mkdir -p /usr/local/etc/sems/etc installing etc/mailbox.conf installing etc/mailbox_query.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/mailbox' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/pin_collect' mkdir -p /usr/local/etc/sems/etc installing etc/pin_collect.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/pin_collect' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/py_sems' mkdir -p /usr/local/etc/sems/etc installing etc/py_sems.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/py_sems' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/registrar_client' mkdir -p /usr/local/etc/sems/etc make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/registrar_client' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/voicemail' mkdir -p /usr/local/etc/sems/etc installing etc/voicemail.conf make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/voicemail' make[1]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps' make[1]: Entering directory `/usr/local/src/sems-0.10.0-rc2/core' make[2]: Entering directory `/usr/local/src/sems-0.10.0-rc2/core' g++ -MM AmAudio.cpp -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"' -DOS='"linux"' > AmAudio.d /bin/sh: g++: command not found make[2]: *** [AmAudio.d] Error 127 make[2]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/core' make[1]: [all] Error 2 (ignored) sed -e "s#/usr/.*lib/sems/audio/#/usr/local/lib/sems/audio/#g" \ -e "s#/usr/.*lib/sems/plug-in/#/usr/local/lib/sems/plug-in/#g" \ -e "s#/usr/.*etc/sems#/usr/local/etc/sems/#g" \ < sems.conf.sample > /usr/local/etc/sems/sems.conf.default chmod 644 /usr/local/etc/sems/sems.conf.default if [ ! -f /usr/local/etc/sems/sems.conf ]; then \ cp -f /usr/local/etc/sems/sems.conf.default \ /usr/local/etc/sems/sems.conf; \ fi touch /usr/local/sbin/sems install -m 755 sems /usr/local/sbin/ install: cannot stat `sems': No such file or directory make[1]: *** [install-bin] Error 1 make[1]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/core' Thanks. Roa Yu :) -----Original Message----- From: Stefan Sayer [mailto:stefan.sayer@iptego.de] Sent: Friday, November 23, 2007 6:32 PM To: roayu Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Can SER support 3-way Conference Hello, can you re-run 'make install' in sems' source directory, and post the output? Thanks Stefan roayu wrote: > Hi Ram! > > I've installed SER (sip stack) and SEMS. I managed to start both SER but I > failed to start SEMS. > > I got the following error message: > "/usr/local/sbin/sems : Permission denied" > > Then I found that the permission for /usr/local/sbin/sems is not 755 and the > file size of it is 0 (zero). > > Why am I having this error message? Can anyone there tell me why? > > Thanks. > > Roa Yu :) > > > -----Original Message----- > From: ram [mailto:talk2ram@gmail.com] > Sent: Wednesday, November 21, 2007 9:06 PM > To: roayu > Subject: Re: [Serusers] Can SER support 3-way Conference > > On Nov 20, 2007 8:39 AM, roayu <roayu(a)ctisys.net> wrote: >> >> >> Hi there, >> >> >> >> Can SER alone support 3-way Conference w/o integrate with other >> applications? >> >> >> > > Hi > > SER is proxy not a Media gateway > > Look at SEM or ASTERISK for that > > ram > _______________________________________________ > Serusers mailing list > Serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers -- Stefan Sayer VoIP Services stefan.sayer(a)iptego.de www.iptego.de iptego GmbH Am Borsigturm 40 13507 Berlin Germany Amtsgericht Charlottenburg, HRB 101010 Geschaeftsfuehrer: Alexander Hoffmann

16 years, 5 months

[OpenSER-Users] A suggestion for 1.3 nathelper

by Robert Dyck

When I started using openser I used a patched version of 1.0 nathelper. This patch created two formats for fix_nated_contact. There was the original format -- fix_nated_contact() and the new format fix_nated_contact(1.2.3.4). The original format appears to be useful for service providers. The new format is useful when you are using openser as an ALG for a home or small office phone system. The contact gets mangled before being sent to the registrar. Because redoing the patch for each new version of openser that comes along is silly, I had previously asked the list for an alternative. Someone suggested using encode_contact from the mangler modules. This works but I think it is sub-optimal when you have multiple phones with the same user name. Each one creates its own contact with the registrar. The service providers server does the forking and there is a lot of excess messaging with the INVITEs and CANCELs when the call is answered by one of the phones. With fix_nated_contact(1.2.3.4) there is only one location registered and the local openser does the forking and the CANCELs are confined to the LAN. Comments? Rob

16 years, 5 months

[OpenSER-Users] In 1.3 how to use set_rtp_proxy_set

by Robert Dyck

If I have only one rtp proxy should I use set_rtp_proxy_set("0")? I think openser should be smart enough to figure it out if there is only one rtp proxy. It looks like there is a cut and paste error in the 1.3 nathelper wiki. 1.6.3. set_rtp_proxy_set() Sets the Id of the rtpproxy set to be used for the next [un]force_rtp_proxy() command. This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE, BRANCH_ROUTE. Example 1-17. fix_nated_contact usage ... set_rtp_proxy_set("2"); force_rtp_proxy(); Rob ...

16 years, 5 months

Re: [Serusers] [Serdev] [Tracker] Created: (SER-332) tcp branching error

by Tomasz Zieleniewski

once again because to big attachments:) On Nov 23, 2007 11:48 AM, Tomasz Zieleniewski <tzieleniewski(a)gmail.com> wrote: > sorry I forgot to place the attachments > > > On Nov 23, 2007 11:47 AM, Tomasz Zieleniewski <tzieleniewski(a)gmail.com> wrote: > > Hi, > > > > Some more debug information: > > > > User contacts: > > ser@sen:~/ser/ser-2.0/ssp$ ./serctl/ser_ctl usrloc show touk(a)voip.rd.touk.pl > > sip:touk@192.168.0.164:1338;rinstance=191d670c84591ea3;transport=TCP 3330 -1.0 > > sip:touk@192.168.0.164:1348;rinstance=e51fd20db73fc732;transport=TCP 3405 -1.0 > > > > Contents of the location table: > > mysql> select * from location where uid like 'touk@%'; > > +----------------------+--------------------------+----------------------------------------------------------------------+----------+---------------------+----+----------------------------------------------+------+-------+----------------------------------+----------+ > > | uid | aor | contact > > | received | expires > > | q | callid | cseq > > | flags | user_agent | instance | > > +----------------------+--------------------------+----------------------------------------------------------------------+----------+---------------------+----+----------------------------------------------+------+-------+----------------------------------+----------+ > > | touk(a)voip.rd.touk.pl | sip:touk@voip.rd.touk.pl | > > sip:touk@192.168.0.164:1338;rinstance=191d670c84591ea3;transport=TCP | > > NULL | 2007-11-23 11:17:03 | -1 | > > MTQ1ZWZmZWE2MWIxZjViYmVkNzZlNmU0YTEwNjRmMTA. | 4 | 0 | X-Lite > > release 1011s stamp 41150 | NULL | > > | touk(a)voip.rd.touk.pl | sip:touk@voip.rd.touk.pl | > > sip:touk@192.168.0.164:1348;rinstance=e51fd20db73fc732;transport=TCP | > > NULL | 2007-11-23 11:18:18 | -1 | > > NDk0ZDA3ZmU5NmFlZmYyMjA5Mjc2ZTZiYTFmMTMxODY. | 4 | 0 | X-Lite > > release 1011s stamp 41150 | NULL | > > +----------------------+--------------------------+----------------------------------------------------------------------+----------+---------------------+----+----------------------------------------------+------+-------+----------------------------------+----------+ > > 2 rows in set (0.00 sec) > > > > > > Here is what does the internal proxy (192.168.0.165:7160) which is > > registrar and perform location service, > > the destination set contains both contacts and the first contact used > > is the one which is unavailable. > > this proxy sends first invite with this contact to boundary sip proxy > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: xlset_attr(bsp_route, > > <$global_addr_bsp;lr=on>) > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: attr_destination($bsp_route) > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: ($fr_inv_timer) > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: t_on_reply(ONREPLY_ROUTE) > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: t_on_failure(FAILURE_ROUTE) > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: t_on_branch(BRANCH_ROUTE) > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: destination set: > > Contact: sip:touk@192.168.0.164:1338;rinstance=191d670c84591ea3;transport=TCP, > > sip:touk@192.168.0.164:1348;rinstance=e51fd20db73fc732;transpo > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: next route: <null> > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: message's next hop: > > sip:voip.rd.touk.pl:7060;lr=on > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: (!t_relay()) > > Nov 23 11:20:27 sen ser[28434]: branch_route[BRANCH_ROUTE]: <INVITE> > > ruri:<sip:touk@192.168.0.164:1338;rinstance=191d670c84591ea3;transport=TCP> > > t:<sip:touk@voip.rd.touk.pl> f:<sip:hellboy@voip.rd.touk.pl> c > > Nov 23 11:20:27 sen ser[28434]: branch_route[BRANCH_ROUTE]: > > append_hf(P-Warn: forked branch) > > Nov 23 11:20:27 sen ser[28434]: branch_route[BRANCH_ROUTE]: <INVITE> > > ruri:<sip:touk@192.168.0.164:1348;rinstance=e51fd20db73fc732;transport=TCP> > > t:<sip:touk@voip.rd.touk.pl> f:<sip:hellboy@voip.rd.touk.pl> c > > Nov 23 11:20:27 sen ser[28434]: branch_route[BRANCH_ROUTE]: > > append_hf(P-Warn: forked branch) > > Nov 23 11:20:27 sen ser[28434]: ERROR: tcp_blocking_connect: poll > > error: flags 18 > > Nov 23 11:20:27 sen ser[28434]: ERROR: tcp_blocking_connect: SO_ERROR > > (111) Connection refused > > Nov 23 11:20:27 sen ser[28434]: ERROR: tcpconn_connect: > > tcp_blocking_connect failed > > Nov 23 11:20:27 sen ser[28434]: ERROR: tcp_send: connect failed > > Nov 23 11:20:27 sen ser[28434]: msg_send: ERROR: tcp_send failed > > Nov 23 11:20:27 sen ser[28434]: ERROR: t_send_branch: sending request > > on branch 1 failed > > Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: drop > > > > here is what happens in boundary sip proxy: > > is receives the invite tries to do the t_rqlay but there is the tcp error. > > t_relay() fails and it sends the sl_reply_error to internal sip proxy: > > Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: destination set: <null> > > Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: next route: <null> > > Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: message's next hop: > > sip:touk@192.168.0.164:1338;rinstance=191d670c84591ea3;transport=TCP > > Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: (!t_relay()) > > Nov 23 11:31:38 sen ser[31861]: ERROR: tcp_blocking_connect: poll > > error: flags 18 > > Nov 23 11:31:38 sen ser[31861]: ERROR: tcp_blocking_connect: SO_ERROR > > (111) Connection refused > > Nov 23 11:31:38 sen ser[31861]: ERROR: tcpconn_connect: > > tcp_blocking_connect failed > > Nov 23 11:31:38 sen ser[31861]: ERROR: tcp_send: connect failed > > Nov 23 11:31:38 sen ser[31861]: msg_send: ERROR: tcp_send failed > > Nov 23 11:31:38 sen ser[31861]: ERROR: t_send_branch: sending request > > on branch 0 failed > > Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: (!t_relay()) -> TRUE > > Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: sl_reply_error() > > Nov 23 11:31:38 sen ser[31861]: ERROR: sl_reply_error used: I'm > > terribly sorry, server error occurred (1/SL) > > > > in the attachment there are ngrep and wireshark log from the same situation > > > > if you need more info please let me know > > waiting for your feedback > > > > Cheers > > tomasz > > > > > > > > On Nov 22, 2007 8:40 PM, Andrei Pelinescu-Onciul <andrei(a)iptel.org> wrote: > > > On Nov 16, 2007 at 14:43, Tomasz Zieleniewski (JIRA) <tracker(a)iptel.org> wrote: > > > > tcp branching error > > > > ------------------- > > > > > > > > Key: SER-332 > > > > URL: http://tracker.iptel.org/browse/SER-332 > > > > Project: SER > > > > Issue Type: Bug > > > > Components: core > > > > Affects Versions: 2.0 > > > > Environment: Linux sen 2.6.18-5-amd64 #1 SMP Tue Oct 2 20:37:02 UTC 2007 x86_64 GNU/Linux > > > > Reporter: Tomasz Zieleniewski > > > > Priority: Critical > > > > > > > > > > > > Hi, > > > > > > > > I have the following situation. > > > > I have two ser rel_2_0_0 instances one acting as a boundary proxy the > > > > other on as internal proxy (registrar, location). > > > > > > > > I have the following situation I have a user which has registered two > > > > contacs one woth tcp transport the other one with udp. > > > > > > > > All messages coming to and outgoing from my network travels through > > > > boundary sip proxy. > > > > > > > > When internal ser perform lookup_location it get to contacts and the > > > > destination set contains two records: > > > > Nov 15 11:03:13 sen ser[3673]: route[FORWARD]: destination set: > > > > Contact: sip:xlite@192.168.0.164:1221;rinstance=d35f9cda6bd79b0a;transport=TCP, > > > > sip:xlite@192.168.0.164:7060 > > > > > > > > Then internal ser forward message to boundary SIP proxy by changing > > > > the destination of the message and with the usage of t_relay(). > > > > I see from log that there are two branches involved: > > > > Nov 15 11:03:13 sen ser[3673]: branch_route[BRANCH_ROUTE]: <INVITE> > > > > ruri:<sip:xlite@192.168.0.164:1221;rinstance=d35f9cda6bd79b0a;transport=TCP> > > > > t:<sip:00@voip.rd.touk.pl> f:<sip:lkl@voip.rd.touk.pl> > > > > Nov 15 11:03:13 sen ser[3673]: branch_route[BRANCH_ROUTE]: > > > > append_hf(P-Warn: forked branch) > > > > Nov 15 11:03:13 sen ser[3673]: branch_route[BRANCH_ROUTE]: <INVITE> > > > > ruri:<sip:xlite@192.168.0.164:7060;rinstance=cfca8523e3747cb0> > > > > t:<sip:00@voip.rd.touk.pl> f:<sip:lkl@voip.rd.touk.pl> > > > > Nov 15 11:03:13 sen ser[3673]: branch_route[BRANCH_ROUTE]: > > > > append_hf(P-Warn: forked branch) > > > > > > > > both INVITES reaches boudary SIP proxy. > > > > > > > > Because first contact was unreachable there was an tcp error: > > > > ser[3516]: ERROR: tcp_blocking_connect: poll error: flags 18 > > > > Nov 15 11:03:13 sen ser[3516]: ERROR: tcp_blocking_connect: SO_ERROR > > > > (111) Connection refused > > > > Nov 15 11:03:13 sen ser[3516]: ERROR: tcpconn_connect: > > > > tcp_blocking_connect failed > > > > Nov 15 11:03:13 sen ser[3516]: ERROR: tcp_send: connect failed > > > > Nov 15 11:03:13 sen ser[3516]: msg_send: ERROR: tcp_send failed > > > > Nov 15 11:03:13 sen ser[3516]: ERROR: t_send_branch: sending request > > > > on branch 0 failed > > > > > > > > after which ser invokes sl_reply_error() which results in 477 next hop > > > > error reponse message sent to internal ser instance. > > > > The problem arises when boudary sip proxy processes second INVITE > > > > which correspond to second destination. > > > > when boundary SIP proxy receives it doesn't send it to user agent but > > > > instead reponses to internal ser with > > > > 500 I'm terribly sorry, server error occurred (1/SL) > > > > the only thing I see in the boundary SIP proxy log is: > > > > ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (1/SL) > > > > > > > > Did I miss something here or this is an error? > > > > Waiting for Your feedback > > > > > > > > > > Could you make some traffic dump between the 2 proxies and send it to me > > > (andrei(a)iptel.org)? > > > It's sounds quite strange (it should work without any problems) and a > > > look at the packets might help. > > > > > > > > > Thanks, > > > Andrei > > > _______________________________________________ > > > Serdev mailing list > > > Serdev(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serdev > > > > > >

16 years, 5 months

Re: [Serusers] [Serdev] [Tracker] Created: (SER-332) tcp branching error

by Tomasz Zieleniewski

Hi, Some more debug information: User contacts: ser@sen:~/ser/ser-2.0/ssp$ ./serctl/ser_ctl usrloc show touk(a)voip.rd.touk.pl sip:touk@192.168.0.164:1338;rinstance=191d670c84591ea3;transport=TCP 3330 -1.0 sip:touk@192.168.0.164:1348;rinstance=e51fd20db73fc732;transport=TCP 3405 -1.0 Contents of the location table: mysql> select * from location where uid like 'touk@%'; +----------------------+--------------------------+----------------------------------------------------------------------+----------+---------------------+----+----------------------------------------------+------+-------+----------------------------------+----------+ | uid | aor | contact | received | expires | q | callid | cseq | flags | user_agent | instance | +----------------------+--------------------------+----------------------------------------------------------------------+----------+---------------------+----+----------------------------------------------+------+-------+----------------------------------+----------+ | touk(a)voip.rd.touk.pl | sip:touk@voip.rd.touk.pl | sip:touk@192.168.0.164:1338;rinstance=191d670c84591ea3;transport=TCP | NULL | 2007-11-23 11:17:03 | -1 | MTQ1ZWZmZWE2MWIxZjViYmVkNzZlNmU0YTEwNjRmMTA. | 4 | 0 | X-Lite release 1011s stamp 41150 | NULL | | touk(a)voip.rd.touk.pl | sip:touk@voip.rd.touk.pl | sip:touk@192.168.0.164:1348;rinstance=e51fd20db73fc732;transport=TCP | NULL | 2007-11-23 11:18:18 | -1 | NDk0ZDA3ZmU5NmFlZmYyMjA5Mjc2ZTZiYTFmMTMxODY. | 4 | 0 | X-Lite release 1011s stamp 41150 | NULL | +----------------------+--------------------------+----------------------------------------------------------------------+----------+---------------------+----+----------------------------------------------+------+-------+----------------------------------+----------+ 2 rows in set (0.00 sec) Here is what does the internal proxy (192.168.0.165:7160) which is registrar and perform location service, the destination set contains both contacts and the first contact used is the one which is unavailable. this proxy sends first invite with this contact to boundary sip proxy Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: xlset_attr(bsp_route, <$global_addr_bsp;lr=on>) Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: attr_destination($bsp_route) Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: ($fr_inv_timer) Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: t_on_reply(ONREPLY_ROUTE) Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: t_on_failure(FAILURE_ROUTE) Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: t_on_branch(BRANCH_ROUTE) Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: destination set: Contact: sip:touk@192.168.0.164:1338;rinstance=191d670c84591ea3;transport=TCP, sip:touk@192.168.0.164:1348;rinstance=e51fd20db73fc732;transpo Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: next route: <null> Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: message's next hop: sip:voip.rd.touk.pl:7060;lr=on Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: (!t_relay()) Nov 23 11:20:27 sen ser[28434]: branch_route[BRANCH_ROUTE]: <INVITE> ruri:<sip:touk@192.168.0.164:1338;rinstance=191d670c84591ea3;transport=TCP> t:<sip:touk@voip.rd.touk.pl> f:<sip:hellboy@voip.rd.touk.pl> c Nov 23 11:20:27 sen ser[28434]: branch_route[BRANCH_ROUTE]: append_hf(P-Warn: forked branch) Nov 23 11:20:27 sen ser[28434]: branch_route[BRANCH_ROUTE]: <INVITE> ruri:<sip:touk@192.168.0.164:1348;rinstance=e51fd20db73fc732;transport=TCP> t:<sip:touk@voip.rd.touk.pl> f:<sip:hellboy@voip.rd.touk.pl> c Nov 23 11:20:27 sen ser[28434]: branch_route[BRANCH_ROUTE]: append_hf(P-Warn: forked branch) Nov 23 11:20:27 sen ser[28434]: ERROR: tcp_blocking_connect: poll error: flags 18 Nov 23 11:20:27 sen ser[28434]: ERROR: tcp_blocking_connect: SO_ERROR (111) Connection refused Nov 23 11:20:27 sen ser[28434]: ERROR: tcpconn_connect: tcp_blocking_connect failed Nov 23 11:20:27 sen ser[28434]: ERROR: tcp_send: connect failed Nov 23 11:20:27 sen ser[28434]: msg_send: ERROR: tcp_send failed Nov 23 11:20:27 sen ser[28434]: ERROR: t_send_branch: sending request on branch 1 failed Nov 23 11:20:27 sen ser[28434]: route[FORWARD]: drop here is what happens in boundary sip proxy: is receives the invite tries to do the t_rqlay but there is the tcp error. t_relay() fails and it sends the sl_reply_error to internal sip proxy: Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: destination set: <null> Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: next route: <null> Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: message's next hop: sip:touk@192.168.0.164:1338;rinstance=191d670c84591ea3;transport=TCP Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: (!t_relay()) Nov 23 11:31:38 sen ser[31861]: ERROR: tcp_blocking_connect: poll error: flags 18 Nov 23 11:31:38 sen ser[31861]: ERROR: tcp_blocking_connect: SO_ERROR (111) Connection refused Nov 23 11:31:38 sen ser[31861]: ERROR: tcpconn_connect: tcp_blocking_connect failed Nov 23 11:31:38 sen ser[31861]: ERROR: tcp_send: connect failed Nov 23 11:31:38 sen ser[31861]: msg_send: ERROR: tcp_send failed Nov 23 11:31:38 sen ser[31861]: ERROR: t_send_branch: sending request on branch 0 failed Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: (!t_relay()) -> TRUE Nov 23 11:31:38 sen ser[31861]: route[FORWARD]: sl_reply_error() Nov 23 11:31:38 sen ser[31861]: ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (1/SL) in the attachment there are ngrep and wireshark log from the same situation if you need more info please let me know waiting for your feedback Cheers tomasz On Nov 22, 2007 8:40 PM, Andrei Pelinescu-Onciul <andrei(a)iptel.org> wrote: > On Nov 16, 2007 at 14:43, Tomasz Zieleniewski (JIRA) <tracker(a)iptel.org> wrote: > > tcp branching error > > ------------------- > > > > Key: SER-332 > > URL: http://tracker.iptel.org/browse/SER-332 > > Project: SER > > Issue Type: Bug > > Components: core > > Affects Versions: 2.0 > > Environment: Linux sen 2.6.18-5-amd64 #1 SMP Tue Oct 2 20:37:02 UTC 2007 x86_64 GNU/Linux > > Reporter: Tomasz Zieleniewski > > Priority: Critical > > > > > > Hi, > > > > I have the following situation. > > I have two ser rel_2_0_0 instances one acting as a boundary proxy the > > other on as internal proxy (registrar, location). > > > > I have the following situation I have a user which has registered two > > contacs one woth tcp transport the other one with udp. > > > > All messages coming to and outgoing from my network travels through > > boundary sip proxy. > > > > When internal ser perform lookup_location it get to contacts and the > > destination set contains two records: > > Nov 15 11:03:13 sen ser[3673]: route[FORWARD]: destination set: > > Contact: sip:xlite@192.168.0.164:1221;rinstance=d35f9cda6bd79b0a;transport=TCP, > > sip:xlite@192.168.0.164:7060 > > > > Then internal ser forward message to boundary SIP proxy by changing > > the destination of the message and with the usage of t_relay(). > > I see from log that there are two branches involved: > > Nov 15 11:03:13 sen ser[3673]: branch_route[BRANCH_ROUTE]: <INVITE> > > ruri:<sip:xlite@192.168.0.164:1221;rinstance=d35f9cda6bd79b0a;transport=TCP> > > t:<sip:00@voip.rd.touk.pl> f:<sip:lkl@voip.rd.touk.pl> > > Nov 15 11:03:13 sen ser[3673]: branch_route[BRANCH_ROUTE]: > > append_hf(P-Warn: forked branch) > > Nov 15 11:03:13 sen ser[3673]: branch_route[BRANCH_ROUTE]: <INVITE> > > ruri:<sip:xlite@192.168.0.164:7060;rinstance=cfca8523e3747cb0> > > t:<sip:00@voip.rd.touk.pl> f:<sip:lkl@voip.rd.touk.pl> > > Nov 15 11:03:13 sen ser[3673]: branch_route[BRANCH_ROUTE]: > > append_hf(P-Warn: forked branch) > > > > both INVITES reaches boudary SIP proxy. > > > > Because first contact was unreachable there was an tcp error: > > ser[3516]: ERROR: tcp_blocking_connect: poll error: flags 18 > > Nov 15 11:03:13 sen ser[3516]: ERROR: tcp_blocking_connect: SO_ERROR > > (111) Connection refused > > Nov 15 11:03:13 sen ser[3516]: ERROR: tcpconn_connect: > > tcp_blocking_connect failed > > Nov 15 11:03:13 sen ser[3516]: ERROR: tcp_send: connect failed > > Nov 15 11:03:13 sen ser[3516]: msg_send: ERROR: tcp_send failed > > Nov 15 11:03:13 sen ser[3516]: ERROR: t_send_branch: sending request > > on branch 0 failed > > > > after which ser invokes sl_reply_error() which results in 477 next hop > > error reponse message sent to internal ser instance. > > The problem arises when boudary sip proxy processes second INVITE > > which correspond to second destination. > > when boundary SIP proxy receives it doesn't send it to user agent but > > instead reponses to internal ser with > > 500 I'm terribly sorry, server error occurred (1/SL) > > the only thing I see in the boundary SIP proxy log is: > > ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (1/SL) > > > > Did I miss something here or this is an error? > > Waiting for Your feedback > > > > Could you make some traffic dump between the 2 proxies and send it to me > (andrei(a)iptel.org)? > It's sounds quite strange (it should work without any problems) and a > look at the packets might help. > > > Thanks, > Andrei > _______________________________________________ > Serdev mailing list > Serdev(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serdev >

16 years, 5 months

← Newer
1
...
4
5
6
7
8
9
10
...
25
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users November 2007