sr-dev March 2013

sr-dev@lists.kamailio.org

36 participants
428 discussions

git:master: README - last minute small edits
by Olle E. Johansson 11 Mar '13

11 Mar '13

Module: sip-router Branch: master Commit: 0bdc78ffb5e4a2f4d77df39372dad66cdf3c141d URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=0bdc78f… Author: Olle E. Johansson <oej(a)edvina.net> Committer: Olle E. Johansson <oej(a)edvina.net> Date: Mon Mar 11 11:16:09 2013 +0100 README - last minute small edits --- README | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README b/README index e1ee0ba..e0eae66 100644 --- a/README +++ b/README @@ -38,7 +38,7 @@ Kamailio's performance and robustness allows it to serve millions of users and a of very large operators. With a low-cost dual-CPU, the Kamailio server is able to power IP telephony services in an area as large as the Bay Area during peak hours. -The Kamailio is extremely configurable to allow the creation of various routing and +The Kamailio server is extremely configurable to allow the creation of various routing and admission policies as well as setting up new and customized services. Its configurability allows it to serve many roles: network security barrier, presence server, application server, IMS server or PSTN gateway guard (Session Border Controller) for example. @@ -74,8 +74,8 @@ Router, then OpenSER and now Kamailio. A merge project was started during the fa of 2008 by developers from the OpenSER project, recently renamed to Kamailio.org and SIP Express Router (SER) from iptel.org. -Kamailio is the result of a merge of the code base and years -of experience from both developer teams. In release 4.0, during the spring of 2013, the +Kamailio is the result of a merge of the code base and years of experience from +both developer teams. In release 4.0, during the spring of 2013, the merger of the products was completed and a unified product was released. See http://www.sip-router.org/ for the story of SER, OpenSER/Kamailio and kamailio.org. @@ -89,7 +89,7 @@ subject to available manpower. To receive feedback to your inquiries, we recommend you to subscribe to the sr-users mailing list and post your queries there. This mailing -list is set up for mutual help by the community of ser users and developers. +list is set up for mutual help by the community of Kamailio users and developers. To participate in the mailing list, subscribe at the following web address: http://lists.sip-router.org/mailman/listinfo/sr-users

1 0

git:4.0: README - last minute release fixes
by Olle E. Johansson 11 Mar '13

11 Mar '13

Module: sip-router Branch: 4.0 Commit: 4f084e251742f64ac423c5d266f0ea0dc1e33926 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=4f084e2… Author: Olle E. Johansson <oej(a)edvina.net> Committer: Olle E. Johansson <oej(a)edvina.net> Date: Mon Mar 11 11:13:36 2013 +0100 README - last minute release fixes --- README | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README b/README index e1ee0ba..e0eae66 100644 --- a/README +++ b/README @@ -38,7 +38,7 @@ Kamailio's performance and robustness allows it to serve millions of users and a of very large operators. With a low-cost dual-CPU, the Kamailio server is able to power IP telephony services in an area as large as the Bay Area during peak hours. -The Kamailio is extremely configurable to allow the creation of various routing and +The Kamailio server is extremely configurable to allow the creation of various routing and admission policies as well as setting up new and customized services. Its configurability allows it to serve many roles: network security barrier, presence server, application server, IMS server or PSTN gateway guard (Session Border Controller) for example. @@ -74,8 +74,8 @@ Router, then OpenSER and now Kamailio. A merge project was started during the fa of 2008 by developers from the OpenSER project, recently renamed to Kamailio.org and SIP Express Router (SER) from iptel.org. -Kamailio is the result of a merge of the code base and years -of experience from both developer teams. In release 4.0, during the spring of 2013, the +Kamailio is the result of a merge of the code base and years of experience from +both developer teams. In release 4.0, during the spring of 2013, the merger of the products was completed and a unified product was released. See http://www.sip-router.org/ for the story of SER, OpenSER/Kamailio and kamailio.org. @@ -89,7 +89,7 @@ subject to available manpower. To receive feedback to your inquiries, we recommend you to subscribe to the sr-users mailing list and post your queries there. This mailing -list is set up for mutual help by the community of ser users and developers. +list is set up for mutual help by the community of Kamailio users and developers. To participate in the mailing list, subscribe at the following web address: http://lists.sip-router.org/mailman/listinfo/sr-users

1 0

about registrar outbound modes
by Juha Heinanen 11 Mar '13

11 Mar '13

from registrar README: 3.24. outbound_mode (integer) If set to 0 then this module will accept REGISTER requests that do not contain a Supported: header with the outbound options-tag. The 200 OK response to REGISTER requests that this module generates will not contain Require: or Supported: headers with the outbound options tag. If set to 1 then this module will accept REGISTER requests that do not contain a Supported: header with the outbound options-tag. The 200 OK response to REGISTER requests that this module generates will contain a Supported: header with the outbound options tag. If set to 2 then this module will reject REGISTER requests that do not contain a Supported: header with the outbound options-tag. The 200 OK response to REGISTER requests that this module generates will contain Require: and Supported: headers with the outbound options tag. looks likes there is no mode that could be used by registrar that intends to support registrations from both outbound capable and non-outbound capable UAs. i would like to change mode 1 as follows: If set to 1 then this module will accept REGISTER requests that do not contain a Supported: header with the outbound options-tag. The 200 OK response to REGISTER requests that this module generates will contain a Require: or Supported: header with the outbound options tag depending on if REGISTER requests contain or do not contain, respectively, a Supported: header with the outbound options-tag. without this modification UAs that support outbound don't get back a response that tells them that registrar supports outbound: 4.2.1. Initial Registrations ... If outbound registration succeeded, as indicated by the presence of the outbound option-tag in the Require header field of a successful registration response, the UA begins sending keep-alives as described in Section 4.4. i would thus like to consider the current definition of mode 1 as a bug, since it does not achieve anything more than mode 0. comments? -- juha

2 7

presence notify packet garbage with latest 4.0
by Juha Heinanen 11 Mar '13

11 Mar '13

i tested my presence server using the latest 4.0 branch and noticed that some notify requests generated by presence server over tcp cannot be interpreted by my sip proxy. here is working example using version 4.0.0-pre1 when presence server is sending notify request to sip proxy over tcp to port 5070: Mar 11 04:06:15 sip /usr/sbin/pres-serv[6837]: INFO: Routing locally generated NOTIFY <sip:jh_test_fi@192.98.102.10:5074;alias=192.98.102.10~46961~2;transport=tcp> to <sip:jh@test.fi> from <sip:jh@test.fi> Mar 11 04:06:15 sip /usr/sbin/sip-proxy[6473]: INFO: Routing in-dialog NOTIFY <sip:jh_test_fi@192.98.102.10:5074;transport=tcp> from <sip:jh@test.fi> to <sip:192.98.102.10:46961;transport=tcp> No. Time Source Destination Protocol Info 242 04:06:15.847426 127.0.0.1 127.0.0.1 SIP Request: NOTIFY sip:jh_test_fi@192.98.102.10:5074;alias=192.98.102.10~46961~2;transport=tcp Frame 242 (707 bytes on wire, 707 bytes captured) Linux cooked capture Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1) Transmission Control Protocol, Src Port: 40580 (40580), Dst Port: vtsas (5070), Seq: 1, Ack: 1, Len: 639 Session Initiation Protocol Request-Line: NOTIFY sip:jh_test_fi@192.98.102.10:5074;alias=192.98.102.10~46961~2;transport=tcp SIP/2.0 Message Header Via: SIP/2.0/TCP 127.0.0.1:5080;branch=z9hG4bK582b.bbb468a4000000000000000000000000.0 To: sip:jh@test.fi;tag=xohct From: sip:jh@test.fi;tag=2c15998813993a5f2698a8693042e46f-d0d1 CSeq: 2 NOTIFY Call-ID: kblivgathfumnxl(a)sip.test.fi Route: <sip:127.0.0.1:5070;transport=tcp;r2=on;lr>, <sip:192.98.102.10;transport=tcp;r2=on;lr> Content-Length: 0 User-Agent: OpenXg Presence/XCAP Server (4.0.0-pre1 (i386/linux)) Max-Forwards: 70 Event: message-summary Contact: <sip:127.0.0.1:5080;transport=tcp> Subscription-State: active;expires=900 0000 00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00 ................ 0010 45 10 02 b3 e5 4d 40 00 40 06 54 e5 7f 00 00 01 E....M@.@.T..... 0020 7f 00 00 01 9e 84 13 ce 2b 73 81 d2 25 bd 9e 17 ........+s..%... 0030 80 18 02 01 00 a8 00 00 01 01 08 0a 00 3b 64 9e .............;d. 0040 00 3b 64 9d 4e 4f 54 49 46 59 20 73 69 70 3a 6a .;d.NOTIFY sip:j 0050 68 5f 74 65 73 74 5f 66 69 40 31 39 32 2e 39 38 h_test_fi(a)192.98 0060 2e 31 30 32 2e 31 30 3a 35 30 37 34 3b 61 6c 69 .102.10:5074;ali 0070 61 73 3d 31 39 32 2e 39 38 2e 31 30 32 2e 31 30 as=192.98.102.10 0080 7e 34 36 39 36 31 7e 32 3b 74 72 61 6e 73 70 6f ~46961~2;transpo 0090 72 74 3d 74 63 70 20 53 49 50 2f 32 2e 30 0d 0a rt=tcp SIP/2.0.. 00a0 56 69 61 3a 20 53 49 50 2f 32 2e 30 2f 54 43 50 Via: SIP/2.0/TCP 00b0 20 31 32 37 2e 30 2e 30 2e 31 3a 35 30 38 30 3b 127.0.0.1:5080; 00c0 62 72 61 6e 63 68 3d 7a 39 68 47 34 62 4b 35 38 branch=z9hG4bK58 00d0 32 62 2e 62 62 62 34 36 38 61 34 30 30 30 30 30 2b.bbb468a400000 00e0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 0000000000000000 00f0 30 30 30 2e 30 0d 0a 54 6f 3a 20 73 69 70 3a 6a 000.0..To: sip:j 0100 68 40 74 65 73 74 2e 66 69 3b 74 61 67 3d 78 6f h(a)test.fi;tag=xo 0110 68 63 74 0d 0a 46 72 6f 6d 3a 20 73 69 70 3a 6a hct..From: sip:j 0120 68 40 74 65 73 74 2e 66 69 3b 74 61 67 3d 32 63 h(a)test.fi;tag=2c 0130 31 35 39 39 38 38 31 33 39 39 33 61 35 66 32 36 15998813993a5f26 0140 39 38 61 38 36 39 33 30 34 32 65 34 36 66 2d 64 98a8693042e46f-d 0150 30 64 31 0d 0a 43 53 65 71 3a 20 32 20 4e 4f 54 0d1..CSeq: 2 NOT 0160 49 46 59 0d 0a 43 61 6c 6c 2d 49 44 3a 20 6b 62 IFY..Call-ID: kb 0170 6c 69 76 67 61 74 68 66 75 6d 6e 78 6c 40 73 69 livgathfumnxl@si 0180 70 2e 74 65 73 74 2e 66 69 0d 0a 52 6f 75 74 65 p.test.fi..Route 0190 3a 20 3c 73 69 70 3a 31 32 37 2e 30 2e 30 2e 31 : <sip:127.0.0.1 01a0 3a 35 30 37 30 3b 74 72 61 6e 73 70 6f 72 74 3d :5070;transport= 01b0 74 63 70 3b 72 32 3d 6f 6e 3b 6c 72 3e 2c 20 3c tcp;r2=on;lr>, < 01c0 73 69 70 3a 31 39 32 2e 39 38 2e 31 30 32 2e 31 sip:192.98.102.1 01d0 30 3b 74 72 61 6e 73 70 6f 72 74 3d 74 63 70 3b 0;transport=tcp; 01e0 72 32 3d 6f 6e 3b 6c 72 3e 0d 0a 43 6f 6e 74 65 r2=on;lr>..Conte 01f0 6e 74 2d 4c 65 6e 67 74 68 3a 20 30 0d 0a 55 73 nt-Length: 0..Us 0200 65 72 2d 41 67 65 6e 74 3a 20 4f 70 65 6e 58 67 er-Agent: OpenXg 0210 20 50 72 65 73 65 6e 63 65 2f 58 43 41 50 20 53 Presence/XCAP S 0220 65 72 76 65 72 20 20 28 34 2e 30 2e 30 2d 70 72 erver (4.0.0-pr 0230 65 31 20 28 69 33 38 36 2f 6c 69 6e 75 78 29 29 e1 (i386/linux)) 0240 0d 0a 4d 61 78 2d 46 6f 72 77 61 72 64 73 3a 20 ..Max-Forwards: 0250 37 30 0d 0a 45 76 65 6e 74 3a 20 6d 65 73 73 61 70..Event: messa 0260 67 65 2d 73 75 6d 6d 61 72 79 0d 0a 43 6f 6e 74 ge-summary..Cont 0270 61 63 74 3a 20 3c 73 69 70 3a 31 32 37 2e 30 2e act: <sip:127.0. 0280 30 2e 31 3a 35 30 38 30 3b 74 72 61 6e 73 70 6f 0.1:5080;transpo 0290 72 74 3d 74 63 70 3e 0d 0a 53 75 62 73 63 72 69 rt=tcp>..Subscri 02a0 70 74 69 6f 6e 2d 53 74 61 74 65 3a 20 61 63 74 ption-State: act 02b0 69 76 65 3b 65 78 70 69 72 65 73 3d 39 30 30 0d ive;expires=900. 02c0 0a 0d 0a ... and here is failing example using version 4.0.0-rc1: Mar 11 04:02:12 sip /usr/sbin/pres-serv[5879]: INFO: Routing locally generated NOTIFY <sip:jh_test_fi@192.98.102.10:5074;alias=192.98.102.10~46955~2;transport=tcp> to <sip:jh@test.fi> from <sip:jh@test.fi> Mar 11 04:02:12 sip /usr/sbin/sip-proxy[6463]: INFO: Routing in-dialog ##### here is $rm Mar 11 04:02:12 sip /usr/sbin/sip-proxy[6463]: INFO: <core> [parser/parse_fline.c:145]: ERROR:parse_first_line: method not followed by SP Mar 11 04:02:12 sip /usr/sbin/sip-proxy[6463]: INFO: <core> [parser/parse_fline.c:242]: ERROR:parse_first_line: bad message Mar 11 04:02:12 sip /usr/sbin/sip-proxy[6463]: INFO: <core> [parser/parse_fline.c:90]: ERROR: parse_first_line: message too short: 7 Mar 11 04:02:12 sip /usr/sbin/sip-proxy[6463]: INFO: <core> [parser/parse_fline.c:242]: ERROR:parse_first_line: bad message Mar 11 04:02:12 sip /usr/sbin/sip-proxy[6463]: ERROR: <core> [parser/msg_parser.c:705]: ERROR: parse_msg: message=<out#015#012#015#012> Mar 11 04:02:12 sip /usr/sbin/sip-proxy[6463]: ERROR: <core> [receive.c:146]: ERROR: receive_msg: parse_msg failed Frame 31 (724 bytes on wire, 724 bytes captured) Linux cooked capture Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1) Transmission Control Protocol, Src Port: 40567 (40567), Dst Port: vtsas (5070), Seq: 1, Ack: 1, Len: 656 Session Initiation Protocol Request-Line: NOTIFY sip:jh_test_fi@192.98.102.10:5074;alias=192.98.102.10~46955~2;transport=tcp SIP/2.0 Message Header Via: SIP/2.0/TCP 127.0.0.1:5080;branch=z9hG4bK84cf.d6d935d2000000000000000000000000.0 To: sip:jh@test.fi;tag=zrrmw From: sip:jh@test.fi;tag=2c15998813993a5f2698a8693042e46f-d351 CSeq: 2 NOTIFY Call-ID: jcgampqtrnzphwb(a)sip.test.fi Route: <sip:127.0.0.1:5070;transport=tcp;r2=on;lr>, <sip:192.98.102.10;transport=tcp;r2=on;lr> Content-Length: 0 User-Agent: OpenXg Presence/XCAP Server (4.0.0-rc1 (i386/linux)) Max-Forwards: 70 Event: message-summary Contact: <sip:127.0.0.1:5080;transport=tcp> Subscription-State: active;expires=900 Data (656 bytes) Data: 4E4F54494659207369703A6A685F746573745F6669403139... [Length: 656] 0000 00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00 ................ 0010 45 10 02 c4 6f 27 40 00 40 06 ca fa 7f 00 00 01 E...o'@.@....... 0020 7f 00 00 01 9e 77 13 ce 1f 95 60 1b 27 89 f5 cc .....w....`.'... 0030 80 18 02 55 00 b9 00 00 01 01 08 0a 00 3a 76 a3 ...U.........:v. 0040 00 3a 61 7f 4e 4f 54 49 46 59 20 73 69 70 3a 6a .:a.NOTIFY sip:j 0050 68 5f 74 65 73 74 5f 66 69 40 31 39 32 2e 39 38 h_test_fi(a)192.98 0060 2e 31 30 32 2e 31 30 3a 35 30 37 34 3b 61 6c 69 .102.10:5074;ali 0070 61 73 3d 31 39 32 2e 39 38 2e 31 30 32 2e 31 30 as=192.98.102.10 0080 7e 34 36 39 35 35 7e 32 3b 74 72 61 6e 73 70 6f ~46955~2;transpo 0090 72 74 3d 74 63 70 20 53 49 50 2f 32 2e 30 0d 0a rt=tcp SIP/2.0.. 00a0 56 69 61 3a 20 53 49 50 2f 32 2e 30 2f 54 43 50 Via: SIP/2.0/TCP 00b0 20 31 32 37 2e 30 2e 30 2e 31 3a 35 30 38 30 3b 127.0.0.1:5080; 00c0 62 72 61 6e 63 68 3d 7a 39 68 47 34 62 4b 38 34 branch=z9hG4bK84 00d0 63 66 2e 64 36 64 39 33 35 64 32 30 30 30 30 30 cf.d6d935d200000 00e0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 0000000000000000 00f0 30 30 30 2e 30 0d 0a 54 6f 3a 20 73 69 70 3a 6a 000.0..To: sip:j 0100 68 40 74 65 73 74 2e 66 69 3b 74 61 67 3d 7a 72 h(a)test.fi;tag=zr 0110 72 6d 77 0d 0a 46 72 6f 6d 3a 20 73 69 70 3a 6a rmw..From: sip:j 0120 68 40 74 65 73 74 2e 66 69 3b 74 61 67 3d 32 63 h(a)test.fi;tag=2c 0130 31 35 39 39 38 38 31 33 39 39 33 61 35 66 32 36 15998813993a5f26 0140 39 38 61 38 36 39 33 30 34 32 65 34 36 66 2d 64 98a8693042e46f-d 0150 33 35 31 0d 0a 43 53 65 71 3a 20 32 20 4e 4f 54 351..CSeq: 2 NOT 0160 49 46 59 0d 0a 43 61 6c 6c 2d 49 44 3a 20 6a 63 IFY..Call-ID: jc 0170 67 61 6d 70 71 74 72 6e 7a 70 68 77 62 40 73 69 gampqtrnzphwb@si 0180 70 2e 74 65 73 74 2e 66 69 0d 0a 52 6f 75 74 65 p.test.fi..Route 0190 3a 20 3c 73 69 70 3a 31 32 37 2e 30 2e 30 2e 31 : <sip:127.0.0.1 01a0 3a 35 30 37 30 3b 74 72 61 6e 73 70 6f 72 74 3d :5070;transport= 01b0 74 63 70 3b 72 32 3d 6f 6e 3b 6c 72 3e 2c 20 3c tcp;r2=on;lr>, < 01c0 73 69 70 3a 31 39 32 2e 39 38 2e 31 30 32 2e 31 sip:192.98.102.1 01d0 30 3b 74 72 61 6e 73 70 6f 72 74 3d 74 63 70 3b 0;transport=tcp; 01e0 72 32 3d 6f 6e 3b 6c 72 3e 0d 0a 43 6f 6e 74 65 r2=on;lr>..Conte 01f0 6e 74 2d 4c 65 6e 67 74 68 3a 20 30 0d 0a 55 73 nt-Length: 0..Us 0200 65 72 2d 41 67 65 6e 74 3a 20 4f 70 65 6e 58 67 er-Agent: OpenXg 0210 20 50 72 65 73 65 6e 63 65 2f 58 43 41 50 20 53 Presence/XCAP S 0220 65 72 76 65 72 20 20 28 34 2e 30 2e 30 2d 72 63 erver (4.0.0-rc 0230 31 20 28 69 33 38 36 2f 6c 69 6e 75 78 29 29 0d 1 (i386/linux)). 0240 0a 4d 61 78 2d 46 6f 72 77 61 72 64 73 3a 20 37 .Max-Forwards: 7 0250 30 0d 0a 45 76 65 6e 74 3a 20 6d 65 73 73 61 67 0..Event: messag 0260 65 2d 73 75 6d 6d 61 72 79 0d 0a 43 6f 6e 74 61 e-summary..Conta 0270 63 74 3a 20 3c 73 69 70 3a 31 32 37 2e 30 2e 30 ct: <sip:127.0.0 0280 2e 31 3a 35 30 38 30 3b 74 72 61 6e 73 70 6f 72 .1:5080;transpor 0290 74 3d 74 63 70 3e 0d 0a 53 75 62 73 63 72 69 70 t=tcp>..Subscrip 02a0 74 69 6f 6e 2d 53 74 61 74 65 3a 20 61 63 74 69 tion-State: acti 02b0 76 65 3b 65 78 70 69 72 65 73 3d 39 30 30 0d 0a ve;expires=900.. 02c0 0d 0a 6f 75 74 0d 0a 0d 0a 00 00 00 00 00 00 00 ..out........... 02d0 00 00 00 00 .... notice that wireshark in the failing case shows that notify request is followed by data, which it is not doing in the working example. i have tried this on two hosts with equal result. in both cases the config files, amount of memory, etc. are the same. this looks like a show stopper grade problem to me. what has changed between 4.0.0-pre1 and 4.0.0-rc1 that could explain this? -- juha

3 11

git:4.0: INSTALL: updates for v4.0.0
by Daniel-Constantin Mierla 11 Mar '13

11 Mar '13

Module: sip-router Branch: 4.0 Commit: de672e729c52f27252c78759c9b68b5ca09dfbdc URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=de672e7… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Sun Mar 10 22:07:11 2013 +0100 INSTALL: updates for v4.0.0 (cherry picked from commit b4ebc4a8164cfee995fb3ed0570702ae0547c0ce) --- INSTALL | 102 ++++++++++++++++++++++++++++++++++++++------------------------ 1 files changed, 62 insertions(+), 40 deletions(-) diff --git a/INSTALL b/INSTALL index 2cd8015..557601b 100644 --- a/INSTALL +++ b/INSTALL @@ -1,12 +1,9 @@ -$Id$ - ================================================== - Kamailio Installation Notes + Kamailio SIP Server Installation Notes - http://www.kamailio.org - http://sip-router.org + http://www.kamailio.org ================================================== @@ -17,15 +14,11 @@ $Id$ not explicitely mentioned, SIP server refers to any of these two applications. - This memo gives you hints how to set up the SIP server quickly. To - understand how SIP server works and how to configure it properly, - please read the admin's guide available from the http://sip-router.org - website. - - We also urge you to read latest ISSUES (available from website - too) and check for potential problems in this release. - Users of previous releases are encouraged to read NEWS to learn how to move - to this new SIP server version. + This memo gives you hints how to set up the SIP server quickly. + + You can find similar tutorial and many more on project's web site: + - http://www.kamailio.org/w/documentation/ + - http://www.kamailio.org/wiki/ Table of Contents @@ -34,6 +27,10 @@ Table of Contents 1. SIP Server Flavours 2. Supported Architectures and Requirements 3. Howto Build SIP Server From the Source Distribution + 3.1 Kamailio Fast Track Installation + 3.2 Details Installing from Source Code + A) Set SIP Server Flavour + B) Build Commands 4. Quick-Start Installation Guide A) Getting Help B) Disclaimers @@ -51,7 +48,7 @@ The two major SIP server flavours are: - Kamailio (former OpenSER) Starting with version 3.0.0, the two SIP server flavours are built from -same source code tree. In version 4.0.0 the two source code trees was +same source code tree. In version 4.0.0 the two source code trees were merged even more, so a combined module directory is now used. Kamailio flavor is the one built by default. SER is, historically speaking, the @@ -64,10 +61,10 @@ very few, Kamailio enabling next compile time flags: - application server extensions in tm module In version 4.0.0 the modules were merged into one set and the merger -between the two products was completed. Kamailio is now the main -flavour. +between the two products was completed. -Switching between flavours is a matter of 'make' command parameters. +Kamailio is now the default flavour. Switching between flavours is a matter +of 'make' command parameters. Several installation tutorials for Kamailio are available on the web wiki: - http://www.kamailio.org/wiki/ @@ -135,6 +132,7 @@ Requirements: - libpcre libs and devel headers - if you want to compile the lcr and dialplan modules - libsctp devel headers - if you want to compile the SCTP transport in the core +- libssl devel headers (openssl project) - if you want to compule the TLS module - linunistring - for the Websockets module @@ -208,7 +206,6 @@ OS Notes: see README of the module you want to use Both SER and Kamailio flavours have APT deb repositories that allow you to install the binaries easily - see the web sites for more details: - - http://iptel.org/ser - http://kamailio.org Cygwin (alpha state, partial support) @@ -230,22 +227,47 @@ OS Notes: 3. Howto Build SIP Server From Source Distribution -------------------------------------------- +-------------------------------------------------- + +(NOTE: if make doesn't work try gmake instead) + +3.1 Kamailio Fast Track Installation +.................................... + + +If you are familiar with Unix/Linux build tools aready and you installed +required dependency, then you can just follow this section, otherwise +skip over it. + +To get the SIP server installed, in the folder with source code run: + + make cfg + make all + make install + +If you want to install with additional modules, for example with mysql and +tls, run: + + make include_modules="db_mysql tls" cfg + make all + make install + +3.2 Details Installing from Source Code +....................................... -(NOTE: if make doesn't work try gmake instead) A) Set SIP Server Flavour If you don't have a clean source tree, first do: make proper -To build SER flavour, you don't need to do anything special, continue to +To build Kamailio flavour, you don't need to do anything special, continue to read the section 3.B). -To build Kamailio flavour, you have to run first: - make FLAVOUR=kamailio cfg +To build SER flavour, you have to run first: + make FLAVOUR=ser cfg -The parameter 'FLAVOUR=kamailio' must be given all the time when make target +The parameter 'FLAVOUR=ser' must be given all the time when make target is 'cfg'. B) Build Commands @@ -520,15 +542,15 @@ Install: "modules" or "excluded_modules"). -3. Quick-Start Installation Guide ----------------------------------------------- +4. Quick-Start Installation Guide +--------------------------------- A) Getting Help This guide gives you instructions on how to set up the SIP server (SER or Kamailio) on your box quickly. In case the default configuration does not fly, please check the documentation at the SIP server web site - http://sip-router.org to learn how to configure SIP server for your site. + http://www.kamailio.org to learn how to configure SIP server for your site. If the documentation does not resolve your problem you may try contacting our user forum by E-mail at sr-users(a)lists.sip-router.org -- that is the @@ -564,7 +586,7 @@ C) Quick Start If you use Solaris 8 you can try our solaris package. If you use Gentoo Linux you do not have to download a package. -2) Install the package + 2) Install the package RPM: rpm -i <package_name> debian: @@ -584,7 +606,7 @@ C) Quick Start *BSD: pkg_add package_name -3) Start the server + 3) Start the server RPM + gentoo: /etc/init.d/ser start @@ -603,7 +625,7 @@ C) Quick Start You can start SIP server directly with /usr/local/sbin/ser or /usr/local/sbin/kamailio. -4) optionally, watch server's health using the + 4) optionally, watch server's health using the serctl or kamctl utility - to do so, first set the environment variable SIP_DOMAIN to your domain @@ -623,7 +645,7 @@ C) Quick Start /usr/local/sbin/kamctl moni (if you installed Kamailio flavour from a tar.gz or solaris package) -5) Connect SIP phones + 5) Connect SIP phones Register with the server using your favorite SIP User Agent. You may want to look at configuration hints for use of various clients on iptel.org site at @@ -651,7 +673,7 @@ D) SIP Server with Persistent Data Storage set-variable = max_connections=500 -1) Download the package containing mysql support for SIP server from: + 1) Download the package containing mysql support for SIP server from: **** site not available yet @@ -661,7 +683,7 @@ D) SIP Server with Persistent Data Storage For gentoo please include 'mysql' to your USE variable in /etc/make.conf or give it as variable to the emerge command. -2) install the package + 2) install the package rpm -i <package_name> or dpkg -i <package_name> @@ -672,7 +694,7 @@ D) SIP Server with Persistent Data Storage (if do not want to put 'mysql' into your USE variable you can type: USE="mysql" emerge ser) -3.1) create MySQL tables for SER flavour + 3.1) create MySQL tables for SER flavour - if you have a previously installed SER on your system, use /usr/sbin/ser_mysql.sh reinstall to convert your SER database into new structures @@ -681,7 +703,7 @@ D) SIP Server with Persistent Data Storage to create SER database structures (you will be prompted for password of MySql "root" user) -3.2) create MySQL tables for Kamailio flavour + 3.2) create MySQL tables for Kamailio flavour - if you have a previously installed Kamailio on your system, use /usr/local/sbin/kamdbctl reinstall to convert your Kamailio database into new structures @@ -690,7 +712,7 @@ D) SIP Server with Persistent Data Storage to create Kamailio database structures (you will be prompted for password of MySql "root" user) -4) configure SIP server to use SQL + 4) configure SIP server to use SQL uncomment all lines in configuration file ser.cfg or kamilio.cfg which are related to authentication: - loadmodule "db_mysql.so" @@ -704,7 +726,7 @@ D) SIP Server with Persistent Data Storage break; } -5) be sure to replace realm, the first parameter in www_* actions, + 5) be sure to replace realm, the first parameter in www_* actions, with name of your server; some broken UAC implementations don't authenticate otherwise; the authentication command in your configuration script should look then like this: @@ -713,12 +735,12 @@ D) SIP Server with Persistent Data Storage break; } -6) restart the server + 6) restart the server /etc/init.d/ser restart or /etc/init.d/kamailio restart -7) you can now start managing the server using the serctl or kamctl utility; + 7) you can now start managing the server using the serctl or kamctl utility; you need to first set the environment variable SIP_DOMAIN to your local SIP realm, e.g., export SIP_DOMAIN="myserver.foobar.com"

2 3

git:4.0: tm: set proper buffer len when Max-Forward header is not added
by Daniel-Constantin Mierla 11 Mar '13

11 Mar '13

Module: sip-router Branch: 4.0 Commit: b6040e7c14a9562d58649859a407f9f1f5b3a8cc URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b6040e7… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Mon Mar 11 09:38:37 2013 +0100 tm: set proper buffer len when Max-Forward header is not added - reported by Juha Heinanen (cherry picked from commit 2d38b046b6202a35c0adf4c8b61f0d665432dd4f) --- modules/tm/t_msgbuilder.c | 14 +++++++++++--- 1 files changed, 11 insertions(+), 3 deletions(-) diff --git a/modules/tm/t_msgbuilder.c b/modules/tm/t_msgbuilder.c index 60328b3..aa0144c 100644 --- a/modules/tm/t_msgbuilder.c +++ b/modules/tm/t_msgbuilder.c @@ -1512,6 +1512,7 @@ char* build_uac_req(str* method, str* headers, str* body, dlg_t* dialog, int bra { char* buf, *w; str content_length, cseq, via; + unsigned int maxfwd_len; if (!method || !dialog) { LOG(L_ERR, "build_uac_req(): Invalid parameter value\n"); @@ -1525,6 +1526,14 @@ char* build_uac_req(str* method, str* headers, str* body, dlg_t* dialog, int bra LOG(L_ERR, "build_uac_req(): Error while printing CSeq number\n"); return 0; } + + if(headers==NULL || headers->len<15 + || _strnstr(headers->s, "Max-Forwards:", headers->len)==NULL) { + maxfwd_len = MAXFWD_HEADER_LEN; + } else { + maxfwd_len = 0; + } + *len = method->len + 1 + dialog->hooks.request_uri->len + 1 + SIP_VERSION_LEN + CRLF_LEN; if (assemble_via(&via, t, dst, branch) < 0) { @@ -1540,7 +1549,7 @@ char* build_uac_req(str* method, str* headers, str* body, dlg_t* dialog, int bra *len += CALLID_LEN + dialog->id.call_id.len + CRLF_LEN; /* Call-ID */ *len += CSEQ_LEN + cseq.len + 1 + method->len + CRLF_LEN; /* CSeq */ *len += calculate_routeset_length(dialog); /* Route set */ - *len += MAXFWD_HEADER_LEN; /* Max-forwards */ + *len += maxfwd_len; /* Max-forwards */ *len += CONTENT_LENGTH_LEN + content_length.len + CRLF_LEN; /* Content- Length */ *len += (server_signature ? (user_agent_hdr.len + CRLF_LEN) : 0); /* Signature */ @@ -1564,8 +1573,7 @@ char* build_uac_req(str* method, str* headers, str* body, dlg_t* dialog, int bra w = print_callid(w, dialog, t); /* Call-ID */ w = print_routeset(w, dialog); /* Route set */ - if(headers==NULL || headers->len<15 - || _strnstr(headers->s, "Max-Forwards:", headers->len)==NULL) + if(maxfwd_len>0) memapp(w, MAXFWD_HEADER, MAXFWD_HEADER_LEN); /* Max-forwards */ /* Content-Length */

1 0

git:4.0: pkg: deb specs updated for v4.0.0
by Daniel-Constantin Mierla 11 Mar '13

11 Mar '13

Module: sip-router Branch: 4.0 Commit: 5111813177bce534bbfbc158e3c90cfd381c0b63 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=5111813… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Sun Mar 10 22:46:50 2013 +0100 pkg: deb specs updated for v4.0.0 (cherry picked from commit a349d9aab2d95b9b1cbc58870ead9a7294bcdcaa) --- pkg/kamailio/deb/debian/changelog | 6 ++++++ pkg/kamailio/deb/debian/control | 21 +++++++++++++++++++++ pkg/kamailio/deb/debian/rules | 6 +++--- pkg/kamailio/deb/lenny/changelog | 6 ++++++ pkg/kamailio/deb/lenny/rules | 2 +- pkg/kamailio/deb/precise/changelog | 6 ++++++ pkg/kamailio/deb/precise/control | 21 +++++++++++++++++++++ pkg/kamailio/deb/precise/rules | 6 +++--- pkg/kamailio/deb/squeeze/changelog | 6 ++++++ pkg/kamailio/deb/squeeze/control | 21 +++++++++++++++++++++ pkg/kamailio/deb/squeeze/rules | 4 ++-- pkg/kamailio/deb/wheezy/changelog | 6 ++++++ pkg/kamailio/deb/wheezy/control | 21 +++++++++++++++++++++ pkg/kamailio/deb/wheezy/rules | 6 +++--- 14 files changed, 126 insertions(+), 12 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=511…

1 0

git:master: tm: set proper buffer len when Max-Forward header is not added
by Daniel-Constantin Mierla 11 Mar '13

11 Mar '13

Module: sip-router Branch: master Commit: 2d38b046b6202a35c0adf4c8b61f0d665432dd4f URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2d38b04… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Mon Mar 11 09:38:37 2013 +0100 tm: set proper buffer len when Max-Forward header is not added - reported by Juha Heinanen --- modules/tm/t_msgbuilder.c | 14 +++++++++++--- 1 files changed, 11 insertions(+), 3 deletions(-) diff --git a/modules/tm/t_msgbuilder.c b/modules/tm/t_msgbuilder.c index 60328b3..aa0144c 100644 --- a/modules/tm/t_msgbuilder.c +++ b/modules/tm/t_msgbuilder.c @@ -1512,6 +1512,7 @@ char* build_uac_req(str* method, str* headers, str* body, dlg_t* dialog, int bra { char* buf, *w; str content_length, cseq, via; + unsigned int maxfwd_len; if (!method || !dialog) { LOG(L_ERR, "build_uac_req(): Invalid parameter value\n"); @@ -1525,6 +1526,14 @@ char* build_uac_req(str* method, str* headers, str* body, dlg_t* dialog, int bra LOG(L_ERR, "build_uac_req(): Error while printing CSeq number\n"); return 0; } + + if(headers==NULL || headers->len<15 + || _strnstr(headers->s, "Max-Forwards:", headers->len)==NULL) { + maxfwd_len = MAXFWD_HEADER_LEN; + } else { + maxfwd_len = 0; + } + *len = method->len + 1 + dialog->hooks.request_uri->len + 1 + SIP_VERSION_LEN + CRLF_LEN; if (assemble_via(&via, t, dst, branch) < 0) { @@ -1540,7 +1549,7 @@ char* build_uac_req(str* method, str* headers, str* body, dlg_t* dialog, int bra *len += CALLID_LEN + dialog->id.call_id.len + CRLF_LEN; /* Call-ID */ *len += CSEQ_LEN + cseq.len + 1 + method->len + CRLF_LEN; /* CSeq */ *len += calculate_routeset_length(dialog); /* Route set */ - *len += MAXFWD_HEADER_LEN; /* Max-forwards */ + *len += maxfwd_len; /* Max-forwards */ *len += CONTENT_LENGTH_LEN + content_length.len + CRLF_LEN; /* Content- Length */ *len += (server_signature ? (user_agent_hdr.len + CRLF_LEN) : 0); /* Signature */ @@ -1564,8 +1573,7 @@ char* build_uac_req(str* method, str* headers, str* body, dlg_t* dialog, int bra w = print_callid(w, dialog, t); /* Call-ID */ w = print_routeset(w, dialog); /* Route set */ - if(headers==NULL || headers->len<15 - || _strnstr(headers->s, "Max-Forwards:", headers->len)==NULL) + if(maxfwd_len>0) memapp(w, MAXFWD_HEADER, MAXFWD_HEADER_LEN); /* Max-forwards */ /* Content-Length */

1 0

git:jason.penton/ims_ro_interface: nathelper: add new option sipping_disable_bflag
by Juha Heinanen 11 Mar '13

11 Mar '13

nathelper readme on this flag tells: What branch flag should be used by the module to disable NAT pings on a per-registration basis. If the given flag is set for a particular registration, then no NAT pings will be sent at all, regardless of any other conditions. however, the name of the flag is sipping_disable_bflag, which indicates that it would apply to nat ping via sip requests only. which way it is? please either fix the name of the flag or readme text. -- juha

3 6

git:4.0: core: try to detect ipv6 addresses only when USE_IPV6 is used
by Juha Heinanen 11 Mar '13

11 Mar '13

Module: sip-router Branch: 4.0 Commit: 080db7fd62fcf3c941fce2e1e0552a6584572c3e URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=080db7f… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Juha Heinanen <jh(a)tutpro.com> Date: Sun Mar 10 23:53:26 2013 +0100 core: try to detect ipv6 addresses only when USE_IPV6 is used - reported by Juha Heinanen (cherry picked from commit b035aa9f2cc19d387b1b8f33a7888ffee27a4138) --- dns_cache.c | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/dns_cache.c b/dns_cache.c index b56e94d..b351490 100644 --- a/dns_cache.c +++ b/dns_cache.c @@ -1891,8 +1891,10 @@ inline static struct dns_hash_entry* dns_cache_do_request(str* name, int type) #endif /* USE_DNS_CACHE_STATS */ if (type==T_A){ +#ifdef USE_IPV6 if (str2ip6(name)!=0) goto end; +#endif /* USE_IPV6 */ if ((ip=str2ip(name))!=0){ e=dns_cache_mk_ip_entry(name, ip); if (likely(e)) @@ -2469,8 +2471,10 @@ inline static struct hostent* dns_a_get_he(str* name) struct hostent* he; e=0; +#ifdef USE_IPV6 if (str2ip6(name)!=0) return 0; +#endif if ((ip=str2ip(name))!=0){ return ip_addr2he(name, ip); } @@ -2971,8 +2975,10 @@ inline static int dns_a_resolve( struct dns_hash_entry** e, ret=-E_DNS_NO_IP; if (*e==0){ /* do lookup */ /* if ip don't set *e */ +#ifdef USE_IPV6 if (str2ip6(name)!=0) goto error; +#endif if ((tmp=str2ip(name))!=0){ *ip=*tmp; *rr_no=0;

1 0

← Newer
1
...
30
31
32
33
34
35
36
...
43
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev March 2013