Re: [SR-Users] dispatcher didnt use the gateway
Hi Reda,
i fix it. forward() is stateless and so one then i breaks many things
in my multihomed setup.
I use transaction for it and then it works.
To prevent internal Invites to get dispatched, i used the dst_ip.
I just want external incoming calls to be dispatched.
route[INVITE] {
# -
# INVITE Message Handler
# -
setflag(6);
lookup("aliases");
if (uri!=myself) {
route(NAT);
route(RELAY);
return;
};
#!ifdef WITH_DISPATCHER
if (lookup("location") && (dst_ip==222.222.222.222)) {
if(ds_select_domain("1", "4")) {
xlog("DISPATCHER ds_select_domain\n");
route(NAT);
xlog("DISPATCHER was in route-NAT now route-RELAY\n");
route(RELAY);
xlog("DISPATCHER was in route-RELAY\n");
return;
}
}
#!endif
if (!lookup("location")) {
xlog("404 User not found\n");
sl_send_reply("404", "User Not Found");
return;
};
route(NAT);
route(RELAY);
}
route[RELAY] {
# -
# Default Message Handler
# -
t_on_reply("1");
if (!t_relay()) {
if (method=="INVITE" && isflagset(6)) {
unforce_rtp_proxy();
};
sl_reply_error();
};
}
--
Mit freundlichen Grüßen
*Karsten Horsmann*
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] uac module incoming INVITE become wrong dst_ip address
Hello List,
i am nearly finishing my multihomed config (public ip/internal ip)
with kamailio.
For incoming calls i want to use the uac module too.
Then i want to locate an permanet entry and dispatch it to ivr system
behind kamailio.
i tried something like this:
if (lookup("location") && (dst_ip==222.222.222.222)) {
if(ds_select_domain("1", "4")) {
Okay for registerd UAC this works perfect - but if made an call to the
uac registerd
number i got as $Ri the 172.20.100.74 - and thats is the private ip address.
Why that???
Any hints to check "if its internal or external" call???
--
Mit freundlichen Grüßen
*Karsten Horsmann*
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] registrar/usrloc updates - gruu support (rfc 5627)
Hello, one new updates was done to usrloc/registrar, to take in consideration reg-id Contact parameter specified by RFC 5626. This parameter is used to match usrloc records along with +sip.instance parameter (when present). You will need to update/re-create location and aliases tables -- note that I haven't increased the version value for these tables this times, since it is not a change within or in between stable releases. Cheers, Daniel On 4/13/12 3:15 PM, Daniel-Constantin Mierla wrote: Hello, I just pushed GRUU support in git master branch. That implied adding two new columns to location table, therefore if you use devel version, **you have to update your db schema**. Perhaps a bit of tuning will follow in the next days, but GRUU support should be fully functional in terms of routing. Testing and feedback will be very appreciated as well as hints on what SIP hard/phones support GRUU properly. Be also aware that now you may have to do lookup location even for within dialog requests, if the r-uri is a local GRUU. Cheers, Daniel -- Daniel-Constantin Mierla Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany http://www.asipto.com/index.php/kamailio-advanced-training/ ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] SIP Attack
Hello. I was wondering if someone could help me here. From time to time I stat to receive from the internet this SIP message : U 190.22.140.170:51316 -> 64.76.154.110:5060 SIP/2.0 400 BadRequest. Via: . From: . To: . Call-ID: . CSeq: . User-Agent: AddPac SIP Gateway. Content-Length: 0. . At burst rate of 124 pps (packets per second), this meesage is entering to Kamailio routine and generating a lot of ERROR logs lie these : Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: [parser/msg_parser.c:353]: ERROR: bad header field [To: 5] Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: [parser/msg_parser.c:353]: ERROR: bad header field [To: 5] Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: [parser/msg_parser.c:353]: ERROR: bad header field [To: 5] Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al as, parse_headers failed Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: WARNING: sanity [sanity.c:254]: sanity_check(): check_required_headers(): fa iled to send 400 via sl reply Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: [parser/msg_parser.c:353]: ERROR: bad header field [To: 5] Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: [parser/msg_parser.c:353]: ERROR: bad header field [To: 5] Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: [parser/msg_parser.c:353]: ERROR: bad header field [To: 5] Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al as, parse_headers failed Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: WARNING: sanity [sanity.c:254]: sanity_check(): check_required_headers(): fa iled to send 400 via sl reply Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: [parser/msg_parser.c:353]: ERROR: bad header field [To: 5] Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: [parser/msg_parser.c:353]: ERROR: bad header field [To: 5] Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: [parser/msg_parser.c:353]: ERROR: bad header field [To: 5] Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al as, parse_headers failed Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: WARNING: sanity [sanity.c:254]: sanity_check(): check_required_headers(): fa iled to send 400 via sl reply The only way that I have now for blocking this packet to hit the Kamailio server is via iptables : iptables -A INPUT -s 190.22.140.170 -p udp --dport 5060 --jump REJECT Is there a better way to do this?! Thanks in advance, * * *Ricardo Martinez.-* ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP Attack
IMHO preventing the packet to reach kamailio is better (via iptables) than doing something in kamailio itself Regards, Vineet Menon On 17 April 2012 20:32, Ricardo Martinez wrote: > Hello. > > I was wondering if someone could help me here. From time to time I stat > to receive from the internet this SIP message : > > > > U 190.22.140.170:51316 -> 64.76.154.110:5060 > > SIP/2.0 400 BadRequest. > > Via: . > > From: . > > To: . > > Call-ID: . > > CSeq: . > > User-Agent: AddPac SIP Gateway. > > Content-Length: 0. > > . > > > > At burst rate of 124 pps (packets per second), this meesage is entering to > Kamailio routine and generating a lot of ERROR logs lie these : > > Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: > [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header > > Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: > [parser/msg_parser.c:353]: ERROR: bad header field [To: > gister=>5] > > Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: > [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header > > Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: > [parser/msg_parser.c:353]: ERROR: bad header field [To: > gister=>5] > > Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: > [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header > > Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: > [parser/msg_parser.c:353]: ERROR: bad header field [To: > gister=>5] > > Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: > [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al > > as, parse_headers failed > > Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: WARNING: sanity > [sanity.c:254]: sanity_check(): check_required_headers(): fa > > iled to send 400 via sl reply > > Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: > [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header > > Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: > [parser/msg_parser.c:353]: ERROR: bad header field [To: > gister=>5] > > Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: > [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header > > Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: > [parser/msg_parser.c:353]: ERROR: bad header field [To: > gister=>5] > > Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: > [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header > > Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: > [parser/msg_parser.c:353]: ERROR: bad header field [To: > gister=>5] > > Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: > [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al > > as, parse_headers failed > > Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: WARNING: sanity > [sanity.c:254]: sanity_check(): check_required_headers(): fa > > iled to send 400 via sl reply > > Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: > [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header > > Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: > [parser/msg_parser.c:353]: ERROR: bad header field [To: > gister=>5] > > Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: > [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header > > Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: > [parser/msg_parser.c:353]: ERROR: bad header field [To: > gister=>5] > > Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: > [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header > > Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: > [parser/msg_parser.c:353]: ERROR: bad header field [To: > gister=>5] > > Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: > [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al > > as, parse_headers failed > > Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: WARNING: sanity > [sanity.c:254]: sanity_check(): check_required_headers(): fa > > iled to send 400 via sl reply > > > > > > The only way that I have now for blocking this packet to hit the Kamailio > server is via iptables : > > iptables -A INPUT -s 190.22.140.170 -p udp --dport 5060 --jump REJECT > > > > Is there a better way to do this?! > > Thanks in advance, > > * * > > *Ricardo Martinez.-* > > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP Attack
Hi, Do you have any client that is sending a corrupt request to the "AddPac SIP Gateway" at 190.22.140.170, so that this gateway is replying "400 bad request" ? Maybe you could resolve this problem at the source.. If it's not the case, you can send an email to the owner of the IP address. A quick lookup on the IP address on www.network-tools.com gives you a hint on the owner. Reda On Tue, Apr 17, 2012 at 17:19, Vineet Menon wrote: > IMHO preventing the packet to reach kamailio is better (via iptables) than > doing something in kamailio itself > > Regards, > > Vineet Menon > > > > > On 17 April 2012 20:32, Ricardo Martinez wrote: > >> Hello. >> >> I was wondering if someone could help me here. From time to time I stat >> to receive from the internet this SIP message : >> >> >> >> U 190.22.140.170:51316 -> 64.76.154.110:5060 >> >> SIP/2.0 400 BadRequest. >> >> Via: . >> >> From: . >> >> To: . >> >> Call-ID: . >> >> CSeq: . >> >> User-Agent: AddPac SIP Gateway. >> >> Content-Length: 0. >> >> . >> >> >> >> At burst rate of 124 pps (packets per second), this meesage is entering >> to Kamailio routine and generating a lot of ERROR logs lie these : >> >> Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: >> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header >> >> Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: >> [parser/msg_parser.c:353]: ERROR: bad header field [To: > >> gister=>5] >> >> Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: >> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header >> >> Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: >> [parser/msg_parser.c:353]: ERROR: bad header field [To: > >> gister=>5] >> >> Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: >> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header >> >> Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: >> [parser/msg_parser.c:353]: ERROR: bad header field [To: > >> gister=>5] >> >> Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: >> [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al >> >> as, parse_headers failed >> >> Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: WARNING: sanity >> [sanity.c:254]: sanity_check(): check_required_headers(): fa >> >> iled to send 400 via sl reply >> >> Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: >> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header >> >> Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: >> [parser/msg_parser.c:353]: ERROR: bad header field [To: > >> gister=>5] >> >> Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: >> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header >> >> Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: >> [parser/msg_parser.c:353]: ERROR: bad header field [To: > >> gister=>5] >> >> Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: >> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header >> >> Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: >> [parser/msg_parser.c:353]: ERROR: bad header field [To: > >> gister=>5] >> >> Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: >> [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al >> >> as, parse_headers failed >> >> Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: WARNING: sanity >> [sanity.c:254]: sanity_check(): check_required_headers(): fa >> >> iled to send 400 via sl reply >> >> Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: >> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header >> >> Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: >> [parser/msg_parser.c:353]: ERROR: bad header field [To: > >> gister=>5] >> >> Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: >> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header >> >> Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: >> [parser/msg_parser.c:353]: ERROR: bad header field [To: > >> gister=>5] >> >> Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: >> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header >> >> Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: >> [parser/msg_parser.c:353]: ERROR: bad header field [To: > >> gister=>5] >> >> Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: >> [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al >> >> as, parse_headers failed >> >> Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: WARNING: sanity >> [sanity.c:254]: sanity_check(): check_required_headers(): fa >> >> iled to send 400 via sl reply >> >> >> >> >> >> The only way that I have now for blocking this packet to hit the Kamailio >> server is via iptables : >> >> iptables -A INPUT -s 190.22.140.170 -p udp --dport 5060 --jump REJECT >> >> >> >> Is there a better way to do this?! >> >> Thanks in advance, >>
[SR-Users] SIP Status: 401 Unauthorized (0 bindings)
Hello List, I have a fresh install kamailio 3.2.0 running on ubuntu. Everything seems to work fine according to the logs, I have enabled support for the following: - enabled support to connect to MySQL server - enabled user authentication - enabled persistent user location service - enabled NAT traversal and updated RTPProxy control socket parameter I added a few users with kamctl add user pass but when I try to register with my client I get the following: 8.257745 x.x.x.x -> 10.62.99.103 SIP Request: REGISTER sip:x.x.x.x 8.258462 10.62.99.103 -> x.x.x.x SIP Status: 401 Unauthorized(0 bindings) Here are some detailed logs for the reg process: T x.x.x.x:63171 -> 10.62.99.103:5060 [AP] REGISTER sip:x.x.x.x SIP/2.0. Via: SIP/2.0/TCP 192.168.126.19:4369;rport;branch=z9hG4bK239028812. From: ;tag=303867081. To: . Call-ID: 1300614569. CSeq: 7 REGISTER. Contact: . Max-Forwards: 70. User-Agent: Linphone/3.5.0 (eXosip2/3.6.0). Expires: 600. Content-Length: 0. . T 10.62.99.103:5060 -> x.x.x.x:63171 [AP] SIP/2.0 401 Unauthorized. Via: SIP/2.0/TCP 192.168.126.19:4369 ;rport=63171;branch=z9hG4bK239028812;received=x.x.x.x. From: ;tag=303867081. To: ;tag=b27e1a1d33761e85846fc98f5f3a7e58.b260. Call-ID: 1300614569. CSeq: 7 REGISTER. WWW-Authenticate: Digest realm="x.x.x.x", nonce="T42z9U+NssnZP82+sdkwPgl1nRk61QDm". Server: kamailio (3.2.0 (i386/linux)). Content-Length: 0. Any help is greatly appreciated. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP Status: 401 Unauthorized (0 bindings)
You have to check username, password, realm. Also - whether password is plaintext or not. If this do not work, you can put debug=4 or even more. Then you will receive plenty of messages, but may be you will see what is wrong. On Tue, Apr 17, 2012 at 9:16 PM, Saul Waizer wrote: > Hello List, > > I have a fresh install kamailio 3.2.0 running on ubuntu. Everything seems > to work fine according to the logs, I have enabled support for the > following: > > >- enabled support to connect to MySQL server >- enabled user authentication >- enabled persistent user location service >- enabled NAT traversal and updated RTPProxy control socket parameter > >I added a few users with kamctl add user pass but when I try to >register with my client I get the following: > > > 8.257745 x.x.x.x -> 10.62.99.103 SIP Request: REGISTER sip:x.x.x.x > 8.258462 10.62.99.103 -> x.x.x.x SIP Status: 401 Unauthorized(0 > bindings) > > Here are some detailed logs for the reg process: > > T x.x.x.x:63171 -> 10.62.99.103:5060 [AP] > > REGISTER sip:x.x.x.x SIP/2.0. > > Via: SIP/2.0/TCP 192.168.126.19:4369;rport;branch=z9hG4bK239028812. > > From: ;tag=303867081. > > To: . > > Call-ID: 1300614569. > > CSeq: 7 REGISTER. > > Contact: . > > Max-Forwards: 70. > > User-Agent: Linphone/3.5.0 (eXosip2/3.6.0). > > Expires: 600. > > Content-Length: 0. > > . > > > > T 10.62.99.103:5060 -> x.x.x.x:63171 [AP] > > SIP/2.0 401 Unauthorized. > > Via: SIP/2.0/TCP 192.168.126.19:4369 > ;rport=63171;branch=z9hG4bK239028812;received=x.x.x.x. > > From: ;tag=303867081. > > To: ;tag=b27e1a1d33761e85846fc98f5f3a7e58.b260. > > Call-ID: 1300614569. > > CSeq: 7 REGISTER. > > WWW-Authenticate: Digest realm="x.x.x.x", > nonce="T42z9U+NssnZP82+sdkwPgl1nRk61QDm". > > Server: kamailio (3.2.0 (i386/linux)). > > Content-Length: 0. > > > Any help is greatly appreciated. > > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP Status: 401 Unauthorized (0 bindings)
Thank you, I enabled higher verbosity and got the following: 7(29749) DEBUG: tm [t_lookup.c:1148]: DEBUG: t_check_msg: msg id=2 global id=2 T end=(nil) 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=470 a=6 n=route 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=763 a=17 n=if 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=698 a=26 n=is_method 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=707 a=17 n=if 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=701 a=27 n=www_authorize 7(29749) DEBUG: auth_db [authorize.c:303]: realm value [1.1.1.1] 7(29749) DEBUG: auth [api.c:95]: auth: digest-algo: MD5 parsed value: 1 7(29749) DEBUG: [db_res.c:118]: allocate 28 bytes for result set at 0xb7209040 7(29749) DEBUG: db_mysql [km_res.c:68]: 1 columns returned from the query 7(29749) DEBUG: [db_res.c:155]: allocate 4 bytes for result names at 0xb7209118 7(29749) DEBUG: [db_res.c:165]: allocate 4 bytes for result types at 0xb720908c 7(29749) DEBUG: db_mysql [km_res.c:85]: allocate 8 bytes for RES_NAMES[0] at 0xb7209ce4 7(29749) DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0xb7209ce4)[0]=[password] 7(29749) DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type 7(29749) DEBUG: [db_res.c:184]: allocate 8 bytes for rows at 0xb7209d1c 7(29749) DEBUG: [db_row.c:119]: allocate 20 bytes for row values at 0xb7209d54 7(29749) DEBUG: [db_val.c:117]: converting STRING [abc123] 7(29749) DEBUG: auth [api.c:210]: check_response: Our result = '8077c41df1fac7cf3bdc69f13268d82b' 7(29749) DEBUG: auth [api.c:220]: check_response: Authorization failed 7(29749) DEBUG: [db_res.c:81]: freeing 1 columns 7(29749) DEBUG: [db_res.c:85]: freeing RES_NAMES[0] at 0xb7209ce4 7(29749) DEBUG: [db_res.c:94]: freeing result names at 0xb7209118 7(29749) DEBUG: [db_res.c:99]: freeing result types at 0xb720908c 7(29749) DEBUG: [db_res.c:54]: freeing 1 rows 7(29749) DEBUG: [db_row.c:97]: freeing row values at 0xb7209d54 7(29749) DEBUG: [db_res.c:62]: freeing rows at 0xb7209d1c 7(29749) DEBUG: [db_res.c:136]: freeing result set at 0xb7209040 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=703 a=27 n=www_challenge 7(29749) DEBUG: auth [challenge.c:102]: build_challenge_hf: realm='1.1.1.1' 7(29749) DEBUG: auth [challenge.c:244]: auth: 'WWW-Authenticate: Digest realm="1.1.1.1", nonce="T42590+NuMv/Z+tJt2jKl5A1XJ49feO7" I know the user/pass is correct as i set it to something very simple, I still dont understand what is wrong... On Tue, Apr 17, 2012 at 2:29 PM, Stoyan Mihaylov < stoyan.v.mihay...@gmail.com> wrote: > You have to check username, password, realm. Also - whether password is > plaintext or not. > If this do not work, you can put debug=4 or even more. Then you will > receive plenty of messages, but may be you will see what is wrong. > > On Tue, Apr 17, 2012 at 9:16 PM, Saul Waizer wrote: > >> Hello List, >> >> I have a fresh install kamailio 3.2.0 running on ubuntu. Everything seems >> to work fine according to the logs, I have enabled support for the >> following: >> >> >>- enabled support to connect to MySQL server >>- enabled user authentication >>- enabled persistent user location service >>- enabled NAT traversal and updated RTPProxy control socket parameter >> >>I added a few users with kamctl add user pass but when I try to >>register with my client I get the following: >> >> >> 8.257745 x.x.x.x -> 10.62.99.103 SIP Request: REGISTER sip:x.x.x.x >> 8.258462 10.62.99.103 -> x.x.x.x SIP Status: 401 Unauthorized(0 >> bindings) >> >> Here are some detailed logs for the reg process: >> >> T x.x.x.x:63171 -> 10.62.99.103:5060 [AP] >> >> REGISTER sip:x.x.x.x SIP/2.0. >> >> Via: SIP/2.0/TCP 192.168.126.19:4369;rport;branch=z9hG4bK239028812. >> >> From: ;tag=303867081. >> >> To: . >> >> Call-ID: 1300614569. >> >> CSeq: 7 REGISTER. >> >> Contact: . >> >> Max-Forwards: 70. >> >> User-Agent: Linphone/3.5.0 (eXosip2/3.6.0). >> >> Expires: 600. >> >> Content-Length: 0. >> >> . >> >> >> >> T 10.62.99.103:5060 -> x.x.x.x:63171 [AP] >> >> SIP/2.0 401 Unauthorized. >> >> Via: SIP/2.0/TCP 192.168.126.19:4369 >> ;rport=63171;branch=z9hG4bK239028812;received=x.x.x.x. >> >> From: ;tag=303867081. >> >> To: ;tag=b27e1a1d33761e85846fc98f5f3a7e58.b260. >> >> Call-ID: 1300614569. >> >> CSeq: 7 REGISTER. >> >> WWW-Authenticate: Digest realm="x.x.x.x", >> nonce="T42z9U+NssnZP82+sdkwPgl1nRk61QDm". >> >> Server: kamailio (3.2.0 (i386/linux)). >> >> Content-Length: 0. >> >> >> Any help is greatly appreciated. >> >> >> >> ___ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >> sr-users@lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> >> > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@li
Re: [SR-Users] dropped calls after 38 seconds openSER
Daniel, i got a fresh install kamailio 3.2.0 running on ubuntu per your
suggestion. rtpproxy is running as well. My nathelper looks like this:
# - nathelper params -
modparam("nathelper", "natping_interval", 3)
modparam("nathelper", "ping_nated_only", 0)
modparam("nathelper", "sipping_bflag", FLB_NATSIPPING)
modparam("nathelper", "sipping_from", "sip:pin...@kamailio.org")
# SW changes
modparam("nathelper", "natping_processes", 3)
modparam("nathelper", "sipping_bflag", 7)
modparam("nathelper", "sipping_method", "INFO")
I also ran "kamctl fifo nh_enable_ping 1" on the console.
Calls drop at *exactly 30* seconds, I dont see anything obvious in the
logs. Any suggestions? Anyone?
On Mon, Apr 16, 2012 at 2:51 PM, Saul Waizer wrote:
> Daniel,
>
> thank you for the suggestion, I followed the tutorial and got it up and
> running, however I am still experiencing the same issue, dropped calls
> after 30 seconds. Furthermore the output of tshark -i eth0 -R sip does not
> show any errors such as too many hops, everything looks very clean but I
> still cant get more than 30 seconds out.
>
> I have a default config with mysql enabled and nat. rtproxy is running as
> well.
>
> Any help is greatly appreciated.
>
>
> On Mon, Apr 16, 2012 at 1:31 PM, Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>> Hello,
>>
>> ngrep trace (I haven't seen any yet in the thread) of such call can help
>> seeing if Record-/Route and Contact headers are properly set and maintained
>> during the call. It might be a broken RR handling in a device or a wrong
>> update of contact address.
>>
>> On the other hand, in the config, I saw presence being loaded -- if you
>> need that, then start with kamailio 3.2.x, here is a tutorial:
>>
>> http://www.kamailio.org/wiki/install/3.2.x/git
>>
>> It comes with a default config file where is very easy to enable nat
>> traversal as well as presence handling -- just read the top of config file
>> and add the appropriate #!define directives.
>>
>> 1.3.x is anyhow way too old...
>>
>> Cheers,
>> Daniel
>>
>>
>>
>> On 4/16/12 7:16 PM, Stoyan Mihaylov wrote:
>>
>> I am using nathelper and rtpproxy.
>> We had no serious problems with those modules.
>> My idea was to overwrite wrong addresses in ACK and BYE packages, because
>> they kept reentering kamailo, instead of being forwarded where they have to
>> go.
>>
>> By the way - you can add:
>> modparam("htable", "htable", "forw=>size=8;autoexpire=7200;")
>> modparam("htable", "htable", "mustforw=>size=8;autoexpire=7200;")
>>
>> On Mon, Apr 16, 2012 at 8:03 PM, Saul Waizer wrote:
>>
>>> Thank you Stoyan
>>> *
>>> *
>>> I added the routing config as you suggested but it still drops the call
>>> after 30 seconds.
>>>
>>> Any other suggestions?
>>>
>>> Note: my nathelper module is commented out because I can't get it to
>>> work, here is my mod list:
>>>
>>> ## Modules Section
>>>
>>> #set module path
>>> mpath="/usr/lib/openser/modules/"
>>>
>>> /* uncomment next line for MySQL DB support */
>>> loadmodule "mysql.so"
>>> loadmodule "sl.so"
>>> loadmodule "tm.so"
>>> loadmodule "rr.so"
>>> loadmodule "maxfwd.so"
>>> loadmodule "usrloc.so"
>>> loadmodule "registrar.so"
>>> loadmodule "textops.so"
>>> loadmodule "mi_fifo.so"
>>> loadmodule "uri_db.so"
>>> loadmodule "uri.so"
>>> loadmodule "xlog.so"
>>> loadmodule "acc.so"
>>>
>>> loadmodule "auth.so"
>>> loadmodule "auth_db.so"
>>>
>>> #loadmodule "domain.so"
>>> loadmodule "presence.so"
>>> #loadmodule "presence_xml.so"
>>>
>>> # !! Nathelper
>>> #loadmodule "nathelper.so"
>>> #loadmodule "nat_traversal.so"
>>> #loadmodule "rtpproxy.so"
>>> #loadmodule "dialog.so"
>>>
>>> Thank You
>>>
>>>
>>> On Mon, Apr 16, 2012 at 12:03 PM, Stoyan Mihaylov <
>>> stoyan.v.mihay...@gmail.com> wrote:
>>>
Some time ago, I had similar problem.
This was my solution:
if(is_method("INVITE")){
ds_select_dst("1","4");
$sht(forw=>$ft)=$du;
sl_send_reply("100","Trying");
route(RELAY);
exit();
}
if ( is_method("ACK|BYE") ) {
if ( t_check_trans() ) {
t_relay();
exit;
} else {
if(($sht(forw=>$ft))=~$td){
$du=$sht(forw=>$ft);
}else if((($td=="sip.mydomain.com
")||($td=="ip.of.my.domain"))&&($si=="ip.of.my.domain")){
$du=$sht(forw=>$ft);
}
t_relay();
exit;
>
> I am new to opensips so I am not too familiar with the routing
> logics, a google search on that error suggests that there is a problem
> with
> the route config where its creating a loop exhausting the Max Hops. The
> way
> I configured my clients uses my server as a proxy.
>
> Any help is greatly appreciated!
>
> On Mon, Apr 16, 2012 at 1:59 AM, davy van de moere <
> davy.van.de.mo...@gmail.com> wrote:
>
>> 38 seconds sounds pretty close to 30 seconds. Could those 38 seconds
>> be a 30 seconds after the actual answer packet?
>>
>> If so,
Re: [SR-Users] SIP Status: 401 Unauthorized (0 bindings)
7(29749) DEBUG: auth [api.c:95]: auth: digest-algo: MD5 parsed value: 1
I think you have to check authorization - this is part of my config:
#!define DBURL "mysql://user:p...@ip.of.mysl.db/openser"
modparam("auth_db", "db_url", DBURL)
modparam("auth_db", "calculate_ha1", yes)
modparam("auth_db", "password_column", "password")
modparam("auth_db", "load_credentials", "")
In subscribtion table, I am using now only plaintext passwords, which is
weakness, but I will solve it later.
On Tue, Apr 17, 2012 at 9:44 PM, Saul Waizer wrote:
> Thank you, I enabled higher verbosity and got the following:
>
> 7(29749) DEBUG: tm [t_lookup.c:1148]: DEBUG: t_check_msg: msg id=2 global
> id=2 T end=(nil)
>
> 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=470 a=6
> n=route
>
> 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=763 a=17
> n=if
>
> 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=698 a=26
> n=is_method
>
> 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=707 a=17
> n=if
>
> 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=701 a=27
> n=www_authorize
>
> 7(29749) DEBUG: auth_db [authorize.c:303]: realm value [1.1.1.1]
>
> 7(29749) DEBUG: auth [api.c:95]: auth: digest-algo: MD5 parsed value: 1
>
> 7(29749) DEBUG: [db_res.c:118]: allocate 28 bytes for result set
> at 0xb7209040
>
> 7(29749) DEBUG: db_mysql [km_res.c:68]: 1 columns returned from the query
>
> 7(29749) DEBUG: [db_res.c:155]: allocate 4 bytes for result names
> at 0xb7209118
>
> 7(29749) DEBUG: [db_res.c:165]: allocate 4 bytes for result types
> at 0xb720908c
>
> 7(29749) DEBUG: db_mysql [km_res.c:85]: allocate 8 bytes for RES_NAMES[0]
> at 0xb7209ce4
>
> 7(29749) DEBUG: db_mysql [km_res.c:92]:
> RES_NAMES(0xb7209ce4)[0]=[password]
>
> 7(29749) DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type
>
> 7(29749) DEBUG: [db_res.c:184]: allocate 8 bytes for rows at
> 0xb7209d1c
>
> 7(29749) DEBUG: [db_row.c:119]: allocate 20 bytes for row values
> at 0xb7209d54
>
> 7(29749) DEBUG: [db_val.c:117]: converting STRING [abc123]
>
> 7(29749) DEBUG: auth [api.c:210]: check_response: Our result =
> '8077c41df1fac7cf3bdc69f13268d82b'
>
> 7(29749) DEBUG: auth [api.c:220]: check_response: Authorization failed
>
> 7(29749) DEBUG: [db_res.c:81]: freeing 1 columns
>
> 7(29749) DEBUG: [db_res.c:85]: freeing RES_NAMES[0] at 0xb7209ce4
>
> 7(29749) DEBUG: [db_res.c:94]: freeing result names at 0xb7209118
>
> 7(29749) DEBUG: [db_res.c:99]: freeing result types at 0xb720908c
>
> 7(29749) DEBUG: [db_res.c:54]: freeing 1 rows
>
> 7(29749) DEBUG: [db_row.c:97]: freeing row values at 0xb7209d54
>
> 7(29749) DEBUG: [db_res.c:62]: freeing rows at 0xb7209d1c
>
> 7(29749) DEBUG: [db_res.c:136]: freeing result set at 0xb7209040
>
> 7(29749) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio.cfg] l=703 a=27
> n=www_challenge
>
> 7(29749) DEBUG: auth [challenge.c:102]: build_challenge_hf:
> realm='1.1.1.1'
>
> 7(29749) DEBUG: auth [challenge.c:244]: auth: 'WWW-Authenticate: Digest
> realm="1.1.1.1", nonce="T42590+NuMv/Z+tJt2jKl5A1XJ49feO7"
>
>
> I know the user/pass is correct as i set it to something very simple, I
> still dont understand what is wrong...
>
> On Tue, Apr 17, 2012 at 2:29 PM, Stoyan Mihaylov <
> stoyan.v.mihay...@gmail.com> wrote:
>
>> You have to check username, password, realm. Also - whether password is
>> plaintext or not.
>> If this do not work, you can put debug=4 or even more. Then you will
>> receive plenty of messages, but may be you will see what is wrong.
>>
>> On Tue, Apr 17, 2012 at 9:16 PM, Saul Waizer wrote:
>>
>>> Hello List,
>>>
>>> I have a fresh install kamailio 3.2.0 running on ubuntu. Everything
>>> seems to work fine according to the logs, I have enabled support for the
>>> following:
>>>
>>>
>>>- enabled support to connect to MySQL server
>>>- enabled user authentication
>>>- enabled persistent user location service
>>>- enabled NAT traversal and updated RTPProxy control socket parameter
>>>
>>>I added a few users with kamctl add user pass but when I try to
>>>register with my client I get the following:
>>>
>>>
>>> 8.257745 x.x.x.x -> 10.62.99.103 SIP Request: REGISTER sip:x.x.x.x
>>> 8.258462 10.62.99.103 -> x.x.x.x SIP Status: 401 Unauthorized(0
>>> bindings)
>>>
>>> Here are some detailed logs for the reg process:
>>>
>>> T x.x.x.x:63171 -> 10.62.99.103:5060 [AP]
>>>
>>> REGISTER sip:x.x.x.x SIP/2.0.
>>>
>>> Via: SIP/2.0/TCP 192.168.126.19:4369;rport;branch=z9hG4bK239028812.
>>>
>>> From: ;tag=303867081.
>>>
>>> To: .
>>>
>>> Call-ID: 1300614569.
>>>
>>> CSeq: 7 REGISTER.
>>>
>>> Contact: .
>>>
>>> Max-Forwards: 70.
>>>
>>> User-Agent: Linphone/3.5.0 (eXosip2/3.6.0).
>>>
>>> Expires: 600.
>>>
>>> Content-Length: 0.
>>>
>>> .
>>>
>>>
>>>
>>> T 10.62.99.103:5060 -> x.x.x.x:63171 [AP]
>>>
>>> SIP/2.0 401 Unauthorized.
>>>
>>> Via: SIP/2.0/TCP 192.168.126.19:4369
>>> ;rport=63171;branch=z9hG4bK2
Re: [SR-Users] dropped calls after 38 seconds openSER
I used wireshark on all interfaces and there I saw reentrance of ACK and
BYE.
Then I spent lot of time to find how to go around.
On Tue, Apr 17, 2012 at 10:41 PM, Saul Waizer wrote:
> Daniel, i got a fresh install kamailio 3.2.0 running on ubuntu per your
> suggestion. rtpproxy is running as well. My nathelper looks like this:
>
> # - nathelper params -
> modparam("nathelper", "natping_interval", 3)
> modparam("nathelper", "ping_nated_only", 0)
> modparam("nathelper", "sipping_bflag", FLB_NATSIPPING)
> modparam("nathelper", "sipping_from", "sip:pin...@kamailio.org")
> # SW changes
> modparam("nathelper", "natping_processes", 3)
> modparam("nathelper", "sipping_bflag", 7)
> modparam("nathelper", "sipping_method", "INFO")
>
> I also ran "kamctl fifo nh_enable_ping 1" on the console.
>
> Calls drop at *exactly 30* seconds, I dont see anything obvious in the
> logs. Any suggestions? Anyone?
>
> On Mon, Apr 16, 2012 at 2:51 PM, Saul Waizer wrote:
>
>> Daniel,
>>
>> thank you for the suggestion, I followed the tutorial and got it up and
>> running, however I am still experiencing the same issue, dropped calls
>> after 30 seconds. Furthermore the output of tshark -i eth0 -R sip does not
>> show any errors such as too many hops, everything looks very clean but I
>> still cant get more than 30 seconds out.
>>
>> I have a default config with mysql enabled and nat. rtproxy is running as
>> well.
>>
>> Any help is greatly appreciated.
>>
>>
>> On Mon, Apr 16, 2012 at 1:31 PM, Daniel-Constantin Mierla <
>> mico...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> ngrep trace (I haven't seen any yet in the thread) of such call can help
>>> seeing if Record-/Route and Contact headers are properly set and maintained
>>> during the call. It might be a broken RR handling in a device or a wrong
>>> update of contact address.
>>>
>>> On the other hand, in the config, I saw presence being loaded -- if you
>>> need that, then start with kamailio 3.2.x, here is a tutorial:
>>>
>>> http://www.kamailio.org/wiki/install/3.2.x/git
>>>
>>> It comes with a default config file where is very easy to enable nat
>>> traversal as well as presence handling -- just read the top of config file
>>> and add the appropriate #!define directives.
>>>
>>> 1.3.x is anyhow way too old...
>>>
>>> Cheers,
>>> Daniel
>>>
>>>
>>>
>>> On 4/16/12 7:16 PM, Stoyan Mihaylov wrote:
>>>
>>> I am using nathelper and rtpproxy.
>>> We had no serious problems with those modules.
>>> My idea was to overwrite wrong addresses in ACK and BYE packages,
>>> because they kept reentering kamailo, instead of being forwarded where they
>>> have to go.
>>>
>>> By the way - you can add:
>>> modparam("htable", "htable", "forw=>size=8;autoexpire=7200;")
>>> modparam("htable", "htable", "mustforw=>size=8;autoexpire=7200;")
>>>
>>> On Mon, Apr 16, 2012 at 8:03 PM, Saul Waizer wrote:
>>>
Thank you Stoyan
*
*
I added the routing config as you suggested but it still drops the call
after 30 seconds.
Any other suggestions?
Note: my nathelper module is commented out because I can't get it to
work, here is my mod list:
## Modules Section
#set module path
mpath="/usr/lib/openser/modules/"
/* uncomment next line for MySQL DB support */
loadmodule "mysql.so"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "mi_fifo.so"
loadmodule "uri_db.so"
loadmodule "uri.so"
loadmodule "xlog.so"
loadmodule "acc.so"
loadmodule "auth.so"
loadmodule "auth_db.so"
#loadmodule "domain.so"
loadmodule "presence.so"
#loadmodule "presence_xml.so"
# !! Nathelper
#loadmodule "nathelper.so"
#loadmodule "nat_traversal.so"
#loadmodule "rtpproxy.so"
#loadmodule "dialog.so"
Thank You
On Mon, Apr 16, 2012 at 12:03 PM, Stoyan Mihaylov <
stoyan.v.mihay...@gmail.com> wrote:
> Some time ago, I had similar problem.
> This was my solution:
> if(is_method("INVITE")){
> ds_select_dst("1","4");
> $sht(forw=>$ft)=$du;
> sl_send_reply("100","Trying");
> route(RELAY);
> exit();
> }
>
> if ( is_method("ACK|BYE") ) {
> if ( t_check_trans() ) {
> t_relay();
> exit;
> } else {
> if(($sht(forw=>$ft))=~$td){
> $du=$sht(forw=>$ft);
> }else if((($td=="sip.mydomain.com
> ")||($td=="ip.of.my.domain"))&&($si=="ip.of.my.domain")){
> $du=$sht(forw=>$ft);
> }
> t_relay();
> exit;
>
>>
>> I am new to opensips so I am not too familiar with the routing
>> logics, a google search on that error suggests that there is a problem
>> with
>> the route config where its creating a loop exhausting the Max Hops. The
>> way
>> I confi
[SR-Users] How to configure Kamailio routing logic based on mobile phone numbers
Hi there, Now I could configure Kamailio routing logic based on service's short code (i.e route calls to 200, 300 to separated service's appliction (so call, app serv 1 and app serv 2). My problem is how can i configure Kamailio so that it can route the call from mobile numbers, such as calls from mobile number starting with 0988 x, 0978 x will be routed to app serv1 and the calls of 0976 x to app serv 2. So do you guys have an answer for me ? I would really appreciate your help!!! ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] htable feature request
Hi, I'd like to ask for a feature request for htable. Would it be possible to add an MI function to delete specific entries from an htable, e.g. with "sercmd htable.remove " before freezing 3.3? That'd be handy for example if you hold blocked IPs in htable, but want to unblock some of them manually. At the moment, I only see the method of restarting kamailio to whipe the whole table (and it'd only work if dbmode=0). Thanks in advance, Andreas signature.asc Description: OpenPGP digital signature ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
