- sr-users - kamailio.org

Calling number Routing possibility in 1.5rel.
by Maciej Bylica 13 Apr '10

13 Apr '10

Dear ALL, I am playing around with kamailio 1.5. Could somebody explain me what module best fit to route the call on the basis of number A (calling number). What is more all rules should be able to be modified directly from mysql db. I've run through 3.0 modules and figured out that there is drouting module which is really great, but is it present in 1.5 rel? If negative, what other modules can be used. Thx in advance, Maciej.

2 7

[Serusers] Problems Using iptel accounts
by Nahum Nir 12 Apr '10

12 Apr '10

Hi all, I have made two accounts at iptel: nahum1 and nahum2. I have two computers running X-Lite, both of them registered succesfully. But when I try to invite I get 404 Not Found. I'm dialing nahum2(a)iptel.org. What an I doing worng? Thanks, Nahum

2 1

My wish
by Alex Balashov 12 Apr '10

12 Apr '10

Allow cfg_get parameters to be used as modparams, too, so I can define one set of global database properties and pass them as db_urls to every module that uses one and also to 'sqlops' as an 'sqlcon', and similar things. -- Alex Balashov - Principal Evariste Systems LLC 1170 Peachtree Street 12th Floor, Suite 1200 Atlanta, GA 30309 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/

3 16

Close TLS connection and Registrar Server (Kamailio V1.4.x)
by edson.gomes.leme 11 Apr '10

11 Apr '10

Hello, We are using Kamailio V1.4 with TCP/TLS. The Kamailio is configured the TCP lifetime to the expire value of the REGISTER by using the tcp_persistent_flag parameter of Kamailio's registrar module. Note: The SIP proxy should not close the TCP connection as it is not capable of opening a new one. Kamailio tries to open a TLS connection to the client. The Kamailio should use the existing TLS/TCP connection that was established by the client during registration. We are applying NAT traversal techniques to instruct Kamailio to reuse the established TCP/TLS connection. Example: for each register call fix_nated_register(). For every other request and response call fix_nated_contact(). I have got one SIP phone registered via TLS to kamailio-1.4.X version with Expires = 3600. phone1: connected via ip1:port1 and Expires = 3600. Example: After 15 minutes TLS connection is closed. The SIP Phone opens a new TLS connection and registers via TLS to Kamailio. Thus, we have the following records on the Registrar Server (Kamailio): phone1: connected via ip1:port1 and Expires = 2700 [3600 – (15 min * 60 s) = 2700]. phone1: connected via ip1:port2 and Expires = 3600. Is this the desirable behavior? Shouldn’t the Kamailio (Registrar Server) delete the below registry? phone1: connected via ip1:port1 and Expires = 2700 [3600 – (15 min * 60 s) = 2700]. Best regards! Edson G. Leme

2 1

Close TLS connection and Registrar Server (Kamailio V1.4.x)
by edson.gomes.leme 11 Apr '10

11 Apr '10

1 0

users@kamailio and sr-users@sip-router merged
by Daniel-Constantin Mierla 10 Apr '10

10 Apr '10

Hello, the process of merging users(a)list.kamailio.org and sr-users(a)lists.sip-router.org is completed, offering a single place for community discussions via email related to stable versions and generic topics, also removing confusion for new comers which to use for best feedback. Because sr-users was a rather new mailing list, I imported the archive from users. It will help to continue the topics and have the entire knowledge base built over years in the same place, for web searches. The old Users mailing list archive still exists separately, link at: http://lists.kamailio.org/pipermail/users/ No new posts will get there, subscription is disabled, messages to users list are directed to sr-users (therefore replying to existing threads on either of the mailing lists work just fine). No matter you were a Users or SR-Users subscriber, updates to your profile can be done at: http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users I case your password is no longer valid, you can retrieve it via password reminder at: http://lists.sip-router.org/cgi-bin/mailman/options/sr-users Thanks, Daniel PS. Some of you may have received an unintentional "unsubscribed from sr-users-new mailing list" message, just ignore it - happened when I simulated synchronization of members on temporary name sr-users-new, no unsubscribe action was actually done -- sorry for inconvenience. -- Daniel-Constantin Mierla

1 0

[Kamailio-Users] merging users mailing list
by Daniel-Constantin Mierla 10 Apr '10

10 Apr '10

Hello, I am starting the merging process of users mailing list. Please ignore any notifications you get, if you get them is by mistake in my config -- none of subscribed users will be affected, the work is done for testing on a temporary new list, therefore everyone is safe. Sorry for any inconvenience! I will announce when it is finished. Daniel

1 0

[Kamailio-Users] dispatcher has problems
by Vic Jolin 09 Apr '10

09 Apr '10

I just noticed that if I have 4 servers set like this # group sip addresses of your * units 1 sip:XXX.XXX.XXX.XXX:5060 1 sip:XXX.XXX.XXX.XXX:5060 1 sip:XXX.XXX.XXX.XXX:5060 1 sip:XXX.XXX.XXX.XXX:5060 the registration does not work and I get 401 unauthorized. My setup is like this Openser as proxy sends all SIP messages to load balanced asterisk servers So sip phones should be able to register to the asterisk server The routing part in kamailio.cfg looks like this if ( method=="REGISTER" || method=="NOTIFY" || method=="OPTIONS" || method=="ACK" || method=="MESSAGE") { fix_nated_contact(); fix_nated_register(); ds_select_dst("1","4"); forward();#uri:host, uri:port); exit(); } if (method=="BYE" || method=="CANCEL") { unforce_rtp_proxy(); } else if (method=="INVITE"){ log("VCTOR: Got an invite\n"); fix_nated_contact(); force_rtp_proxy(); ds_select_dst("1","4"); forward();#uri:host, uri:port); t_on_failure("1"); }; search_append('Contact:.*sip:[^>[:cntrl:]]*', ';nat=yes'); t_on_reply("1"); if (!is_method("INVITE|REGISTER|MESSAGE|BYE|NOTIFY|ACK|CANCEL|REFER|SUBSCRIBE|OPTIONS|INFO")) { xlog("L_INFO", "=== [$rm] Method Not Implement ===========\n"); sl_send_reply("501", "Not implemented here"); return; }; any thoughts?

2 2

[Kamailio-Users] lcr module creating extra branch
by Jon Bonilla 09 Apr '10

09 Apr '10

Hi I am using Kamailio 3.0.1 and experiencing a strange behaviour of the lcr module. In short: Using next_gw() function makes my server to send two INVITEs to different destinations! The INVITE Kamailio receives is like: R=sip:4644235465675757@77.77.77.77 F=sip:manwe2@77.77.77.77 T=sip:4644235465675757@77.77.77.77 To try this I have set this in my gw table: sercmd lcr.dump_gws { lcr_id: 1 grp_id: 17 ip_addr: 91.121.117.27 hostname: sindominio.net port: 5080 scheme: sip transport: UDP strip: 0 tag: weight: 1 flags: 37 defunct_until: 268313248 } sercmd lcr.dump_lcrs { lcr_id: 1 prefix: from_uri: grp_id: 17 priority: 1 } Hostname and ip_addr don't match (sindominio.net points to 82.144.4.26). What I capture leaving Kamailio is: U 2010/04/08 17:51:09.614055 77.77.77.77:5060 -> 91.121.117.27:5080 INVITE sip:+4644235465675757@77.77.77.77 SIP/2.0' Record-Route: <sip:77.77.77.77;lr=on;ftag=hgtcn;nat=yes;vsf=czFwOgs5JCAEJEYoJGk3ajxNYmBrPBYC>' Via: SIP/2.0/UDP 77.77.77.77;branch=z9hG4bK90e8.cd3135e1.0' Via: SIP/2.0/UDP 10.0.0.92;received=91.115.172.34;rport=53658;branch=z9hG4bKiwibmejv' Max-Forwards: 69' To: <sip:4644235465675757@77.77.77.77>' From: "1102" <sip:1102@77.77.77.77>;tag=hgtcn' Call-ID: qxvyddwlnmurqvi@multivac' CSeq: 571 INVITE' Contact: <sip:manwe2@91.115.172.34:53658>' Content-Type: application/sdp' Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE' Supported: replaces,norefersub,100rel' User-Agent: Twinkle/1.4.2' Content-Length: 226' ' v=0' o=twinkle 1296734594 70729915 IN IP4 77.77.77.77' s=-' c=IN IP4 77.77.77.77' t=0 0' m=audio 38232 RTP/AVP 8 101' a=rtpmap:8 PCMA/8000' a=rtpmap:101 telephone-event/8000' a=fmtp:101 0-15' a=ptime:20' a=nortpproxy:yes' # U 2010/04/08 17:51:09.614074 77.77.77.77:5060 -> 82.144.4.26:5060 INVITE sip:+4644235465675757@sindominio.net SIP/2.0' Record-Route: <sip:77.77.77.77;lr=on;ftag=hgtcn;nat=yes;vsf=czFwOgs5JCAEJEYoJGk3ajxNYmBrPBYC>' Via: SIP/2.0/UDP 77.77.77.77;branch=z9hG4bK90e8.cd3135e1.1' Via: SIP/2.0/UDP 10.0.0.92;received=91.115.172.34;rport=53658;branch=z9hG4bKiwibmejv' Max-Forwards: 69' To: <sip:4644235465675757@77.77.77.77>' From: "1102" <sip:1102@77.77.77.77>;tag=hgtcn' Call-ID: qxvyddwlnmurqvi@multivac' CSeq: 571 INVITE' Contact: <sip:manwe2@91.115.172.34:53658>' Content-Type: application/sdp' Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE' Supported: replaces,norefersub,100rel' User-Agent: Twinkle/1.4.2' Content-Length: 226' ' v=0' o=twinkle 1296734594 70729915 IN IP4 77.77.77.77' s=-' c=IN IP4 77.77.77.77' t=0 0' m=audio 38232 RTP/AVP 8 101' a=rtpmap:8 PCMA/8000' a=rtpmap:101 telephone-event/8000' a=fmtp:101 0-15' a=ptime:20' a=nortpproxy:yes' My kamailio.cfg script does something like this: if(!load_gws("1", "$ru")) ... if(!next_gw()) ... t_on_branch("BRANCH_ROUTE_CLI_RTP"); if(!t_relay_to("0x01")) ... Branch route_cli_rtp: do rtpproxy stuff No append_branch is executed at all. I have two INVITES IMHO because next_gw() function does create the second one. Any idea about this behaviour?

3 10

[Kamailio-Users] sr-docs mailing list
by Daniel-Constantin Mierla 09 Apr '10

09 Apr '10

Hello, I renamed kamailio-docs(a)lists.kamailio.org to sr-docs(a)lists.sip-router.org. Info about it at: http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-docs Lately, several discussions touched the documentation aspects, in a need for a better structuring and updates for the new context of sip router project. The old mailing list was active for a while, but with the start of sip router project was ignored because of more focus on integration work. I hope some of you will join, help to build new documentation and spot mistakes in existing versions. Volunteers that want to lead various documentation efforts are more than welcome! Just say what you need... Thanks, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla

1 0

[Kamailio-Users] Kamailio Blocking
by dotnetdub 09 Apr '10

09 Apr '10

Hello List, I have been running a very stable Kamailio 1.4 install for over a year now with no downtime. From time to time I get a message from the OS telling me that task kamailio:xxxx blocked for more than 120 seconds and a dump into syslog. I recently setup Kamailio 3.01 and it's been running for around 3 weeks now. Purely testing at the moment, there is only 1 SIP registration and almost no activity most of the time. I was checking dmesg and: [269844.208011] INFO: task kamailio:28504 blocked for more than 120 seconds. [269844.208093] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [269844.208178] kamailio D f6d77bf8 0 28504 28484 [269844.208180] f771e140 00000082 00000002 f6d77bf8 f7091390 f771e2cc c4019020 00000000 [269844.208184] 00000000 011615c9 f7091398 00000282 00000000 00000000 00000000 ffffffff [269844.208188] f5cba384 f5cba38c f5cba388 f771e140 c02c91ec f6969d68 f5cba38c f771e140 [269844.208191] Call Trace: [269844.208203] [<c02c91ec>] __mutex_lock_slowpath+0x50/0x7b [269844.208208] [<c02c9082>] mutex_lock+0xa/0xb [269844.208210] [<c02b7d4d>] unix_dgram_recvmsg+0x3e/0x231 [269844.208214] [<c0161beb>] get_page_from_freelist+0xc1/0x3e9 [269844.208218] [<c0161045>] __rmqueue_smallest+0x83/0xe3 [269844.208221] [<c025f771>] sock_recvmsg+0xde/0xf9 [269844.208226] [<c01387b0>] autoremove_wake_function+0x0/0x2d [269844.208231] [<c01620e9>] __alloc_pages_internal+0xb5/0x34e [269844.208236] [<c0260595>] sys_recvfrom+0xb4/0x116 [269844.208239] [<c011af13>] do_page_fault+0x0/0x8f9 [269844.208242] [<c0108540>] do_notify_resume+0x5f8/0x649 [269844.208247] [<c011b3c5>] do_page_fault+0x4b2/0x8f9 [269844.208250] [<c0260a48>] sys_socketcall+0x135/0x19e [269844.208254] [<c0108853>] sysenter_past_esp+0x78/0xb1 [269844.208257] [<c02c0000>] xenfb_probe+0xd1/0x35b [269844.208261] ======================= [269844.208262] INFO: task kamailio:28506 blocked for more than 120 seconds. [269844.208314] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [269844.208395] kamailio D d0e00947 0 28506 28484 [269844.208397] f77f8e60 00000082 00000002 d0e00947 00004292 f77f8fec c4024020 00000001 [269844.208401] 00000000 00000001 00000002 00000000 f7091398 00000001 00000001 c01211f2 [269844.208404] f5cba384 f5cba38c f5cba388 f77f8e60 c02c91ec f5cba38c f60add68 f77f8e60 [269844.208408] Call Trace: [269844.208410] [<c01211f2>] __wake_up_sync+0x2a/0x3e [269844.208413] [<c02c91ec>] __mutex_lock_slowpath+0x50/0x7b [269844.208416] [<c02c9082>] mutex_lock+0xa/0xb [269844.208418] [<c02b7d4d>] unix_dgram_recvmsg+0x3e/0x231 [269844.208421] [<c0161beb>] get_page_from_freelist+0xc1/0x3e9 [269844.208424] [<c0161045>] __rmqueue_smallest+0x83/0xe3 [269844.208427] [<c025f771>] sock_recvmsg+0xde/0xf9 [269844.208431] [<c01387b0>] autoremove_wake_function+0x0/0x2d [269844.208435] [<c01620e9>] __alloc_pages_internal+0xb5/0x34e [269844.208440] [<c0260595>] sys_recvfrom+0xb4/0x116 [269844.208444] [<c0180d0d>] cp_new_stat64+0xfc/0x10e [269844.208449] [<c011b3c5>] do_page_fault+0x4b2/0x8f9 [269844.208452] [<c0260a48>] sys_socketcall+0x135/0x19e [269844.208456] [<c0108853>] sysenter_past_esp+0x78/0xb1 [269844.208459] [<c02c0000>] xenfb_probe+0xd1/0x35b [269844.208462] ======================= [274198.229285] INFO: task kamailio:28504 blocked for more than 120 seconds. [274198.229340] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [274198.229422] kamailio D f6d77bf8 0 28504 28484 [274198.229425] f771e140 00000082 00000002 f6d77bf8 f7091390 f771e2cc c4019020 00000000 [274198.229429] 00000000 011615c9 f7091398 00000282 00000000 00000000 00000000 ffffffff [274198.229432] f5cba384 f5cba38c f5cba388 f771e140 c02c91ec f6969d68 f5cba38c f771e140 [274198.229436] Call Trace: [274198.229447] [<c02c91ec>] __mutex_lock_slowpath+0x50/0x7b [274198.229453] [<c02c9082>] mutex_lock+0xa/0xb [274198.229455] [<c02b7d4d>] unix_dgram_recvmsg+0x3e/0x231 [274198.229459] [<c0161beb>] get_page_from_freelist+0xc1/0x3e9 [274198.229463] [<c0161045>] __rmqueue_smallest+0x83/0xe3 [274198.229466] [<c025f771>] sock_recvmsg+0xde/0xf9 [274198.229471] [<c01387b0>] autoremove_wake_function+0x0/0x2d [274198.229476] [<c01620e9>] __alloc_pages_internal+0xb5/0x34e [274198.229481] [<c0260595>] sys_recvfrom+0xb4/0x116 [274198.229484] [<c011af13>] do_page_fault+0x0/0x8f9 [274198.229487] [<c0108540>] do_notify_resume+0x5f8/0x649 [274198.229492] [<c011b3c5>] do_page_fault+0x4b2/0x8f9 [274198.229495] [<c0260a48>] sys_socketcall+0x135/0x19e [274198.229499] [<c0108853>] sysenter_past_esp+0x78/0xb1 [274198.229502] [<c02c0000>] xenfb_probe+0xd1/0x35b [274198.229506] ======================= [274198.229507] INFO: task kamailio:28506 blocked for more than 120 seconds. [274198.229559] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [274198.229641] kamailio D d0e00947 0 28506 28484 [274198.229643] f77f8e60 00000082 00000002 d0e00947 00004292 f77f8fec c4024020 00000001 [274198.229646] 00000000 00000001 00000002 00000000 f7091398 00000001 00000001 c01211f2 [274198.229650] f5cba384 f5cba38c f5cba388 f77f8e60 c02c91ec f5cba38c f60add68 f77f8e60 [274198.229653] Call Trace: [274198.229656] [<c01211f2>] __wake_up_sync+0x2a/0x3e [274198.229659] [<c02c91ec>] __mutex_lock_slowpath+0x50/0x7b [274198.229662] [<c02c9082>] mutex_lock+0xa/0xb [274198.229664] [<c02b7d4d>] unix_dgram_recvmsg+0x3e/0x231 [274198.229667] [<c0161beb>] get_page_from_freelist+0xc1/0x3e9 [274198.229670] [<c0161045>] __rmqueue_smallest+0x83/0xe3 [274198.229673] [<c025f771>] sock_recvmsg+0xde/0xf9 [274198.229677] [<c01387b0>] autoremove_wake_function+0x0/0x2d [274198.229681] [<c01620e9>] __alloc_pages_internal+0xb5/0x34e [274198.229686] [<c0260595>] sys_recvfrom+0xb4/0x116 [274198.229690] [<c0180d0d>] cp_new_stat64+0xfc/0x10e [274198.229696] [<c011b3c5>] do_page_fault+0x4b2/0x8f9 [274198.229699] [<c0260a48>] sys_socketcall+0x135/0x19e [274198.229703] [<c0108853>] sysenter_past_esp+0x78/0xb1 [274198.229706] [<c02c0000>] xenfb_probe+0xd1/0x35b There was no activity when this happened. ON the 1.4 box there could be about 10 sessions setup when it happens. kamctl ps: Process:: ID=14 PID=28504 Type=MI DATAGRAM Process:: ID=15 PID=28505 Type=MI DATAGRAM Process:: ID=16 PID=28506 Type=MI DATAGRAM Even on the old install this doesn't seem to cause any problem and same here on 3.01 but would like to try and solve it. Any idea? Regards, Stephen

4 5

[Kamailio-Users] fr_inv_timer in kam-3.0
by Andreas Granig 09 Apr '10

09 Apr '10

Hi, In the docs at http://kamailio.org/docs/modules/3.0.x/modules/tm.html#fr_inv_timer it says that fr_inv_timer_avp should be defined like this, without $ or $avp: modparam("tm", "fr_inv_timer_avp", "my_fr_inv_timer") In kam <= 1.5 I did it like that: modparam("tm", "fr_inv_timer_avp", "$avp(s:callee_fr_inv_timer)") which doesn't give me an error on startup with kam-3.0 either, but the timer doesn't get fired (I use seconds for that as noted in the docs). If I change it to modparam("tm", "fr_inv_timer_avp", "callee_fr_inv_timer") then I get the error "malformed or non AVP callee_fr_inv_timer AVP definition", same with setting it to "s:callee_fr_inv_timer". Anyhow, it seems to be deprecated anyways, so I'm looking to get t_set_fr() working. I'm just curious how I can use a var or AVP loaded from DB to set the value on-the-fly? t_set_fr(...) seems to allow only constants to be set. Couldn't find anything in the docs regarding that one. Thanks, Andreas

5 14

[Kamailio-Users] drop in branch/onsend-route in kam-3.0
by Andreas Granig 08 Apr '10

08 Apr '10

Hi, Looks like behavior of drop has changed in Kamailio 3.0. Before, I was able to drop() a specific branch in branch_route depending on various checks. http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.0.x#drop still says this is possible, http://kamailio.org/docs/modules/3.0.x/modules/tm.html#t_on_branch says it's not possible. So calling drop() in branch_route has no effect, and I have no idea how to mark a branch in branch_route to be dropped in onsend_route, because checking a bflag doesn't work there, and neither does checking $rU. Any ideas on how to accomplish dropping a specific branch? Andreas

5 7

[Kamailio-Users] Understanding memory-leaks by inspecting PKG/SHM memory status at shutdown
by Iñaki Baz Castillo 08 Apr '10

08 Apr '10

Hi, according to the wiki page: http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory In order to detect a possible memory leak (in PGK or SHM) a good way is enabling memory debugging and shuting down the server, so: "the memory manager will dump the memory status. Normally most of the memory is cleaned during shutdown. If there is memory leak, it should be visible as not-freed memory." But I would like to know how exactly to detect if there is a memoty leak by inspecting the SHM/PKG status, something like this: ----------------------------------------------------------------------------------------------------------------------------- [32715]: Memory status (pkg): [32715]: fm_status (0x701a40): [32715]: heap size= 16777216 [32715]: used= 189696, used+overhead=247392, free=16529824 [32715]: max used (+overhead)= 247392 [32715]: dumping free list: [32715]: hash = 1 fragments no.: 1, unused: 0#012#011#011 bucket size: 8 - 8 (first 8) [32715]: hash = 2058 fragments no.: 1, unused: 0#012#011#011 bucket size: 8388608 - 16777216 (first 16530136) [32715]: TOTAL: 2 free fragments = 16530144 free bytes [32678]: Memory status (shm): [32678]: fm_status (0x7fa57921c000): [32678]: heap size= 67108864 [32678]: used= 16, used+overhead=35872, free=67072992 [32678]: max used (+overhead)= 2821064 [32678]: dumping free list: [32678]: hash = 1 fragments no.: 45, unused: 0#012#011#011 bucket size: 8 - 8 (first 8) [32678]: hash = 2 fragments no.: 4, unused: 0#012#011#011 bucket size: 16 - 16 (first 16) [32678]: hash = 3 fragments no.: 16, unused: 0#012#011#011 bucket size: 24 - 24 (first 24) [32678]: hash = 4 fragments no.: 2, unused: 0#012#011#011 bucket size: 32 - 32 (first 32) [32678]: hash = 5 fragments no.: 1, unused: 0#012#011#011 bucket size: 40 - 40 (first 40) [32678]: hash = 6 fragments no.: 1, unused: 0#012#011#011 bucket size: 48 - 48 (first 48) [32678]: hash = 7 fragments no.: 39, unused: 0#012#011#011 bucket size: 56 - 56 (first 56) [32678]: hash = 8 fragments no.: 1, unused: 0#012#011#011 bucket size: 64 - 64 (first 64) [32678]: hash = 9 fragments no.: 1, unused: 0#012#011#011 bucket size: 72 - 72 (first 72) [32678]: hash = 10 fragments no.: 2, unused: 0#012#011#011 bucket size: 80 - 80 (first 80) [32678]: hash = 15 fragments no.: 1, unused: 0#012#011#011 bucket size: 120 - 120 (first 120) [32678]: hash = 25 fragments no.: 1, unused: 0#012#011#011 bucket size: 200 - 200 (first 200) [32678]: hash = 40 fragments no.: 5, unused: 0#012#011#011 bucket size: 320 - 320 (first 320) [32678]: hash = 112 fragments no.: 1, unused: 0#012#011#011 bucket size: 896 - 896 (first 896) [32678]: hash = 128 fragments no.: 4, unused: 0#012#011#011 bucket size: 1024 - 1024 (first 1024) [32678]: hash = 129 fragments no.: 2, unused: 0#012#011#011 bucket size: 1032 - 1032 (first 1032) [32678]: hash = 224 fragments no.: 1, unused: 0#012#011#011 bucket size: 1792 - 1792 (first 1792) [32678]: hash = 258 fragments no.: 3, unused: 0#012#011#011 bucket size: 2064 - 2064 (first 2064) [32678]: hash = 473 fragments no.: 1, unused: 0#012#011#011 bucket size: 3784 - 3784 (first 3784) [32678]: hash = 1026 fragments no.: 1, unused: 0#012#011#011 bucket size: 8208 - 8208 (first 8208) [32678]: hash = 2049 fragments no.: 2, unused: 0#012#011#011 bucket size: 16384 - 32768 (first 16512) [32678]: hash = 2051 fragments no.: 1, unused: 0#012#011#011 bucket size: 65536 - 131072 (first 98336) [32678]: hash = 2056 fragments no.: 1, unused: 0#012#011#011 bucket size: 2097152 - 4194304 (first 2621440) [32678]: hash = 2060 fragments no.: 1, unused: 0#012#011#011 bucket size: 33554432 - 67108864 (first 64287800) [32678]: TOTAL: 137 free fragments = 67072992 free bytes ----------------------------------------------------------------------------------------------------------------------------- This is, how should look this SHM/PKG status example (after shutdown) in case there is a memory leak? how to detect not-freed memory? Thanks a lot. -- Iñaki Baz Castillo <ibc(a)aliax.net>

2 5

[Kamailio-Users] irc devel meeting
by Daniel-Constantin Mierla 08 Apr '10

08 Apr '10

Hello, I know some of devels are still in Easter vacation, but I hope we can get together soon on irc to sketch the plan for 3.1 release. I propose next week, Wednesday, April 14, 15:00UTC, on #sip-router channel hosted by irc.freenode.net If you are a developer and want to participate, please announce. If it is not possible to attend for major contributors, we can look for another date (eventually start a pool to see the day were most of us are available). Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla

4 4

[Serusers] ReTransmission of CANCELs on 0.9.7
by rupert.organ＠bt.com 08 Apr '10

08 Apr '10

Hi All, Has anyone come up against an issue on 0.9.6 / 0.9.7 whereby a SIP App Server, delivers a CANCEL to the SER. The SER proxies the CANCELs to all the forked endpoints. At the same time it sends "200 Cancelling" back to the SIP App server...(this suppresses CANCEL retransmission from the SIP App server). If one of the CANCELs from the SER to the SIP UA gets lost....the phone keeps ringing. There is no CANCEL retransmission on the SER !!! There is CANCEL retransmission on the SIP App, but when it sends SER replies "no pending branches" Ideally want the SER do CANCEL retransmissions. I understand the timers were rewritten in 0.10.x but this is not hardened version like 0.9.6....any suggestions? Thanks in advance Rupert

4 3

[Kamailio-Users] merging users mailing lists
by Daniel-Constantin Mierla 08 Apr '10

08 Apr '10

Hello, I propose to merge the users mailing lists, most of the traffic these days is about 3.0 and even there are 2 stables branches now, they are sync'ed, so same code more or less. For 3.1 will be one stable branch, falvor selection will be only a matter of make command. Lately common useful topics are discussed on those different mailing lists, notifications and knowledge base building require cross-posting, lot of overhead imo. Any other opinion? Like with devel mailing lists, existing email addresses for users ML can still be used, just that end on same ML. Natural choice will be to have users@kamailio and serusers@iptel to be directed to sr-users(a)lists.sip-router.org Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

6 8

[Kamailio-Users] mc (Midnight Commander) syntax highlighting scheme
by Константин 07 Apr '10

07 Apr '10

Hi all! For easy editing kamailio configuration files I developed a syntax highlighting scheme for mc. Preview The scheme includes basic syntactic structures of Kamailio 1.5, all constants, variables, operators and standart core functions. To install it, download the file kamailio.syntax from attachment and copy it to /usr/share/mc/syntax (for Debian Etch) Next, add to the file /usr/share/mc/syntax/Syntax including: file ..\*\\.cfg$ Kamailio\sconfig include kamailio.syntax Thats all, I hope its helps someone ;) -- Shpinev Konstantin mailto:kks_mail@inbox.ru

3 2

[Kamailio-Users] Version 3
by dotnetdub 07 Apr '10

07 Apr '10

Hi List, Anybody using this in production yet? If so what kind of volume and how is reliability? Looking to move to this platform, looks very good, interested to hear some experiences. Thanks, Stephen

5 6

Re: [Kamailio-Users] Odd Behaviour with Kamailio + TLS
by Hemanshu Patel 02 Apr '10

02 Apr '10

Yes, i had installed self signed certificates via IE. Bria shows it and validates them during registration process, its the call initiation where it creates problem. Kamailio starts without fix_nated_register. With this function it gives configuration file error. and i had load nathelper.so and that is been confirmed via logs -- Regards, Hemanshu Patel SIS,Ahmedabad. M: 09601295238 > Just checking... > > Some time ago, I made some tests with Bria and self signed certs... It was a little tricky to find that I had to install the cert through IE. Did you install them this way? Can you check Bria's log to ensure that the cert is accepted? > > Edson. > > Henning Westerholt escreveu: >> On Thursday 01 April 2010, Hemanshu Patel wrote: >>> yes i did, and log shows that nathelper.so load without any problem. kamailio loads and work perfectly with grandstream devices with TLS and >>> SRTp. it gives problem with Bria softphones only. >>> I am using self signed certificates which works perfectly with grandstream, can there be any chances that due to self sign ness of the >>> certificates, it doesnt work well with bria devices. >> Hi Hemanshu, >> ok, so the error you reported in your previous message is solved. It could be >> possible that the Bria softphone implement a more strict policy with regards >> to the check of the certificates. But you should be able to find something in >> the UA documentation about this, you could ask the vendor or other users. As >> the last resort just test with certificates that are not self signed. ;-) >> Cheers, >> Henning >> _______________________________________________ >> Kamailio (OpenSER) - Users mailing list >> Users(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >

2 2

[Kamailio-Users] Odd Behaviour with Kamailio + TLS
by Hemanshu Patel 01 Apr '10

01 Apr '10

Hi all, I am not sure it is strange behavior or its the desirable one. i have got two phones registered via TLS to kamailio-1.5.X version. phone1: connected via ip1:port1 and having contact value ip1:port2 phone2: connected via ip2:port3 and having contact value ip2:port4 when i have just this two phones i can see 2 TCP connected to my kamailio from both phones from ip1:port1 and ip2:port3. now when i call from phone1 to phone2, rather then using the already established and TLS authenticated connection kamailio creates two new connection from kamailio to ip1:port2 and ip2:port4. mean kamailio creates new connection to the contact value stored in location table of openser DB. Is this the desirable behavior? shouldn't kamailio use the alreay established connection? -- Regards, Hemanshu Patel SIS,Ahmedabad. M: 09601295238

4 6

SEMS 1.2.0 released
by Stefan Sayer 01 Apr '10

01 Apr '10

Hello, it is my pleasure to announce that SEMS 1.2.0 has been released. This release again brings many improvements to this fine, free SIP Media and Application server. Get the source at http://ftp.iptel.org/pub/sems/sems-1.2.0.tar.gz Some debian packages at http://ftp.iptel.org/pub/sems/1.2/1.2.0/packages/ Changelog: http://ftp.iptel.org/pub/sems/doc/current/changelog.html Documentation got some new getting started tutorials: http://ftp.iptel.org/pub/sems/doc/current/index.html And there is now an experimental lenny32 vmware image available, configured as webconference server (but usable for all applications with minimal reconfiguration): https://developer.berlios.de/project/shownotes.php?release_id=17393 For more information see the home page at http://iptel.org/sems . Among the most interesting news I would like to emphasize that its powerful state machine scripting engine DSM has matured a lot between 1.1 and 1.2 versions. Thanks to its growing number of modules (including MySQL DB, conferencing, Python and AWS), live script reloading and monitoring, its interfacing to external applications, and its extended script language it has become a good service development and deployment platform. Other interesting additions is a CMake based build system, an in-memory DB 'monitoring' for administrative and applications use, a twitter app, and numerous fixes and improvements all around. Respect and many Thanks go to all contributors and sponsors of the SEMS project. With Best Regards Stefan Sayer P.S. Apologies if you have received multiple copies of this message. -- Stefan Sayer VoIP Services Consulting and Development Warschauer Str. 24 10243 Berlin tel:+491621366449 sip:sayer@iptel.org email/xmpp:stefan.sayer@gmail.com

1 0

[Serusers] Registration process : 401 then 403, is it possible ?
by inge 01 Apr '10

01 Apr '10

Hi, I'm looking for a workarround to avoid a buggy CPE. The CPE doesn't stop to try to register after he got a 401 Unauthorized. So this produce a flooding. That's why I'm looking for something to send a first 401 and then a 403 if the registration keep failing. Thanks in advance for your idea. Regards, Adrien

1 0

Re: [Kamailio-Users] Users Digest, Vol 58, Issue 76
by Rothe, Marcus, D22-WHV 31 Mar '10

31 Mar '10

"users-request(a)lists.kamailio.org" <users-request(a)lists.kamailio.org> schrieb: Send Users mailing list submissions to users(a)lists.kamailio.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.kamailio.org/cgi-bin/mailman/listinfo/users or, via email, send a message with subject or body 'help' to users-request(a)lists.kamailio.org You can reach the person managing the list at users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Users digest..." Today's Topics: 1. Re: Odd Behaviour with Kamailio + TLS (Klaus Darilion) 2. Re: Registrar: Save modified contact / set the q value (Daniel-Constantin Mierla) 3. Re: more type conversion wonders (Daniel-Constantin Mierla) ---------------------------------------------------------------------- Message: 1 Date: Wed, 31 Mar 2010 11:34:45 +0200 From: Klaus Darilion <klaus.mailinglists(a)pernau.at> Subject: Re: [Kamailio-Users] Odd Behaviour with Kamailio + TLS To: Hemanshu Patel <hemanshu.patel(a)saicare.com> Cc: users(a)lists.kamailio.org Message-ID: <4BB31735.6030500(a)pernau.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Am 31.03.2010 08:56, schrieb Hemanshu Patel: > > Hi all, > > I am not sure it is strange behavior or its the desirable one. > > i have got two phones registered via TLS to kamailio-1.5.X version. > > phone1: connected via ip1:port1 and having contact value ip1:port2 > phone2: connected via ip2:port3 and having contact value ip2:port4 > > when i have just this two phones i can see 2 TCP connected to my kamailio > from both phones from ip1:port1 and ip2:port3. > > now when i call from phone1 to phone2, rather then using the already > established and TLS authenticated connection kamailio creates two new > connection from kamailio to ip1:port2 and ip2:port4. > mean kamailio creates new connection to the contact value stored in > location table of openser DB. > > Is this the desirable behavior? shouldn't kamailio use the alreay > established connection? This is the standard Kamailio behavior. Thus, you should apply NAT traversal techniques to instruct Kamailio to reuse the established connection. In short: for each register call fix_nated_register(). For every other request and response call fix_nated_contact(). Thus, if you use the default configuration and apply NAT traversal it should work. regards klaus ------------------------------ Message: 2 Date: Wed, 31 Mar 2010 11:37:27 +0200 From: Daniel-Constantin Mierla <miconda(a)gmail.com> Subject: Re: [Kamailio-Users] Registrar: Save modified contact / set the q value To: Ovidiu Sas <osas(a)voipembedded.com> Cc: NeoTel Lists <MailingLists(a)neotel.at>, users(a)lists.kamailio.org Message-ID: <4BB317D7.4030102(a)gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 3/30/10 8:29 PM, Ovidiu Sas wrote: > If you need this in 1.5, try to fix the contact header and then > forward the REGISTER back to yourself. > The loopback REGISTER should have the fixed Contact header and now you > can call save(). > You will need to tweak a a little bit the config to get everything > right into the usrloc (the loopback REGISTER will come from the server > IP) and it might work. > it works for no nat scenario, otherwise make sure you will get the looped message on the same socket and you add before looping a header with source ip and port (corresponding nat box pinhole) that you store in received avp. Cheers, Daniel > Regards, > Ovidiu Sas > > On Tue, Mar 30, 2010 at 11:36 AM, NeoTel Lists<MailingLists(a)neotel.at> wrote: > >> Hello Everybody! >> >> Is there any way to save(domain, 0x02) the contact after it has been changed >> somehow in Kamailio<= 1.5? >> Do I have to upgrade to 3.0 and use msg_apply_changes() before save()? >> >> Or: Can I set the to be saved q value somehow? >> >> br >> Walter >> >> _______________________________________________ >> Kamailio (OpenSER) - Users mailing list >> Users(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >> >> > _______________________________________________ > Kamailio (OpenSER) - Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > http://lists.openser-project.org/cgi-bin/mailman/listinfo/users > > -- Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla ------------------------------ Message: 3 Date: Wed, 31 Mar 2010 11:41:29 +0200 From: Daniel-Constantin Mierla <miconda(a)gmail.com> Subject: Re: [Kamailio-Users] more type conversion wonders To: Juha Heinanen <jh(a)tutpro.com> Cc: users(a)lists.sip-router.org Message-ID: <4BB318C9.1080302(a)gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 3/31/10 8:40 AM, Juha Heinanen wrote: > i played a bit more with selects and found that statement > > if ($sht(auth=>foo::count)> @cfg_get.local.gw_timeout) { > xlog("foo"); > } > I guess selects have types, while pseudo-variables are kind of type agnostic. Any PV has a string representation of the value, comparison is done as integer if both PVs are integers, otherwise is done as string. The safe side is to use PV representation of selects when comparing with another PV. PV and selects is another point for the future coherence. Cheers, Daniel > produces error > > 0(9213) :<core> [cfg.y:3379]: parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 507, column 28-55: bad expression: type mismatch: str instead of int at (507,55) > > but the error goes away if i either make explicit conversion > > if ($sht(auth=>foo::count)> (int)(a)cfg_get.local.gw_timeout) { > xlog("foo"); > } > > or use $sel > > if ($sht(auth=>foo::count)> $sel(cfg_get.local.gw_timeout)) { > xlog("foo"); > } > > this is thus exactly opposite than in my t_set_fr ordeal where i got > conversion error when i used $sel instead of @. > > in my opinion, no (int) conversion should be needed in the firs case, > because the value of the cfg variable is int. > > in summary, writing statements that include selects is very difficult > and error prone. > > -- juha > > _______________________________________________ > Kamailio (OpenSER) - Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > http://lists.openser-project.org/cgi-bin/mailman/listinfo/users > > -- Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla ------------------------------ _______________________________________________ Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users End of Users Digest, Vol 58, Issue 76 *************************************

1 0

Re: [Kamailio-Users] Users Digest, Vol 58, Issue 76
by Rothe, Marcus, D22-WHV 31 Mar '10

31 Mar '10

"users-request(a)lists.kamailio.org" <users-request(a)lists.kamailio.org> schrieb: Send Users mailing list submissions to users(a)lists.kamailio.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.kamailio.org/cgi-bin/mailman/listinfo/users or, via email, send a message with subject or body 'help' to users-request(a)lists.kamailio.org You can reach the person managing the list at users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Users digest..." Today's Topics: 1. Re: Odd Behaviour with Kamailio + TLS (Klaus Darilion) 2. Re: Registrar: Save modified contact / set the q value (Daniel-Constantin Mierla) 3. Re: more type conversion wonders (Daniel-Constantin Mierla) ---------------------------------------------------------------------- Message: 1 Date: Wed, 31 Mar 2010 11:34:45 +0200 From: Klaus Darilion <klaus.mailinglists(a)pernau.at> Subject: Re: [Kamailio-Users] Odd Behaviour with Kamailio + TLS To: Hemanshu Patel <hemanshu.patel(a)saicare.com> Cc: users(a)lists.kamailio.org Message-ID: <4BB31735.6030500(a)pernau.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Am 31.03.2010 08:56, schrieb Hemanshu Patel: > > Hi all, > > I am not sure it is strange behavior or its the desirable one. > > i have got two phones registered via TLS to kamailio-1.5.X version. > > phone1: connected via ip1:port1 and having contact value ip1:port2 > phone2: connected via ip2:port3 and having contact value ip2:port4 > > when i have just this two phones i can see 2 TCP connected to my kamailio > from both phones from ip1:port1 and ip2:port3. > > now when i call from phone1 to phone2, rather then using the already > established and TLS authenticated connection kamailio creates two new > connection from kamailio to ip1:port2 and ip2:port4. > mean kamailio creates new connection to the contact value stored in > location table of openser DB. > > Is this the desirable behavior? shouldn't kamailio use the alreay > established connection? This is the standard Kamailio behavior. Thus, you should apply NAT traversal techniques to instruct Kamailio to reuse the established connection. In short: for each register call fix_nated_register(). For every other request and response call fix_nated_contact(). Thus, if you use the default configuration and apply NAT traversal it should work. regards klaus ------------------------------ Message: 2 Date: Wed, 31 Mar 2010 11:37:27 +0200 From: Daniel-Constantin Mierla <miconda(a)gmail.com> Subject: Re: [Kamailio-Users] Registrar: Save modified contact / set the q value To: Ovidiu Sas <osas(a)voipembedded.com> Cc: NeoTel Lists <MailingLists(a)neotel.at>, users(a)lists.kamailio.org Message-ID: <4BB317D7.4030102(a)gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 3/30/10 8:29 PM, Ovidiu Sas wrote: > If you need this in 1.5, try to fix the contact header and then > forward the REGISTER back to yourself. > The loopback REGISTER should have the fixed Contact header and now you > can call save(). > You will need to tweak a a little bit the config to get everything > right into the usrloc (the loopback REGISTER will come from the server > IP) and it might work. > it works for no nat scenario, otherwise make sure you will get the looped message on the same socket and you add before looping a header with source ip and port (corresponding nat box pinhole) that you store in received avp. Cheers, Daniel > Regards, > Ovidiu Sas > > On Tue, Mar 30, 2010 at 11:36 AM, NeoTel Lists<MailingLists(a)neotel.at> wrote: > >> Hello Everybody! >> >> Is there any way to save(domain, 0x02) the contact after it has been changed >> somehow in Kamailio<= 1.5? >> Do I have to upgrade to 3.0 and use msg_apply_changes() before save()? >> >> Or: Can I set the to be saved q value somehow? >> >> br >> Walter >> >> _______________________________________________ >> Kamailio (OpenSER) - Users mailing list >> Users(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >> >> > _______________________________________________ > Kamailio (OpenSER) - Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > http://lists.openser-project.org/cgi-bin/mailman/listinfo/users > > -- Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla ------------------------------ Message: 3 Date: Wed, 31 Mar 2010 11:41:29 +0200 From: Daniel-Constantin Mierla <miconda(a)gmail.com> Subject: Re: [Kamailio-Users] more type conversion wonders To: Juha Heinanen <jh(a)tutpro.com> Cc: users(a)lists.sip-router.org Message-ID: <4BB318C9.1080302(a)gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 3/31/10 8:40 AM, Juha Heinanen wrote: > i played a bit more with selects and found that statement > > if ($sht(auth=>foo::count)> @cfg_get.local.gw_timeout) { > xlog("foo"); > } > I guess selects have types, while pseudo-variables are kind of type agnostic. Any PV has a string representation of the value, comparison is done as integer if both PVs are integers, otherwise is done as string. The safe side is to use PV representation of selects when comparing with another PV. PV and selects is another point for the future coherence. Cheers, Daniel > produces error > > 0(9213) :<core> [cfg.y:3379]: parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 507, column 28-55: bad expression: type mismatch: str instead of int at (507,55) > > but the error goes away if i either make explicit conversion > > if ($sht(auth=>foo::count)> (int)(a)cfg_get.local.gw_timeout) { > xlog("foo"); > } > > or use $sel > > if ($sht(auth=>foo::count)> $sel(cfg_get.local.gw_timeout)) { > xlog("foo"); > } > > this is thus exactly opposite than in my t_set_fr ordeal where i got > conversion error when i used $sel instead of @. > > in my opinion, no (int) conversion should be needed in the firs case, > because the value of the cfg variable is int. > > in summary, writing statements that include selects is very difficult > and error prone. > > -- juha > > _______________________________________________ > Kamailio (OpenSER) - Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > http://lists.openser-project.org/cgi-bin/mailman/listinfo/users > > -- Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla ------------------------------ _______________________________________________ Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users End of Users Digest, Vol 58, Issue 76 *************************************

1 0

[Kamailio-Users] more type conversion wonders
by jh＠tutpro.com 31 Mar '10

31 Mar '10

i played a bit more with selects and found that statement if ($sht(auth=>foo::count) > @cfg_get.local.gw_timeout) { xlog("foo"); } produces error 0(9213) : <core> [cfg.y:3379]: parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 507, column 28-55: bad expression: type mismatch: str instead of int at (507,55) but the error goes away if i either make explicit conversion if ($sht(auth=>foo::count) > (int)(a)cfg_get.local.gw_timeout) { xlog("foo"); } or use $sel if ($sht(auth=>foo::count) > $sel(cfg_get.local.gw_timeout)) { xlog("foo"); } this is thus exactly opposite than in my t_set_fr ordeal where i got conversion error when i used $sel instead of @. in my opinion, no (int) conversion should be needed in the firs case, because the value of the cfg variable is int. in summary, writing statements that include selects is very difficult and error prone. -- juha

2 1

[Kamailio-Users] Registrar: Save modified contact / set the q value
by NeoTel Lists 31 Mar '10

31 Mar '10

Hello Everybody! Is there any way to save(domain, 0x02) the contact after it has been changed somehow in Kamailio <= 1.5? Do I have to upgrade to 3.0 and use msg_apply_changes() before save()? Or: Can I set the to be saved q value somehow? br Walter

4 8

Re: [Kamailio-Users] Registrar: Save modified contact / set the qvalue
by NeoTel Lists 30 Mar '10

30 Mar '10

Again sorry, too much trial&error makes a lot of noise ... if (avp_subst("$(avp(contact))", "/;phone-context=q([01]\.[0-9]+)(.*>)?([^>]*)/\2\3;q=\1/i")) { # just to have it handy int that var(Q) $var(Q) = $(avp(contact){s.select,1,>}{param.value,q}); remove_hf("Contact"); append_hf("Contact: $(avp(contact))\r\n"); # must not add q= twice } -> Same result: q=-1 in Database. -----Ursprüngliche Nachricht----- Von: users-bounces(a)lists.kamailio.org [mailto:users-bounces@lists.kamailio.org] Im Auftrag von NeoTel Lists Gesendet: Dienstag, 30. März 2010 18:56 An: Alex Balashov; users(a)lists.kamailio.org Betreff: Re: [Kamailio-Users] Registrar: Save modified contact / set the qvalue Sorry for being unclear: I meant: Modify the contact in the script, then do save(). E.g. $(avp(contact)) = $ct; # Those Patton can't send the q value ... Misuse their ;phone-context param if (avp_subst("$(avp(contact))", "/;phone-context=q([01]\.[0-9])(.*>)?([^>]*)/\2\3;q=\1/i")) { # just to have it handy int that var(Q) $var(Q) = $(avp(contact){s.select,1,>}{param.value,q}); remove_hf("Contact"); append_hf("Contact: $(avp(contact));q=$var(Q)r\n"); # subst() does the same, also not save()ed } ... setbflag(1); fix_nated_register(); save("contactimpl_nat", "0x02"); Br Walter -----Ursprüngliche Nachricht----- Von: users-bounces(a)lists.kamailio.org [mailto:users-bounces@lists.kamailio.org] Im Auftrag von Alex Balashov Gesendet: Dienstag, 30. März 2010 17:58 An: users(a)lists.kamailio.org Betreff: Re: [Kamailio-Users] Registrar: Save modified contact / set the q value On 03/30/2010 11:36 AM, NeoTel Lists wrote: > Hello Everybody! > Is there any way to save(domain, 0x02) the contact after it has been > changed somehow in Kamailio <= 1.5? If it were not possible, how would nathelper:fix_nated_contact() work? -- Alex Balashov - Principal Evariste Systems LLC Tel : +1 678-954-0670 Direct : +1 678-954-0671 Web : http://www.evaristesys.com/ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

2 2

Re: [Kamailio-Users] Registrar: Save modified contact / set the q value
by NeoTel Lists 30 Mar '10

30 Mar '10

Sorry for being unclear: I meant: Modify the contact in the script, then do save(). E.g. $(avp(contact)) = $ct; # Those Patton can't send the q value ... Misuse their ;phone-context param if (avp_subst("$(avp(contact))", "/;phone-context=q([01]\.[0-9])(.*>)?([^>]*)/\2\3;q=\1/i")) { # just to have it handy int that var(Q) $var(Q) = $(avp(contact){s.select,1,>}{param.value,q}); remove_hf("Contact"); append_hf("Contact: $(avp(contact));q=$var(Q)r\n"); # subst() does the same, also not save()ed } ... setbflag(1); fix_nated_register(); save("contactimpl_nat", "0x02"); Br Walter -----Ursprüngliche Nachricht----- Von: users-bounces(a)lists.kamailio.org [mailto:users-bounces@lists.kamailio.org] Im Auftrag von Alex Balashov Gesendet: Dienstag, 30. März 2010 17:58 An: users(a)lists.kamailio.org Betreff: Re: [Kamailio-Users] Registrar: Save modified contact / set the q value On 03/30/2010 11:36 AM, NeoTel Lists wrote: > Hello Everybody! > Is there any way to save(domain, 0x02) the contact after it has been > changed somehow in Kamailio <= 1.5? If it were not possible, how would nathelper:fix_nated_contact() work? -- Alex Balashov - Principal Evariste Systems LLC Tel : +1 678-954-0670 Direct : +1 678-954-0671 Web : http://www.evaristesys.com/ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

1 0

[Kamailio-Users] Quick REGEX to match Private IP
by Uriel Rozenbaum 30 Mar '10

30 Mar '10

Hi guys, Does anyone have a REGEX syntax to match a private IP on the 192.168.x.x range? I'm trying with: if($avp(s:ip_origen)=~"192.168(\.([1]?\d{1,2}|2[0-4]{1}\d{1}|25[0-5]{1})){2}" ) But all IPs pass as private, even public ones. Thanks! Uriel

4 6

[Kamailio-Users] Fast lock loop with arm
by Zappasodi Daniele 30 Mar '10

30 Mar '10

Hi, I have a big problem with fast lock mutex on arm CPU: sometimes I find one or more children that go in an infinite loop, in the while loop of get_lock function. They remain in Run for long time (sometimes hours) and openser keeps 100% CPU. Now I have changed the functions get_lock and tsl in order to obtain more info and I observe that (if and) when the process finish the cycle, it have done a big amount of cycles. This the log with my added info: Mar 26 20:29:08 SAM-IP openser[1645]: NOTICE:tm:_lock: ret 1 (cycle) Mar 26 20:29:51 SAM-IP openser[1645]: NOTICE:tm:_lock: ret 1 (cycle) Mar 26 20:29:55 SAM-IP openser[1645]: NOTICE:tm:_lock: ret 1 (cycle) Mar 26 20:29:55 SAM-IP openser[1645]: NOTICE:tm:t_retransmit_reply: MYTM lock [process in loop] Mar 26 20:33:46 SAM-IP openser[1645]: NOTICE:tm:_lock: ret 59374917 (cycle) [after 4 minutes and 59374917 cycles, this is an example with a "short" loop] Mar 26 20:33:46 SAM-IP openser[1645]: NOTICE:tm:t_retransmit_reply: MYTM lock done I'm not able to recognize the call flow that generates the loop (I know only that it always happens when t_retransmit_reply calls LOCK_REPLIES), but I urgently need a work around to escape from the loop. This is the get_lock function with my counter j: inline static int get_lock(fl_lock_t* lock) { #ifdef ADAPTIVE_WAIT int i=ADAPTIVE_WAIT_LOOPS; int j=1; /***** my change ****/ #endif while(tsl(lock)){ #ifdef BUSY_WAIT #elif defined ADAPTIVE_WAIT j++; /***** my change ****/ if (i>0) i--; else sched_yield(); #else sched_yield(); #endif } return(j); } Can I break the lock when my counter reaches a big value? Should I call the unlock function after the break? which value can be considered too big? Thanks, Daniele ********************************************************************** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. **********************************************************************

2 7

[Kamailio-Users] Kammailio as proxy and clustered asterisk as registrar
by Vic Jolin 30 Mar '10

30 Mar '10

Hi, I would like to seek help from the list regarding my setup. I have kamailio setup to send any sip messages to load balance asterisk clusters. The registration part is successful. The calling part is not, calls get dropped, I believe it's rtp issue or maybe nat. I'm very new to kamailio and would like to ask for help on this. Tia!

3 2

[Kamailio-Users] kam 1.5 sqlops sql_query timeout value
by Robert McGilvray 30 Mar '10

30 Mar '10

Hello, I'm using the sqlops module for some custom queries against mysql. Sometimes during a cluster failure the mysqld nodes will hang there waiting for the backend to finish up whatever it's doing, it still accepts the connection and the query but doesn't return results. I have a pair of F5 load balancers in front of the two sql nodes, so there is redundancy as long as the cluster is operational. I'd prefer to keep the cross-site failover in kamailio. I looked through the docs on sqlops and I can't find any reference to a timeout value. I'd like to implement a failover in the script to my other database cluster but if kam waits for a long time before returning a negative it may not work very well. Consider this code in my script for 911 services in my US offices: (I rewrite the rpid/pai and ruri based on IP address then send it to my provider(s)) modparam("sqlops","sqlcon","gokam=>mysql://*****:*****@172.20.180.21/sip _gokam") if (!sql_query("gokam", "select location,cidname,cidnum,ciddomain,e911number,inet_ntoa(network) as network,inet_ntoa(netmask) \ as netmask from e911 where (inet_aton('$si') & netmask) = network", "result")) { sl_send_reply("500", "Database error"); exit; } What I'd like to do is: modparam("sqlops","sqlcon","gokam=>mysql://****:****@172.20.180.21/sip_g okam") modparam("sqlops","sqlcon","gokam_site2=>mysql://*****:*****@172.23.180. 21/sip_gokam") if (!sql_query("gokam", "select location,cidname,cidnum,ciddomain,e911number,inet_ntoa(network) as network,inet_ntoa(netmask) \ as netmask from e911 where (inet_aton('$si') & netmask) = network", "result")) { xlog("L_CRIT", "Primary database failure, using alternate\n"); if (!sql_query("gokam_site2", "select location,cidname,cidnum,ciddomain,e911number,inet_ntoa(network) as network,inet_ntoa(netmask) \ as netmask from e911 where (inet_aton('$si') & netmask) = network", "result")) { sl_send_reply("500", Database error"); exit; } What is the default timeout for sql_query before it returns a negative, is it configurable? Thanks! Bob -------------------------------------------------------------------------- This email with all information contained herein or attached hereto may contain confidential and/or privileged information intended for the addressee(s) only. If you have received this email in error, please contact the sender and immediately delete this email in its entirety and any attachments thereto.

3 2

[Kamailio-Users] get warning when sip client is not online
by s.maertens＠telenet.be 30 Mar '10

30 Mar '10

Hello, I have a kamailio setup running for several SIP devices. I would like to be warned whenever one of those devices is not reacheable anymore. That means when they go offline or are not anymore registered to the kamailio server. (timeout, unregister, ...). I am using the location table so we would be able to write a script that just at specific times checks the difference between the subscriber table and the location table but maybe there is a much better and more realtime solution. So basically the question is : how to execute a script whenever a host gets removed fom the location table. I am running Kamailio 3.0.1 All hints are very much appreciated :)

3 2

[Kamailio-Users] GSoC 2010 Student Registration is Open
by Daniel-Constantin Mierla 30 Mar '10

30 Mar '10

Hello, if you are a student (or know one) interested in working with SIP and Presence over the summer, earn some money and experience, you have the choice of Kamailio - SIP Router project within SIP Communicator organization: http://www.kamailio.org/w/gsoc-2010/ Registration is now open, up to April 9, more details in above link. If you have further questions, drop an email. Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla

1 0

ser avp question
by jh＠tutpro.com 29 Mar '10

29 Mar '10

modules_s/domain domain_lookup() function can be used to assign domain attributes to avps. for example, lookup_domain("$fd", "foo.bar"), assigns attributes of domain foo.bar to avps $fd.x, where x is name of attribute. my question is, how can i index these avps if there is more than one with the same name? statement $var(attr) = $fd.attr[]; does not give syntax errors, but $var(attr) = $fd.attr[$var(i)]; produces 0(7368) : <core> [cfg.y:3379]: parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 3174, column 24-30: syntax error 0(7368) : <core> [cfg.y:3379]: parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 3174, column 24-30: bad command 0(7368) : <core> [cfg.y:3382]: parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 3174, column 31: bad command 0(7368) : <core> [cfg.y:3382]: parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 3174, column 31: bad command -- juha

3 5

weird dp_translate() behavior
by jh＠tutpro.com 29 Mar '10

29 Mar '10

while playing with dp_translate(), i noticed the following weird behavior. i have a rule with dpid=11, where match_exp='^\+' and subst_exp and repl_exp are empty. my test goes like this: $rU = "+35892345670"; if (dp_translate("11", $rU/$rU")) { xlog("ruri user is '$rU'\n"); }; $var(test) = "+35892345670"; if (dp_translate("11", "$var(test)/$var(test)")) { xlog("var(test) is '$var(test)'\n"); }; and this is produced to syslog: Mar 29 20:01:39 localhost /usr/sbin/sip-proxy[20533]: ERROR: ruri user is '+35892345670' Mar 29 20:01:39 localhost /usr/sbin/sip-proxy[20533]: ERROR: var(test) is '' that is, $rU is not translated to empty string, but $var(test) is. can someone provide an explanation for this? what should the expected behavior be, when subst_exp and repl_exp are empty? original author of dialplan module is Andreea-Ancuta Onofrei, but i don't know if he is still around. -- juha

1 1

@msg.%s syntax
by jh＠tutpro.com 29 Mar '10

29 Mar '10

first section of page http://sip-router.org/wiki/cookbooks/selects/devel had example @msg.["P-anyheader-youwant"]) that, however, produced syntax error. i removed the dot and got rid of the error. i then went and fixed the wiki page too. however, later on the page there still is @msg.%s and many more like that. are they generated automatically? if so, then fixing them on the wiki page would not help. also, is there somewhere a summary of pv syntax of s and k flavors? -- juha

2 5

Re: [Kamailio-Users] Problem with secure TLS call
by Hemanshu Patel 29 Mar '10

29 Mar '10

With TLS it still is not working Mar 27 11:39:16 [4421] INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255 kb Mar 27 11:39:16 [4425] WARNING:usrloc:dbrow2info: non-local socket <tcp:172.16.16.218:5091>...ignoring Mar 27 11:39:18 [4431] INFO:core:tls_accept: client did not present a certificate Mar 27 11:39:55 [4432] INFO:core:tls_accept: client did not present a certificate Mar 27 11:40:01 [4431] ERROR:rr:w_record_route: Double attempt to record-route Mar 27 11:40:01 [4426] ERROR:core:tls_connect: SSL_ERROR_SYSCALL err=Connection reset by peer(104) Mar 27 11:40:01 [4426] ERROR:core:tls_connect: something wrong in SSL: 5 (ret=-1) err=Connection reset by peer(104) Mar 27 11:40:01 [4426] ERROR:core:tcp_send: failed to send Mar 27 11:40:01 [4426] ERROR:core:msg_send: tcp_send failed Mar 27 11:40:01 [4425] WARNING:core:run_actions: null action list (rec_level=1) my doubt is that if somethings wrong with SSL certificates that i created myself (i.e my own root CA, and self signed certificates), then how come registration is working like charm? if there is some problem with Certificates then registration should also not work. am i right? ---- Regards, Hemanshu Patel Sr. Software Engg SIS,Ahmedabad Mo:09601295238 On Sat 27/03/10 9:50 AM , "Hemanshu Patel" <hemanshu.patel(a)saicare.com> wrote: > I havent tested over TCP, let me check it > but hardphone, i mean hardware based phones from grandstream gvx3140 > works > fine with same implementation on TLS. > -- > Regards, > Hemanshu Patel > M: 09601295238 > > Does eyebeam with SIP over TCP is working? > > > > Am 26.03.2010 13:43, schrieb Hemanshu Patel: > >> > >> i am still having this problem. > >> when i use two grandstream phone everything works fine, > >> i can make calls on TLS and users can talk to each other. > >> > >> But when i use two eyebream phone, it doesnt work, gives > following error > >> > >> :33 [2875] WARNING:core:init_ssl_ctx_behavior: server > verification NOT > >> activated. Weaker security. > >> [ panreg-tls]$ > >> [ panreg-tls]$ > >> [ panreg-tls]$ Mar 26 18:11:59 [2889] > >> ERROR:rr:w_record_route: Double attempt to record-route > >> Mar 26 18:12:09 [2884] ERROR:core:tcp_blocking_connect: timeout > 10 s > >> elapsed from 10 s > >> Mar 26 18:12:09 [2884] ERROR:core:tcpconn_connect: > tcp_blocking_connect > >> failed > >> Mar 26 18:12:09 [2884] ERROR:core:tcp_send: connect failed > >> Mar 26 18:12:09 [2884] ERROR:core:msg_send: tcp_send failed > >> Mar 26 18:12:10 [2883] ERROR:core:tcp_blocking_connect: timeout > 10 s > >> elapsed from 10 s > >> Mar 26 18:12:10 [2883] ERROR:core:tcpconn_connect: > tcp_blocking_connect > >> failed > >> Mar 26 18:12:10 [2883] ERROR:core:tcp_send: connect failed > >> Mar 26 18:12:10 [2883] ERROR:core:msg_send: tcp_send failed > >> Mar 26 18:12:10 [2883] WARNING:core:run_actions: null action list > >> (rec_level=1) > >> Mar 26 18:12:11 [2881] ERROR:core:tcp_blocking_connect: timeout > 10 s > >> elapsed from 10 s > >> Mar 26 18:12:11 [2881] ERROR:core:tcpconn_connect: > tcp_blocking_connect > >> failed > >> Mar 26 18:12:11 [2881] ERROR:core:tcp_send: connect failed > >> Mar 26 18:12:11 [2881] ERROR:core:msg_send: tcp_send failed > >> Mar 26 18:12:13 [2882] ERROR:core:tcp_blocking_connect: timeout > 10 s > >> elapsed from 10 s > >> Mar 26 18:12:13 [2882] ERROR:core:tcpconn_connect: > tcp_blocking_connect > >> failed > >> Mar 26 18:12:13 [2882] ERROR:core:tcp_send: connect failed > >> Mar 26 18:12:13 [2882] ERROR:core:msg_send: tcp_send failed > >> Mar 26 18:12:19 [2884] ERROR:core:tcp_blocking_connect: timeout > 10 s > >> elapsed from 10 s > >> Mar 26 18:12:19 [2884] ERROR:core:tcpconn_connect: > tcp_blocking_connect > >> failed > >> Mar 26 18:12:19 [2884] ERROR:core:tcp_send: connect failed > >> Mar 26 18:12:19 [2884] ERROR:core:msg_send: tcp_send failed > >> > >> > >> > >> Any idea? Same configuration works with grandstream, while they > cant in > >> softphone? and gives 477 errot code. > >> > >> my asterisk log is as below: > >> > >> 26 18:08:09] WARNING[2833]: chan_sip.c:1648 setup_crypto: > Hemanshu: > >> local_key641 jhbAJ7jFE1p/Ngn4kVxy7qTTmkJpeBiN6W98+gmM len 40 > >> -- Called kamailio/1003 > >> -- Got SIP response 477 "Send failed (477/SL)" back from > >> 172.16.16.218 > >> -- No one is available to answer at this time (1:0/0/0) > >> -- Executing [_default:4] Hangup("SIP/5091-8c001430", "") > >> in > >> new stack > >> == Spawn extension (hemu_default, 1003, 4) exited non-zero on > >> 'SIP/5091-8c001430' > >> > ::Disconnected form Oracle, trying to connect again.. > >> > ::Tried a lot, not getting connected.. > >> -- Got SIP response 477 "Send failed (477/SL)" back from > >> 172.16.16.218 > >> > >> > >> Any idea what could be the problem? > >> > > > _______________________________________________ > Kamailio (OpenSER) - Users mailing list > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > http://lists.openser-project.org/cgi-bin/mailman/listinfo/users > > ---- SIS Blade Server, Desktop & Thin Client is now available on DGS & D rate contract. For more detail kindly visit our website http://www.saicare.com

2 4

Re: [Kamailio-Users] Problem with secure TLS call
by Hemanshu Patel 29 Mar '10

29 Mar '10

Here is the complete call log for One call from two clients eyebream and bria running on single PC. Mar 27 12:36:36 [5492] DBG:core:destroy_avp_list: destroying list (nil) Mar 27 12:36:36 [5492] DBG:core:receive_msg: cleaning up Mar 27 12:36:42 [5492] DBG:core:tcp_receive_timeout: 0x7fd335f04798 expired (50, 51) lt=0 Mar 27 12:36:42 [5492] DBG:core:io_watch_del: io_watch_del (0x74efe0, 18, -1, 0x10) fd_no=2 called Mar 27 12:36:42 [5492] DBG:core:release_tcpconn: releasing con 0x7fd335f04798, state 0, fd=18, id=3 Mar 27 12:36:42 [5492] DBG:core:release_tcpconn: extra_data 0x7fd335f017b8 Mar 27 12:36:42 [5499] DBG:core:handle_tcp_child: reader response= 7fd335f04798, 0 from 0 Mar 27 12:36:42 [5499] DBG:core:io_watch_add: io_watch_add(0x74ee80, 24, 2, 0x7fd335f04798), fd_no=17 Mar 27 12:36:42 [5499] DBG:core:handle_tcp_child: cmd CONN_RELEASE 0x7fd335f04798 refcnt= 0 Mar 27 12:36:45 [5499] DBG:core:handle_tcpconn_ev: data available on 0x7fd335eddc18 23 Mar 27 12:36:45 [5499] DBG:core:io_watch_del: io_watch_del (0x74ee80, 23, -1, 0x0) fd_no=18 called Mar 27 12:36:45 [5499] DBG:core:send2child: to tcp child 0 0(5492), 0x7fd335eddc18 Mar 27 12:36:45 [5492] DBG:core:handle_io: received n=8 con=0x7fd335eddc18, fd=18 Mar 27 12:36:45 [5492] DBG:core:io_watch_add: io_watch_add(0x74efe0, 18, 2, 0x7fd335eddc18), fd_no=1 Mar 27 12:36:45 [5492] DBG:core:tls_update_fd: New fd is 18 Mar 27 12:36:45 [5492] DBG:core:_tls_read: 1109 bytes read Mar 27 12:36:45 [5492] DBG:core:tcp_read_req: content-length= 512 Mar 27 12:36:45 [5492] DBG:core:parse_msg: SIP Request: Mar 27 12:36:45 [5492] DBG:core:parse_msg: method: <INVITE> Mar 27 12:36:45 [5492] DBG:core:parse_msg: uri: <sip:1002@172.16.16.218:5091;transport=tls> Mar 27 12:36:45 [5492] DBG:core:parse_msg: version: <SIP/2.0> Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=2 Mar 27 12:36:45 [5492] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK-d8754z-e333132001727d6d-1---d8754z->; state=6 Mar 27 12:36:45 [5492] DBG:core:parse_via_param: found param type 235, <rport> = <n/a>; state=17 Mar 27 12:36:45 [5492] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5492] DBG:core:parse_headers: via found, flags=2 Mar 27 12:36:45 [5492] DBG:core:parse_headers: this is the first via Mar 27 12:36:45 [5492] DBG:core:receive_msg: After parse_msg... Mar 27 12:36:45 [5492] DBG:core:receive_msg: preparing to run routing scripts... Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=100 Mar 27 12:36:45 [5492] DBG:maxfwd:is_maxfwd_present: value = 70 Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=8 Mar 27 12:36:45 [5492] DBG:core:parse_to: end of header reached, state=10 Mar 27 12:36:45 [5492] DBG:core:parse_to: display={}, ruri={sip:1002@172.16.16.218:5091} Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: <To> [31]; uri=[sip:1002@172.16.16.218:5091] Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: to body [<sip:1002@172.16.16.218:5091> ] Mar 27 12:36:45 [5492] DBG:siputils:has_totag: no totag Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=78 Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: cseq <CSeq>: <1> <INVITE> Mar 27 12:36:45 [5492] DBG:tm:t_lookup_request: start searching: hash=44320, isACK=0 Mar 27 12:36:45 [5492] DBG:tm:matching_3261: RFC3261 transaction matching failed Mar 27 12:36:45 [5492] DBG:tm:t_lookup_request: no transaction found Mar 27 12:36:45 [5492] DBG:core:parse_to_param: tag=9f574228 Mar 27 12:36:45 [5492] DBG:core:parse_to: end of header reached, state=29 Mar 27 12:36:45 [5492] DBG:core:parse_to: display={"1003"}, ruri={sip:1003@172.16.16.218:5091} Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if host==us: 13==13 && [172.16.16.218] == [172.16.16.218] Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if port 5090 matches port 5091 Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if host==us: 13==13 && [172.16.16.218] == [172.16.16.218] Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if port 5092 matches port 5091 Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if host==us: 13==13 && [172.16.16.218] == [172.16.16.218] Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if port 5091 matches port 5091 Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: match found for: [172.16.16.218:5091] Mar 27 12:36:45 [5492] DBG:core:check_self: host == me Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=10000 Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: content_length=512 Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: found end of header Mar 27 12:36:45 [5492] DBG:auth:pre_auth: credentials with given realm not found Mar 27 12:36:45 [5492] DBG:auth:reserve_nonce_index: second= 22, sec_monit= -1, index= 3 Mar 27 12:36:45 [5492] DBG:auth:build_auth_hf: nonce index= 3 Mar 27 12:36:45 [5492] DBG:auth:build_auth_hf: 'Proxy-Authenticate: Digest realm="172.16.16.218", nonce="4badaea30000000316e854bb0194116d66618a39dcd9340c" ' Mar 27 12:36:45 [5492] DBG:sl:send_reply: reply in stateless mode (sl) Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=ffffffffffffffff Mar 27 12:36:45 [5492] DBG:core:check_via_address: params 172.16.17.85, 172.16.17.85, 0 Mar 27 12:36:45 [5492] DBG:core:tcp_send: tcp connection found (0x7fd335eddc18), acquiring fd Mar 27 12:36:45 [5492] DBG:core:tcp_send: c= 0x7fd335eddc18, n=16 Mar 27 12:36:45 [5499] DBG:core:handle_ser_child: read response= 7fd335eddc18, 1, fd -1 from 7 (5492) Mar 27 12:36:45 [5492] DBG:core:tcp_send: after receive_fd: c= 0x7fd335eddc18 n=8 fd=19 Mar 27 12:36:45 [5492] DBG:core:tcp_send: sending... Mar 27 12:36:45 [5492] DBG:core:tls_update_fd: New fd is 19 Mar 27 12:36:45 [5492] DBG:core:tls_write: write was successful (519 bytes) Mar 27 12:36:45 [5492] DBG:core:tcp_send: after write: c= 0x7fd335eddc18 n=519 fd=19 Mar 27 12:36:45 [5492] DBG:core:tcp_send: buf= SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/TLS 172.16.17.85:4403;branch=z9hG4bK-d8754z-e333132001727d6d-1---d8754z-;rport=1301 To: <sip:1002@172.16.16.218:5091>;tag=2cf7f9a22b6374f465182a893bba7dec.5636 From: "1003"<sip:1003@172.16.16.218:5091>;tag=9f574228 Call-ID: M2Y2OThmYmYwZjM4ODhhYzk4Mjc0MGFhMDQyNDUzZWU. CSeq: 1 INVITE Proxy-Authenticate: Digest realm="172.16.16.218", nonce="4badaea30000000316e854bb0194116d66618a39dcd9340c" Server: Kamailio (1.5.4-tls (x86_64/linux)) Content-Length: 0 Mar 27 12:36:45 [5492] DBG:core:destroy_avp_list: destroying list (nil) Mar 27 12:36:45 [5492] DBG:core:receive_msg: cleaning up Mar 27 12:36:45 [5492] DBG:core:tls_update_fd: New fd is 18 Mar 27 12:36:45 [5492] DBG:core:_tls_read: 370 bytes read Mar 27 12:36:45 [5492] DBG:core:tcp_read_req: content-length= 0 Mar 27 12:36:45 [5492] DBG:core:parse_msg: SIP Request: Mar 27 12:36:45 [5492] DBG:core:parse_msg: method: <ACK> Mar 27 12:36:45 [5492] DBG:core:parse_msg: uri: <sip:1002@172.16.16.218:5091;transport=tls> Mar 27 12:36:45 [5492] DBG:core:parse_msg: version: <SIP/2.0> Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=2 Mar 27 12:36:45 [5492] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK-d8754z-e333132001727d6d-1---d8754z->; state=6 Mar 27 12:36:45 [5492] DBG:core:parse_via_param: found param type 235, <rport> = <n/a>; state=17 Mar 27 12:36:45 [5492] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5492] DBG:core:parse_headers: via found, flags=2 Mar 27 12:36:45 [5492] DBG:core:parse_headers: this is the first via Mar 27 12:36:45 [5492] DBG:core:receive_msg: After parse_msg... Mar 27 12:36:45 [5492] DBG:core:receive_msg: preparing to run routing scripts... Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=8 Mar 27 12:36:45 [5492] DBG:core:parse_to_param: tag=2cf7f9a22b6374f465182a893bba7dec.5636 Mar 27 12:36:45 [5492] DBG:core:parse_to: end of header reached, state=29 Mar 27 12:36:45 [5492] DBG:core:parse_to: display={}, ruri={sip:1002@172.16.16.218:5091} Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: <To> [73]; uri=[sip:1002@172.16.16.218:5091] Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: to body [<sip:1002@172.16.16.218:5091>] Mar 27 12:36:45 [5492] DBG:sl:sl_filter_ACK: local ACK found -> dropping it! Mar 27 12:36:45 [5492] DBG:core:destroy_avp_list: destroying list (nil) Mar 27 12:36:45 [5492] DBG:core:receive_msg: cleaning up Mar 27 12:36:45 [5492] DBG:core:tls_update_fd: New fd is 18 Mar 27 12:36:45 [5492] DBG:core:_tls_read: 1339 bytes read Mar 27 12:36:45 [5492] DBG:core:tcp_read_req: content-length= 512 Mar 27 12:36:45 [5492] DBG:core:parse_msg: SIP Request: Mar 27 12:36:45 [5492] DBG:core:parse_msg: method: <INVITE> Mar 27 12:36:45 [5492] DBG:core:parse_msg: uri: <sip:1002@172.16.16.218:5091;transport=tls> Mar 27 12:36:45 [5492] DBG:core:parse_msg: version: <SIP/2.0> Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=2 Mar 27 12:36:45 [5492] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK-d8754z-863b295f961d253f-1---d8754z->; state=6 Mar 27 12:36:45 [5492] DBG:core:parse_via_param: found param type 235, <rport> = <n/a>; state=17 Mar 27 12:36:45 [5492] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5492] DBG:core:parse_headers: via found, flags=2 Mar 27 12:36:45 [5492] DBG:core:parse_headers: this is the first via Mar 27 12:36:45 [5492] DBG:core:receive_msg: After parse_msg... Mar 27 12:36:45 [5492] DBG:core:receive_msg: preparing to run routing scripts... Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=100 Mar 27 12:36:45 [5492] DBG:maxfwd:is_maxfwd_present: value = 70 Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=8 Mar 27 12:36:45 [5492] DBG:core:parse_to: end of header reached, state=10 Mar 27 12:36:45 [5492] DBG:core:parse_to: display={}, ruri={sip:1002@172.16.16.218:5091} Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: <To> [31]; uri=[sip:1002@172.16.16.218:5091] Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: to body [<sip:1002@172.16.16.218:5091> ] Mar 27 12:36:45 [5492] DBG:siputils:has_totag: no totag Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=78 Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: cseq <CSeq>: <2> <INVITE> Mar 27 12:36:45 [5492] DBG:tm:t_lookup_request: start searching: hash=44317, isACK=0 Mar 27 12:36:45 [5492] DBG:tm:matching_3261: RFC3261 transaction matching failed Mar 27 12:36:45 [5492] DBG:tm:t_lookup_request: no transaction found Mar 27 12:36:45 [5492] DBG:core:parse_to_param: tag=9f574228 Mar 27 12:36:45 [5492] DBG:core:parse_to: end of header reached, state=29 Mar 27 12:36:45 [5492] DBG:core:parse_to: display={"1003"}, ruri={sip:1003@172.16.16.218:5091} Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if host==us: 13==13 && [172.16.16.218] == [172.16.16.218] Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if port 5090 matches port 5091 Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if host==us: 13==13 && [172.16.16.218] == [172.16.16.218] Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if port 5092 matches port 5091 Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if host==us: 13==13 && [172.16.16.218] == [172.16.16.218] Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: checking if port 5091 matches port 5091 Mar 27 12:36:45 [5492] DBG:core:grep_sock_info: match found for: [172.16.16.218:5091] Mar 27 12:36:45 [5492] DBG:core:check_self: host == me Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=10000 Mar 27 12:36:45 [5492] DBG:auth:check_nonce: comparing [4badaea30000000316e854bb0194116d66618a39dcd9340c] and [4badaea30000000316e854bb0194116d66618a39dcd9340c] Mar 27 12:36:45 [5492] DBG:core:db_new_result: allocate 48 bytes for result set at 0x78d6c8 Mar 27 12:36:45 [5492] DBG:db_mysql:db_mysql_get_columns: 1 columns returned from the query Mar 27 12:36:45 [5492] DBG:core:db_allocate_columns: allocate 8 bytes for result names at 0x78aab8 Mar 27 12:36:45 [5492] DBG:core:db_allocate_columns: allocate 4 bytes for result types at 0x79ea58 Mar 27 12:36:45 [5492] DBG:db_mysql:db_mysql_get_columns: allocate 16 bytes for RES_NAMES[0] at 0x78d010 Mar 27 12:36:45 [5492] DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x78d010)[0]=[password] Mar 27 12:36:45 [5492] DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type Mar 27 12:36:45 [5492] DBG:core:db_allocate_rows: allocate 16 bytes for rows at 0x79ea38 Mar 27 12:36:45 [5492] DBG:core:db_allocate_row: allocate 32 bytes for row values at 0x79ea78 Mar 27 12:36:45 [5492] DBG:core:db_str2val: converting STRING [1234] Mar 27 12:36:45 [5492] DBG:auth_db:get_ha1: HA1 string calculated: 6650a5aab1d658b465ee304e21b8db36 Mar 27 12:36:45 [5492] DBG:auth:check_response: our result = '19406efa15546eb60e105c164a1feb3d' Mar 27 12:36:45 [5492] DBG:auth:check_response: authorization is OK Mar 27 12:36:45 [5492] DBG:auth:post_auth: nonce index= 3 Mar 27 12:36:45 [5492] DBG:core:db_free_columns: freeing 1 columns Mar 27 12:36:45 [5492] DBG:core:db_free_columns: freeing RES_NAMES[0] at 0x78d010 Mar 27 12:36:45 [5492] DBG:core:db_free_columns: freeing result names at 0x78aab8 Mar 27 12:36:45 [5492] DBG:core:db_free_columns: freeing result types at 0x79ea58 Mar 27 12:36:45 [5492] DBG:core:db_free_rows: freeing 1 rows Mar 27 12:36:45 [5492] DBG:core:db_free_row: freeing row values at 0x79ea78 Mar 27 12:36:45 [5492] DBG:core:db_free_rows: freeing rows at 0x79ea38 Mar 27 12:36:45 [5492] DBG:core:db_free_result: freeing result set at 0x78d6c8 Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=14000 Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: content_length=512 Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: found end of header Mar 27 12:36:45 [5492] DBG:core:comp_scriptvar: str 29 : 1003 ---- Invite ---- Mar 27 12:36:45 [5492] DBG:core:comp_scriptvar: str 29 : 1003 Mar 27 12:36:45 [5492] ERROR:rr:w_record_route: Double attempt to record-route Mar 27 12:36:45 [5492] DBG:dispatcher:ds_select_dst: set [1] Mar 27 12:36:45 [5492] DBG:dispatcher:ds_select_dst: alg hash [789753065] Mar 27 12:36:45 [5492] DBG:dispatcher:ds_select_dst: selected [0-1/0] <sip:172.16.16.218:5070> Mar 27 12:36:45 [5492] DBG:tm:t_newtran: transaction on entrance=(nil) Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=ffffffffffffffff Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=78 Mar 27 12:36:45 [5492] DBG:tm:t_lookup_request: start searching: hash=44317, isACK=0 Mar 27 12:36:45 [5492] DBG:tm:matching_3261: RFC3261 transaction matching failed Mar 27 12:36:45 [5492] DBG:tm:t_lookup_request: no transaction found Mar 27 12:36:45 [5492] DBG:tm:run_reqin_callbacks: trans=0x7fd335eee6b0, callback type 1, id 0 entered Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=ffffffffffffffff Mar 27 12:36:45 [5492] DBG:core:check_via_address: params 172.16.17.85, 172.16.17.85, 0 Mar 27 12:36:45 [5492] DBG:core:_shm_resize: resize(0) called Mar 27 12:36:45 [5492] DBG:core:tcp_send: tcp connection found (0x7fd335eddc18), acquiring fd Mar 27 12:36:45 [5492] DBG:core:tcp_send: c= 0x7fd335eddc18, n=16 Mar 27 12:36:45 [5499] DBG:core:handle_ser_child: read response= 7fd335eddc18, 1, fd -1 from 7 (5492) Mar 27 12:36:45 [5492] DBG:core:tcp_send: after receive_fd: c= 0x7fd335eddc18 n=8 fd=19 Mar 27 12:36:45 [5492] DBG:core:tcp_send: sending... Mar 27 12:36:45 [5492] DBG:core:tls_update_fd: New fd is 19 Mar 27 12:36:45 [5492] DBG:core:tls_write: write was successful (352 bytes) Mar 27 12:36:45 [5492] DBG:core:tcp_send: after write: c= 0x7fd335eddc18 n=352 fd=19 Mar 27 12:36:45 [5492] DBG:core:tcp_send: buf= SIP/2.0 100 Giving a try Via: SIP/2.0/TLS 172.16.17.85:4403;branch=z9hG4bK-d8754z-863b295f961d253f-1---d8754z-;rport=1301 To: <sip:1002@172.16.16.218:5091> From: "1003"<sip:1003@172.16.16.218:5091>;tag=9f574228 Call-ID: M2Y2OThmYmYwZjM4ODhhYzk4Mjc0MGFhMDQyNDUzZWU. CSeq: 2 INVITE Server: Kamailio (1.5.4-tls (x86_64/linux)) Content-Length: 0 Mar 27 12:36:45 [5492] DBG:tm:_reply_light: reply sent out. buf=0x79f5e8: SIP/2.0 1..., shmem=0x7fd335f007a8: SIP/2.0 1 Mar 27 12:36:45 [5492] DBG:tm:_reply_light: finished Mar 27 12:36:45 [5492] DBG:core:mk_proxy: doing DNS lookup... Mar 27 12:36:45 [5492] DBG:core:build_req_buf_from_sip_req: id added: <;i=1>, rcv proto=3 Mar 27 12:36:45 [5492] DBG:tm:set_timer: relative timeout is 500000 Mar 27 12:36:45 [5492] DBG:tm:insert_timer_unsafe: [4]: 0x7fd335eee8d0 (54200000) Mar 27 12:36:45 [5492] DBG:tm:set_timer: relative timeout is 30 Mar 27 12:36:45 [5492] DBG:tm:insert_timer_unsafe: [0]: 0x7fd335eee900 (83) Mar 27 12:36:45 [5492] DBG:tm:t_relay_to: new transaction fwd'ed Mar 27 12:36:45 [5492] DBG:tm:t_unref: UNREF_UNSAFE: after is 0 Mar 27 12:36:45 [5492] DBG:core:destroy_avp_list: destroying list (nil) Mar 27 12:36:45 [5492] DBG:core:receive_msg: cleaning up Mar 27 12:36:45 [5487] DBG:core:parse_msg: SIP Reply (status): Mar 27 12:36:45 [5487] DBG:core:parse_msg: version: <SIP/2.0> Mar 27 12:36:45 [5487] DBG:core:parse_msg: status: <100> Mar 27 12:36:45 [5487] DBG:core:parse_msg: reason: <Trying> Mar 27 12:36:45 [5487] DBG:core:parse_headers: flags=2 Mar 27 12:36:45 [5487] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bKd1da.1a6f9b73.0>; state=6 Mar 27 12:36:45 [5487] DBG:core:parse_via_param: found param type 236, = <1>; state=6 Mar 27 12:36:45 [5487] DBG:core:parse_via_param: found param type 234, <received> = <172.16.16.218>; state=16 Mar 27 12:36:45 [5487] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5487] DBG:core:parse_headers: via found, flags=2 Mar 27 12:36:45 [5487] DBG:core:parse_headers: this is the first via Mar 27 12:36:45 [5487] DBG:core:receive_msg: After parse_msg... Mar 27 12:36:45 [5487] DBG:core:forward_reply: found module tm, passing reply to it Mar 27 12:36:45 [5487] DBG:tm:t_check: start=0xffffffffffffffff Mar 27 12:36:45 [5487] DBG:core:parse_headers: flags=22 Mar 27 12:36:45 [5487] DBG:core:parse_via_param: found param type 234, <received> = <172.16.17.85>; state=6 Mar 27 12:36:45 [5487] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK-d8754z-863b295f961d253f-1---d8754z->; state=6 Mar 27 12:36:45 [5487] DBG:core:parse_via_param: found param type 235, <rport> = <1301>; state=16 Mar 27 12:36:45 [5487] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5487] DBG:core:parse_headers: via found, flags=22 Mar 27 12:36:45 [5487] DBG:core:parse_headers: parse_headers: this is the second via Mar 27 12:36:45 [5487] DBG:core:parse_to: end of header reached, state=10 Mar 27 12:36:45 [5487] DBG:core:parse_to: display={}, ruri={sip:1002@172.16.16.218:5091} Mar 27 12:36:45 [5487] DBG:core:get_hdr_field: <To> [31]; uri=[sip:1002@172.16.16.218:5091] Mar 27 12:36:45 [5487] DBG:core:get_hdr_field: to body [<sip:1002@172.16.16.218:5091> ] Mar 27 12:36:45 [5487] DBG:core:get_hdr_field: cseq <CSeq>: <2> <INVITE> Mar 27 12:36:45 [5487] DBG:core:parse_headers: flags=8 Mar 27 12:36:45 [5487] DBG:tm:t_reply_matching: hash 44317 label 934934177 branch 0 Mar 27 12:36:45 [5487] DBG:tm:t_reply_matching: REF_UNSAFE: after is 1 Mar 27 12:36:45 [5487] DBG:tm:t_reply_matching: reply matched (T=0x7fd335eee6b0)! Mar 27 12:36:45 [5487] DBG:tm:t_check: end=0x7fd335eee6b0 Mar 27 12:36:45 [5487] DBG:tm:reply_received: org. status uas=100, uac[0]=0 local=0 is_invite=1) Mar 27 12:36:45 [5487] DBG:tm:t_should_relay_response: T_code=100, new_code=100 Mar 27 12:36:45 [5487] DBG:tm:relay_reply: branch=0, save=0, relay=-1 Mar 27 12:36:45 [5487] DBG:tm:set_timer: relative timeout is 120 Mar 27 12:36:45 [5487] DBG:tm:insert_timer_unsafe: [1]: 0x7fd335eee900 (173) Mar 27 12:36:45 [5487] DBG:tm:t_unref: UNREF_UNSAFE: after is 0 Mar 27 12:36:45 [5487] DBG:core:destroy_avp_list: destroying list (nil) Mar 27 12:36:45 [5487] DBG:core:receive_msg: cleaning up Mar 27 12:36:45 [5489] DBG:core:parse_msg: SIP Request: Mar 27 12:36:45 [5489] DBG:core:parse_msg: method: <INVITE> Mar 27 12:36:45 [5489] DBG:core:parse_msg: uri: <sip:1002@172.16.16.218:5090> Mar 27 12:36:45 [5489] DBG:core:parse_msg: version: <SIP/2.0> Mar 27 12:36:45 [5489] DBG:core:parse_headers: flags=2 Mar 27 12:36:45 [5489] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK7f71d414>; state=6 Mar 27 12:36:45 [5489] DBG:core:parse_via_param: found param type 235, <rport> = <n/a>; state=17 Mar 27 12:36:45 [5489] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5489] DBG:core:parse_headers: via found, flags=2 Mar 27 12:36:45 [5489] DBG:core:parse_headers: this is the first via Mar 27 12:36:45 [5489] DBG:core:receive_msg: After parse_msg... Mar 27 12:36:45 [5489] DBG:core:receive_msg: preparing to run routing scripts... Mar 27 12:36:45 [5489] DBG:core:parse_headers: flags=100 Mar 27 12:36:45 [5489] DBG:core:parse_to: end of header reached, state=10 Mar 27 12:36:45 [5489] DBG:core:parse_to: display={}, ruri={sip:1002@172.16.16.218:5090} Mar 27 12:36:45 [5489] DBG:core:get_hdr_field: <To> [31]; uri=[sip:1002@172.16.16.218:5090] Mar 27 12:36:45 [5489] DBG:core:get_hdr_field: to body [<sip:1002@172.16.16.218:5090> ] Mar 27 12:36:45 [5489] DBG:core:get_hdr_field: cseq <CSeq>: <102> <INVITE> Mar 27 12:36:45 [5489] DBG:maxfwd:is_maxfwd_present: value = 70 ---- From SC/MS/IC ---- Mar 27 12:36:45 [5489] DBG:core:rewrite_uri: rewriting Request-URI with 'sip:1002@172.16.17.85:25923;rinstance=133b23266b1f2e83;transport=TLS' Mar 27 12:36:45 [5489] DBG:core:mk_proxy: doing DNS lookup... Mar 27 12:36:45 [5489] DBG:core:parse_headers: flags=2000 Mar 27 12:36:45 [5489] DBG:core:get_hdr_field: content_length=394 Mar 27 12:36:45 [5489] DBG:core:forward_request: sending: INVITE sip:1002@172.16.17.85:25923;rinstance=133b23266b1f2e83;transport=TLS SIP/2.0 Record-Route: <sip:172.16.16.218:5091;transport=tls;r2=on;lr=on> Record-Route: <sip:172.16.16.218:5090;r2=on;lr=on> Via: SIP/2.0/TLS 172.16.16.218:5091;branch=z9hG4bK7f71d414 Via: SIP/2.0/UDP 172.16.16.218:5070;received=172.16.16.218;branch=z9hG4bK7f71d414;rport=5070 From: "1003" <sip:1003@172.16.16.218:5070>;tag=as7351a581 To: <sip:1002@172.16.16.218:5090> Contact: <sip:1003@172.16.16.218:5070> Call-ID: 7c10eaf0305d3dff6dac07db404d5a60(a)172.16.16.218 CSeq: 102 INVITE User-Agent: PANTHER-SC Max-Forwards: 69 Date: Sat, 27 Mar 2010 07:06:45 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Type: application/sdp Content-Length: 394 v=0 o=root 2434 2434 IN IP4 172.16.17.85 s=session c=IN IP4 172.16.17.85 t=0 0 m=audio 54168 RTP/SAVP 0 18 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - a=ptime:20 a=sendrecv AES_CM_128_HMAC_SHA1_80 inline:qGi2zArgAgHDiUoqc0wbBofpBISpZINZxrqDoa7W . Mar 27 12:36:45 [5489] DBG:core:forward_request: orig. len=935, new_len=1182, proto=3 Mar 27 12:36:45 [5489] DBG:core:tcp_send: no open tcp connection found, opening new one Mar 27 12:36:45 [5489] DBG:core:print_ip: tcpconn_new: new tcp connection to: 172.16.17.85 Mar 27 12:36:45 [5489] DBG:core:tcpconn_new: on port 25923, type 3 Mar 27 12:36:45 [5489] DBG:core:tls_tcpconn_init: entered: Creating a whole new ssl connection Mar 27 12:36:45 [5489] DBG:core:tls_tcpconn_init: name based TLS client domains are disabled Mar 27 12:36:45 [5489] DBG:core:tls_tcpconn_init: no TLS client domain AVP set, looking for socket based TLS client domain Mar 27 12:36:45 [5489] DBG:core:tls_find_client_domain: virtual TLS client domain not found, Using default TLS client domain settings Mar 27 12:36:45 [5489] DBG:core:tls_tcpconn_init: found socket based TLS client domain [0.0.0.0:0] Mar 27 12:36:45 [5489] DBG:core:tls_tcpconn_init: Setting in CONNECT mode (client) Mar 27 12:36:45 [5489] DBG:core:tls_tcpconn_init: TLS server extension is not activated Mar 27 12:36:45 [5489] DBG:core:tls_tcpconn_init: TLS server name is not set, sending ClientHello without server_name Mar 27 12:36:45 [5489] DBG:core:tcp_send: sending... Mar 27 12:36:45 [5489] DBG:core:tls_update_fd: New fd is 12 Mar 27 12:36:45 [5499] DBG:core:handle_ser_child: read response= 7fd335f23098, 2, fd 25 from 4 (5489) Mar 27 12:36:45 [5499] DBG:core:tcpconn_add: hashes: 495, 4 Mar 27 12:36:45 [5499] DBG:core:io_watch_add: io_watch_add(0x74ee80, 25, 2, 0x7fd335f23098), fd_no=17 Mar 27 12:36:45 [5499] DBG:core:handle_tcpconn_ev: data available on 0x7fd335f23098 25 Mar 27 12:36:45 [5489] ERROR:core:tls_connect: SSL_ERROR_SYSCALL err=Connection reset by peer(104) Mar 27 12:36:45 [5499] DBG:core:io_watch_del: io_watch_del (0x74ee80, 25, -1, 0x0) fd_no=18 called Mar 27 12:36:45 [5489] ERROR:core:tls_connect: something wrong in SSL: 5 (ret=-1) err=Connection reset by peer(104) Mar 27 12:36:45 [5499] DBG:core:send2child: to tcp child 1 0(5494), 0x7fd335f23098 Mar 27 12:36:45 [5489] DBG:core:tcp_send: after write: c= 0x7fd335f23098 n=-1 fd=12 Mar 27 12:36:45 [5489] DBG:core:tcp_send: buf= INVITE sip:1002@172.16.17.85:25923;rinstance=133b23266b1f2e83;transport=TLS SIP/2.0 Record-Route: <sip:172.16.16.218:5091;transport=tls;r2=on;lr=on> Record-Route: <sip:172.16.16.218:5090;r2=on;lr=on> Via: SIP/2.0/TLS 172.16.16.218:5091;branch=z9hG4bK7f71d414 Via: SIP/2.0/UDP 172.16.16.218:5070;received=172.16.16.218;branch=z9hG4bK7f71d414;rport=5070 From: "1003" <sip:1003@172.16.16.218:5070>;tag=as7351a581 To: <sip:1002@172.16.16.218:5090> Contact: <sip:1003@172.16.16.218:5070> Call-ID: 7c10eaf0305d3dff6dac07db404d5a60(a)172.16.16.218 CSeq: 102 INVITE User-Agent: PANTHER-SC Max-Forwards: 69 Date: Sat, 27 Mar 2010 07:06:45 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Type: application/sdp Content-Length: 394 v=0 o=root 2434 2434 IN IP4 172.16.17.85 s=session c=IN IP4 172.16.17.85 t=0 0 m=audio 54168 RTP/SAVP 0 18 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - a=ptime:20 a=sendrecv AES_CM_128_HMAC_SHA1_80 inline:qGi2zArgAgHDiUoqc0wbBofpBISpZINZxrqDoa7W Mar 27 12:36:45 [5494] DBG:core:handle_io: received n=8 con=0x7fd335f23098, fd=20 Mar 27 12:36:45 [5489] ERROR:core:tcp_send: failed to send Mar 27 12:36:45 [5494] DBG:core:io_watch_add: io_watch_add(0x74efe0, 20, 2, 0x7fd335f23098), fd_no=1 Mar 27 12:36:45 [5489] ERROR:core:msg_send: tcp_send failed Mar 27 12:36:45 [5494] DBG:core:io_watch_del: io_watch_del (0x74efe0, 20, -1, 0x10) fd_no=2 called Mar 27 12:36:45 [5494] DBG:core:release_tcpconn: releasing con 0x7fd335f23098, state -2, fd=20, id=4 Mar 27 12:36:45 [5494] DBG:core:release_tcpconn: extra_data 0x7fd335f00ef8 Mar 27 12:36:45 [5489] DBG:sl:sl_reply_error: error text is Send failed (477/SL) Mar 27 12:36:45 [5499] DBG:core:handle_tcp_child: reader response= 7fd335f23098, -2 from 1 Mar 27 12:36:45 [5499] DBG:core:tcpconn_destroy: delaying (0x7fd335f23098, flags 0002) ... Mar 27 12:36:45 [5489] DBG:core:parse_headers: flags=ffffffffffffffff Mar 27 12:36:45 [5489] DBG:core:get_hdr_field: found end of header Mar 27 12:36:45 [5499] DBG:core:handle_ser_child: read response= 7fd335f23098, -2, fd -1 from 4 (5489) Mar 27 12:36:45 [5499] DBG:core:tcpconn_destroy: destroying connection 0x7fd335f23098, flags 0002 Mar 27 12:36:45 [5489] DBG:core:check_via_address: params 172.16.16.218, 172.16.16.218, 0 Mar 27 12:36:45 [5499] DBG:core:tls_close: closing SSL connection Mar 27 12:36:45 [5499] DBG:core:tls_update_fd: New fd is 25 Mar 27 12:36:45 [5499] DBG:core:tls_shutdown: shutdown successful Mar 27 12:36:45 [5499] DBG:core:tls_tcpconn_clean: Cleanup function entered Mar 27 12:36:45 [5486] DBG:core:parse_msg: SIP Request: Mar 27 12:36:45 [5486] DBG:core:parse_msg: method: <ACK> Mar 27 12:36:45 [5486] DBG:core:parse_msg: uri: <sip:1002@172.16.16.218:5090> Mar 27 12:36:45 [5486] DBG:core:parse_msg: version: <SIP/2.0> Mar 27 12:36:45 [5486] DBG:core:parse_headers: flags=2 Mar 27 12:36:45 [5486] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK7f71d414>; state=6 Mar 27 12:36:45 [5486] DBG:core:parse_via_param: found param type 235, <rport> = <n/a>; state=17 Mar 27 12:36:45 [5486] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5486] DBG:core:parse_headers: via found, flags=2 Mar 27 12:36:45 [5486] DBG:core:parse_headers: this is the first via Mar 27 12:36:45 [5486] DBG:core:receive_msg: After parse_msg... Mar 27 12:36:45 [5486] DBG:core:receive_msg: preparing to run routing scripts... Mar 27 12:36:45 [5486] DBG:core:parse_headers: flags=8 Mar 27 12:36:45 [5486] DBG:core:parse_to_param: tag=2cf7f9a22b6374f465182a893bba7dec.adb6 Mar 27 12:36:45 [5486] DBG:core:parse_to: end of header reached, state=29 Mar 27 12:36:45 [5486] DBG:core:parse_to: display={}, ruri={sip:1002@172.16.16.218:5090} Mar 27 12:36:45 [5486] DBG:core:get_hdr_field: <To> [73]; uri=[sip:1002@172.16.16.218:5090] Mar 27 12:36:45 [5486] DBG:core:get_hdr_field: to body [<sip:1002@172.16.16.218:5090>] Mar 27 12:36:45 [5486] DBG:sl:sl_filter_ACK: local ACK found -> dropping it! Mar 27 12:36:45 [5486] DBG:core:destroy_avp_list: destroying list (nil) Mar 27 12:36:45 [5486] DBG:core:receive_msg: cleaning up Mar 27 12:36:45 [5489] DBG:core:destroy_avp_list: destroying list (nil) Mar 27 12:36:45 [5489] DBG:core:receive_msg: cleaning up Mar 27 12:36:45 [5485] DBG:core:parse_msg: SIP Reply (status): Mar 27 12:36:45 [5485] DBG:core:parse_msg: version: <SIP/2.0> Mar 27 12:36:45 [5485] DBG:core:parse_msg: status: <404> Mar 27 12:36:45 [5485] DBG:core:parse_msg: reason: <Not Found> Mar 27 12:36:45 [5485] DBG:core:parse_headers: flags=2 Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bKd1da.1a6f9b73.0>; state=6 Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 236, = <1>; state=6 Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 234, <received> = <172.16.16.218>; state=16 Mar 27 12:36:45 [5485] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5485] DBG:core:parse_headers: via found, flags=2 Mar 27 12:36:45 [5485] DBG:core:parse_headers: this is the first via Mar 27 12:36:45 [5485] DBG:core:receive_msg: After parse_msg... Mar 27 12:36:45 [5485] DBG:core:forward_reply: found module tm, passing reply to it Mar 27 12:36:45 [5485] DBG:tm:t_check: start=0xffffffffffffffff Mar 27 12:36:45 [5485] DBG:core:parse_headers: flags=22 Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 234, <received> = <172.16.17.85>; state=6 Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK-d8754z-863b295f961d253f-1---d8754z->; state=6 Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 235, <rport> = <1301>; state=16 Mar 27 12:36:45 [5485] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5485] DBG:core:parse_headers: via found, flags=22 Mar 27 12:36:45 [5485] DBG:core:parse_headers: parse_headers: this is the second via Mar 27 12:36:45 [5485] DBG:core:parse_to_param: tag=as06cb485b Mar 27 12:36:45 [5485] DBG:core:parse_to: end of header reached, state=29 Mar 27 12:36:45 [5485] DBG:core:parse_to: display={}, ruri={sip:1002@172.16.16.218:5091} Mar 27 12:36:45 [5485] DBG:core:get_hdr_field: <To> [46]; uri=[sip:1002@172.16.16.218:5091] Mar 27 12:36:45 [5485] DBG:core:get_hdr_field: to body [<sip:1002@172.16.16.218:5091>] Mar 27 12:36:45 [5485] DBG:core:get_hdr_field: cseq <CSeq>: <2> <INVITE> Mar 27 12:36:45 [5485] DBG:core:parse_headers: flags=8 Mar 27 12:36:45 [5485] DBG:tm:t_reply_matching: hash 44317 label 934934177 branch 0 Mar 27 12:36:45 [5485] DBG:tm:t_reply_matching: REF_UNSAFE: after is 1 Mar 27 12:36:45 [5485] DBG:tm:t_reply_matching: reply matched (T=0x7fd335eee6b0)! Mar 27 12:36:45 [5485] DBG:tm:t_check: end=0x7fd335eee6b0 Mar 27 12:36:45 [5485] DBG:tm:reply_received: org. status uas=100, uac[0]=100 local=0 is_invite=1) Mar 27 12:36:45 [5485] DBG:core:parse_headers: flags=8 Mar 27 12:36:45 [5485] DBG:tm:build_local: using FROM=<From: "1003"<sip:1003@172.16.16.218:5091>;tag=9f574228 >, TO=<To: <sip:1002@172.16.16.218:5091>;tag=as06cb485b >, CSEQ_N=<CSeq: 2> Mar 27 12:36:45 [5485] DBG:tm:extract_parsed_hdrs: ----parsing the buf req - first line Mar 27 12:36:45 [5485] DBG:core:parse_headers: flags=ffffffffffffffff Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bKd1da.1a6f9b73.0>; state=6 Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 236, = <1>; state=16 Mar 27 12:36:45 [5485] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5485] DBG:core:parse_headers: via found, flags=ffffffffffffffff Mar 27 12:36:45 [5485] DBG:core:parse_headers: this is the first via Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 234, <received> = <172.16.17.85>; state=6 Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK-d8754z-863b295f961d253f-1---d8754z->; state=6 Mar 27 12:36:45 [5485] DBG:core:parse_via_param: found param type 235, <rport> = <1301>; state=16 Mar 27 12:36:45 [5485] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5485] DBG:core:parse_headers: via found, flags=ffffffffffffffff Mar 27 12:36:45 [5485] DBG:core:parse_headers: parse_headers: this is the second via Mar 27 12:36:45 [5485] DBG:core:parse_to: end of header reached, state=10 Mar 27 12:36:45 [5485] DBG:core:parse_to: display={}, ruri={sip:1002@172.16.16.218:5091} Mar 27 12:36:45 [5485] DBG:core:get_hdr_field: <To> [31]; uri=[sip:1002@172.16.16.218:5091] Mar 27 12:36:45 [5485] DBG:core:get_hdr_field: to body [<sip:1002@172.16.16.218:5091> ] Mar 27 12:36:45 [5485] DBG:core:get_hdr_field: cseq <CSeq>: <2> <INVITE> Mar 27 12:36:45 [5485] DBG:core:get_hdr_field: content_length=512 Mar 27 12:36:45 [5485] DBG:core:get_hdr_field: found end of header Mar 27 12:36:45 [5485] DBG:tm:t_should_relay_response: T_code=100, new_code=404 Mar 27 12:36:45 [5485] DBG:tm:t_pick_branch: picked branch 0, code 404 Mar 27 12:36:45 [5485] DBG:tm:is_3263_failure: dns-failover test: branch=0, last_recv=404, flags=2 Mar 27 12:36:45 [5485] WARNING:core:run_actions: null action list (rec_level=1) Mar 27 12:36:45 [5485] DBG:tm:relay_reply: branch=0, save=0, relay=0 Mar 27 12:36:45 [5485] DBG:core:parse_headers: flags=2000 Mar 27 12:36:45 [5485] DBG:core:get_hdr_field: content_length=0 Mar 27 12:36:45 [5485] DBG:core:build_res_buf_from_sip_res: old size: 548, new size: 454 Mar 27 12:36:45 [5485] DBG:core:build_res_buf_from_sip_res: copied size: orig:117, new: 23, rest: 431 msg= SIP/2.0 404 Not Found Via: SIP/2.0/TLS 172.16.17.85:4403;received=172.16.17.85;branch=z9hG4bK-d8754z-863b295f961d253f-1---d8754z-;rport=1301 From: "1003"<sip:1003@172.16.16.218:5091>;tag=9f574228 To: <sip:1002@172.16.16.218:5091>;tag=as06cb485b Call-ID: M2Y2OThmYmYwZjM4ODhhYzk4Mjc0MGFhMDQyNDUzZWU. CSeq: 2 INVITE User-Agent: PANTHER-SC Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 Mar 27 12:36:45 [5485] DBG:tm:set_timer: relative timeout is 30 Mar 27 12:36:45 [5485] DBG:tm:insert_timer_unsafe: [0]: 0x7fd335eee828 (83) Mar 27 12:36:45 [5485] DBG:core:tcp_send: tcp connection found (0x7fd335eddc18), acquiring fd Mar 27 12:36:45 [5485] DBG:core:tcp_send: c= 0x7fd335eddc18, n=16 Mar 27 12:36:45 [5499] DBG:core:handle_ser_child: read response= 7fd335eddc18, 1, fd -1 from 1 (5485) Mar 27 12:36:45 [5485] DBG:core:tcp_send: after receive_fd: c= 0x7fd335eddc18 n=8 fd=9 Mar 27 12:36:45 [5485] DBG:core:tcp_send: sending... Mar 27 12:36:45 [5485] DBG:core:tls_update_fd: New fd is 9 Mar 27 12:36:45 [5485] DBG:core:tls_write: write was successful (454 bytes) Mar 27 12:36:45 [5485] DBG:core:tcp_send: after write: c= 0x7fd335eddc18 n=454 fd=9 Mar 27 12:36:45 [5485] DBG:core:tcp_send: buf= SIP/2.0 404 Not Found Via: SIP/2.0/TLS 172.16.17.85:4403;received=172.16.17.85;branch=z9hG4bK-d8754z-863b295f961d253f-1---d8754z-;rport=1301 From: "1003"<sip:1003@172.16.16.218:5091>;tag=9f574228 To: <sip:1002@172.16.16.218:5091>;tag=as06cb485b Call-ID: M2Y2OThmYmYwZjM4ODhhYzk4Mjc0MGFhMDQyNDUzZWU. CSeq: 2 INVITE User-Agent: PANTHER-SC Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 Mar 27 12:36:45 [5485] DBG:tm:relay_reply: sent buf=0x7916f0: SIP/2.0 4..., shmem=0x7fd335f007a8: SIP/2.0 4 Mar 27 12:36:45 [5485] DBG:tm:cleanup_uac_timers: RETR/FR timers reset Mar 27 12:36:45 [5485] DBG:tm:t_unref: UNREF_UNSAFE: after is 0 Mar 27 12:36:45 [5485] DBG:core:destroy_avp_list: destroying list (nil) Mar 27 12:36:45 [5485] DBG:core:receive_msg: cleaning up Mar 27 12:36:45 [5492] DBG:core:tls_update_fd: New fd is 18 Mar 27 12:36:45 [5492] DBG:core:_tls_read: 343 bytes read Mar 27 12:36:45 [5492] DBG:core:tcp_read_req: content-length= 0 Mar 27 12:36:45 [5492] DBG:core:parse_msg: SIP Request: Mar 27 12:36:45 [5492] DBG:core:parse_msg: method: <ACK> Mar 27 12:36:45 [5492] DBG:core:parse_msg: uri: <sip:1002@172.16.16.218:5091;transport=tls> Mar 27 12:36:45 [5492] DBG:core:parse_msg: version: <SIP/2.0> Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=2 Mar 27 12:36:45 [5492] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK-d8754z-863b295f961d253f-1---d8754z->; state=6 Mar 27 12:36:45 [5492] DBG:core:parse_via_param: found param type 235, <rport> = <n/a>; state=17 Mar 27 12:36:45 [5492] DBG:core:parse_via: end of header reached, state=5 Mar 27 12:36:45 [5492] DBG:core:parse_headers: via found, flags=2 Mar 27 12:36:45 [5492] DBG:core:parse_headers: this is the first via Mar 27 12:36:45 [5492] DBG:core:receive_msg: After parse_msg... Mar 27 12:36:45 [5492] DBG:core:receive_msg: preparing to run routing scripts... Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=8 Mar 27 12:36:45 [5492] DBG:core:parse_to_param: tag=as06cb485b Mar 27 12:36:45 [5492] DBG:core:parse_to: end of header reached, state=29 Mar 27 12:36:45 [5492] DBG:core:parse_to: display={}, ruri={sip:1002@172.16.16.218:5091} Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: <To> [46]; uri=[sip:1002@172.16.16.218:5091] Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: to body [<sip:1002@172.16.16.218:5091>] Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=100 Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: cseq <CSeq>: <2> <ACK> Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: content_length=0 Mar 27 12:36:45 [5492] DBG:core:get_hdr_field: found end of header Mar 27 12:36:45 [5492] DBG:maxfwd:is_maxfwd_present: max_forwards header not found! Mar 27 12:36:45 [5492] DBG:siputils:has_totag: totag found Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=200 Mar 27 12:36:45 [5492] DBG:rr:find_first_route: No Route headers found Mar 27 12:36:45 [5492] DBG:rr:loose_route: There is no Route HF Mar 27 12:36:45 [5492] DBG:core:parse_headers: flags=78 Mar 27 12:36:45 [5492] DBG:tm:t_lookup_request: start searching: hash=44317, isACK=1 Mar 27 12:36:45 [5492] DBG:tm:matching_3261: RFC3261 transaction matched, tid=-d8754z-863b295f961d253f-1---d8754z- Mar 27 12:36:45 [5492] DBG:tm:t_lookup_request: REF_UNSAFE: after is 1 Mar 27 12:36:45 [5492] DBG:tm:t_lookup_request: transaction found (T=0x7fd335eee6b0) Mar 27 12:36:45 [5492] DBG:tm:cleanup_uac_timers: RETR/FR timers reset Mar 27 12:36:45 [5492] DBG:tm:insert_timer_unsafe: [2]: 0x7fd335eee730 (58) Mar 27 12:36:45 [5492] DBG:tm:t_unref: UNREF_UNSAFE: after is 0 Mar 27 12:36:45 [5492] DBG:core:destroy_avp_list: destroying list (nil) Mar 27 12:36:45 [5492] DBG:core:receive_msg: cleaning up Mar 27 12:36:45 [5492] DBG:core:tls_update_fd: New fd is 18 Mar 27 12:36:45 [5492] DBG:core:_tls_read: 4 bytes read Mar 27 12:36:45 [5492] DBG:core:tcp_read_req: content-length= 0 Mar 27 12:36:45 [5492] DBG:core:tcp_send: tcp connection found (0x7fd335eddc18), acquiring fd Mar 27 12:36:45 [5492] DBG:core:tcp_send: c= 0x7fd335eddc18, n=16 Mar 27 12:36:45 [5499] DBG:core:handle_ser_child: read response= 7fd335eddc18, 1, fd -1 from 7 (5492) Mar 27 12:36:45 [5492] DBG:core:tcp_send: after receive_fd: c= 0x7fd335eddc18 n=8 fd=19 Mar 27 12:36:45 [5492] DBG:core:tcp_send: sending... Mar 27 12:36:45 [5492] DBG:core:tls_update_fd: New fd is 19 Mar 27 12:36:45 [5492] DBG:core:tls_write: write was successful (2 bytes) Mar 27 12:36:45 [5492] DBG:core:tcp_send: after write: c= 0x7fd335eddc18 n=2 fd=19 Mar 27 12:36:45 [5492] DBG:core:tcp_send: buf= one more thing, i have got two clients from one PC, still look at netstat result hemanshu@localhost user]$ netstat -antp | grep kamailio (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 172.16.16.218:5091 0.0.0.0:* LISTEN 4947/kamailio tcp 0 0 172.16.16.218:5092 0.0.0.0:* LISTEN 4947/kamailio tcp 0 0 172.16.16.218:5091 172.16.17.85:1295 ESTABLISHED 4964/kamailio tcp 0 0 172.16.16.218:5091 172.16.17.85:1296 ESTABLISHED 4964/kamailio tcp 0 0 172.16.16.218:5091 172.16.17.85:1289 ESTABLISHED 4964/kamailio tcp 0 0 172.16.16.218:5091 172.16.17.85:1293 ESTABLISHED 4964/kamailio tcp 0 0 172.16.16.218:5091 172.16.17.85:1291 ESTABLISHED 4964/kamailio tcp 0 0 172.16.16.218:5091 172.16.17.85:1286 ESTABLISHED 4964/kamailio tcp 0 0 172.16.16.218:5091 172.16.17.85:1285 ESTABLISHED 4964/kamailio Both clients keep creating new connection, and not reusing the already connected connection. i this this si the problem ---- Regards, Hemanshu Patel Sr. Software Engg Mo:09601295238 On Sat 27/03/10 11:37 AM , Hemanshu Patel <hemanshu.patel(a)saicare.com> wrote: > With TLS it still is not working > Mar 27 11:39:16 [4421] INFO:core:probe_max_receive_buffer: using a > UDP receive buffer of 255 kb > Mar 27 11:39:16 [4425] WARNING:usrloc:dbrow2info: non-local socket > ...ignoring > Mar 27 11:39:18 [4431] INFO:core:tls_accept: client did not present > a certificate > Mar 27 11:39:55 [4432] INFO:core:tls_accept: client did not present > a certificate > Mar 27 11:40:01 [4431] ERROR:rr:w_record_route: Double attempt to > record-route > Mar 27 11:40:01 [4426] ERROR:core:tls_connect: SSL_ERROR_SYSCALL > err=Connection reset by peer(104) > Mar 27 11:40:01 [4426] ERROR:core:tls_connect: something wrong in > SSL: 5 (ret=-1) err=Connection reset by peer(104) > Mar 27 11:40:01 [4426] ERROR:core:tcp_send: failed to send > Mar 27 11:40:01 [4426] ERROR:core:msg_send: tcp_send failed > Mar 27 11:40:01 [4425] WARNING:core:run_actions: null action list > (rec_level=1) > my doubt is that if somethings wrong with SSL certificates that i > created myself (i.e my own root CA, and self signed certificates), > then how come registration is working like charm? > if there is some problem with Certificates then registration should > also not work. > am i right? > ---- > Regards, > Hemanshu Patel > Sr. Software Engg > SIS,Ahmedabad > Mo:09601295238 > On Sat 27/03/10 9:50 AM , "Hemanshu Patel" wrote: > > I havent tested over TCP, let me check it > > but hardphone, i mean hardware based phones from grandstream > gvx3140 > > works > > fine with same implementation on TLS. > > -- > > Regards, > > Hemanshu Patel > > M: 09601295238 > > > Does eyebeam with SIP over TCP is working? > > > > > > Am 26.03.2010 13:43, schrieb Hemanshu Patel: > > >> > > >> i am still having this problem. > > >> when i use two grandstream phone everything works fine, > > >> i can make calls on TLS and users can talk to each other. > > >> > > >> But when i use two eyebream phone, it doesnt work, gives > > following error > > >> > > >> :33 [2875] WARNING:core:init_ssl_ctx_behavior: server > > verification NOT > > >> activated. Weaker security. > > >> [ panreg-tls]$ > > >> [ panreg-tls]$ > > >> [ panreg-tls]$ Mar 26 18:11:59 [2889] > > >> ERROR:rr:w_record_route: Double attempt to record-route > > >> Mar 26 18:12:09 [2884] ERROR:core:tcp_blocking_connect: timeout > > 10 s > > >> elapsed from 10 s > > >> Mar 26 18:12:09 [2884] ERROR:core:tcpconn_connect: > > tcp_blocking_connect > > >> failed > > >> Mar 26 18:12:09 [2884] ERROR:core:tcp_send: connect failed > > >> Mar 26 18:12:09 [2884] ERROR:core:msg_send: tcp_send failed > > >> Mar 26 18:12:10 [2883] ERROR:core:tcp_blocking_connect: timeout > > 10 s > > >> elapsed from 10 s > > >> Mar 26 18:12:10 [2883] ERROR:core:tcpconn_connect: > > tcp_blocking_connect > > >> failed > > >> Mar 26 18:12:10 [2883] ERROR:core:tcp_send: connect failed > > >> Mar 26 18:12:10 [2883] ERROR:core:msg_send: tcp_send failed > > >> Mar 26 18:12:10 [2883] WARNING:core:run_actions: null action > list > > >> (rec_level=1) > > >> Mar 26 18:12:11 [2881] ERROR:core:tcp_blocking_connect: timeout > > 10 s > > >> elapsed from 10 s > > >> Mar 26 18:12:11 [2881] ERROR:core:tcpconn_connect: > > tcp_blocking_connect > > >> failed > > >> Mar 26 18:12:11 [2881] ERROR:core:tcp_send: connect failed > > >> Mar 26 18:12:11 [2881] ERROR:core:msg_send: tcp_send failed > > >> Mar 26 18:12:13 [2882] ERROR:core:tcp_blocking_connect: timeout > > 10 s > > >> elapsed from 10 s > > >> Mar 26 18:12:13 [2882] ERROR:core:tcpconn_connect: > > tcp_blocking_connect > > >> failed > > >> Mar 26 18:12:13 [2882] ERROR:core:tcp_send: connect failed > > >> Mar 26 18:12:13 [2882] ERROR:core:msg_send: tcp_send failed > > >> Mar 26 18:12:19 [2884] ERROR:core:tcp_blocking_connect: timeout > > 10 s > > >> elapsed from 10 s > > >> Mar 26 18:12:19 [2884] ERROR:core:tcpconn_connect: > > tcp_blocking_connect > > >> failed > > >> Mar 26 18:12:19 [2884] ERROR:core:tcp_send: connect failed > > >> Mar 26 18:12:19 [2884] ERROR:core:msg_send: tcp_send failed > > >> > > >> > > >> > > >> Any idea? Same configuration works with grandstream, while they > > cant in > > >> softphone? and gives 477 errot code. > > >> > > >> my asterisk log is as below: > > >> > > >> 26 18:08:09] WARNING[2833]: chan_sip.c:1648 setup_crypto: > > Hemanshu: > > >> local_key641 jhbAJ7jFE1p/Ngn4kVxy7qTTmkJpeBiN6W98+gmM len 40 > > >> -- Called kamailio/1003 > > >> -- Got SIP response 477 "Send failed (477/SL)" back from > > >> 172.16.16.218 > > >> -- No one is available to answer at this time (1:0/0/0) > > >> -- Executing [_default:4] Hangup("SIP/5091-8c001430", "") > > >> in > > >> new stack > > >> == Spawn extension (hemu_default, 1003, 4) exited non-zero > on > > >> 'SIP/5091-8c001430' > > >> > ::Disconnected form Oracle, trying to connect > again.. > > >> > ::Tried a lot, not getting connected.. > > >> -- Got SIP response 477 "Send failed (477/SL)" back from > > >> 172.16.16.218 > > >> > > >> > > >> Any idea what could be the problem? > > >> > > > > > _______________________________________________ > > Kamailio (OpenSER) - Users mailing list > > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > > http://lists.openser-project.org/cgi-bin/mailman/listinfo/users > > > > > ---- SIS Blade Server, Desktop & Thin Client is now available on DGS > & D rate contract. For more detail kindly visit our website > http://www.saicare.com > > ---- SIS Blade Server, Desktop & Thin Client is now available on DGS & D rate contract. For more detail kindly visit our website http://www.saicare.com

2 1

INVITE timers
by Alex Hermann 27 Mar '10

27 Mar '10

Hello, I'm trying to create a scenarion which was very simple with Kamailio 1.x, but seems impossible with sr3.0. I need to do failover for INVITE's and also limit the call setup time per-branch, so I defined the problem in 2 parts that need to work separately, but also combined into 1 proxy. 1) Fast failover. After t_relay, the destination should be tried for max 2 sec per host. No maximum for the whole set. Thus, if a destination has 4 SRV records, and each host fails after 2 secs, a 408 will be sent back after a total of 8 secs. If a (proivisional) response arrives within 2 sec, a 408 MUST NOT be sent. The exact value of the timer should be configurable per t_relay call. In kamailio this is accomplished by setting the fr_timer(_avp) to 2000ms. In sr3.0 I have yet to find a combination of timer settings that work. 2) Call setup duration. If a destination host returns a response, I want to limit the attempt to 80 secs (default, should be configurable per t_relay call) of ringing/progress/whatever. After that a failure route will take care to route to a different destination, at this time this timer should be restarted. At no other time after the _first_ provisional reponse after the t_relay call should the timer be restarted. In Kamailio this was accomplished by just setting fr_inv_timer(_avp) to the desired value before t_relay(). In sr3.0 this timer will be restarted after additional provisional responses and will not be resetted after a new t_relay call (from failure_route). Any suggestions on how to get the desired behaviours are welcomed (at the moment scenario 1 is more important than 2). -- Greetings, Alex Hermann

3 6

Re: [Kamailio-Users] Problem with secure TLS call
by Hemanshu Patel 27 Mar '10

27 Mar '10

Yups, it works fine with TCP. All packets are forwarded to other party perfectly and everything work smooth. only with TLS, on softphone it doesnt work. any more suggestions ---- Regards, Hemanshu Patel Sr. Software Engg SIS,Ahmedabad Mo:09601295238 On Sat 27/03/10 9:50 AM , "Hemanshu Patel" <hemanshu.patel(a)saicare.com> wrote: > I havent tested over TCP, let me check it > but hardphone, i mean hardware based phones from grandstream gvx3140 > works > fine with same implementation on TLS. > -- > Regards, > Hemanshu Patel > M: 09601295238 > > Does eyebeam with SIP over TCP is working? > > > > Am 26.03.2010 13:43, schrieb Hemanshu Patel: > >> > >> i am still having this problem. > >> when i use two grandstream phone everything works fine, > >> i can make calls on TLS and users can talk to each other. > >> > >> But when i use two eyebream phone, it doesnt work, gives > following error > >> > >> :33 [2875] WARNING:core:init_ssl_ctx_behavior: server > verification NOT > >> activated. Weaker security. > >> [ panreg-tls]$ > >> [ panreg-tls]$ > >> [ panreg-tls]$ Mar 26 18:11:59 [2889] > >> ERROR:rr:w_record_route: Double attempt to record-route > >> Mar 26 18:12:09 [2884] ERROR:core:tcp_blocking_connect: timeout > 10 s > >> elapsed from 10 s > >> Mar 26 18:12:09 [2884] ERROR:core:tcpconn_connect: > tcp_blocking_connect > >> failed > >> Mar 26 18:12:09 [2884] ERROR:core:tcp_send: connect failed > >> Mar 26 18:12:09 [2884] ERROR:core:msg_send: tcp_send failed > >> Mar 26 18:12:10 [2883] ERROR:core:tcp_blocking_connect: timeout > 10 s > >> elapsed from 10 s > >> Mar 26 18:12:10 [2883] ERROR:core:tcpconn_connect: > tcp_blocking_connect > >> failed > >> Mar 26 18:12:10 [2883] ERROR:core:tcp_send: connect failed > >> Mar 26 18:12:10 [2883] ERROR:core:msg_send: tcp_send failed > >> Mar 26 18:12:10 [2883] WARNING:core:run_actions: null action list > >> (rec_level=1) > >> Mar 26 18:12:11 [2881] ERROR:core:tcp_blocking_connect: timeout > 10 s > >> elapsed from 10 s > >> Mar 26 18:12:11 [2881] ERROR:core:tcpconn_connect: > tcp_blocking_connect > >> failed > >> Mar 26 18:12:11 [2881] ERROR:core:tcp_send: connect failed > >> Mar 26 18:12:11 [2881] ERROR:core:msg_send: tcp_send failed > >> Mar 26 18:12:13 [2882] ERROR:core:tcp_blocking_connect: timeout > 10 s > >> elapsed from 10 s > >> Mar 26 18:12:13 [2882] ERROR:core:tcpconn_connect: > tcp_blocking_connect > >> failed > >> Mar 26 18:12:13 [2882] ERROR:core:tcp_send: connect failed > >> Mar 26 18:12:13 [2882] ERROR:core:msg_send: tcp_send failed > >> Mar 26 18:12:19 [2884] ERROR:core:tcp_blocking_connect: timeout > 10 s > >> elapsed from 10 s > >> Mar 26 18:12:19 [2884] ERROR:core:tcpconn_connect: > tcp_blocking_connect > >> failed > >> Mar 26 18:12:19 [2884] ERROR:core:tcp_send: connect failed > >> Mar 26 18:12:19 [2884] ERROR:core:msg_send: tcp_send failed > >> > >> > >> > >> Any idea? Same configuration works with grandstream, while they > cant in > >> softphone? and gives 477 errot code. > >> > >> my asterisk log is as below: > >> > >> 26 18:08:09] WARNING[2833]: chan_sip.c:1648 setup_crypto: > Hemanshu: > >> local_key641 jhbAJ7jFE1p/Ngn4kVxy7qTTmkJpeBiN6W98+gmM len 40 > >> -- Called kamailio/1003 > >> -- Got SIP response 477 "Send failed (477/SL)" back from > >> 172.16.16.218 > >> -- No one is available to answer at this time (1:0/0/0) > >> -- Executing [_default:4] Hangup("SIP/5091-8c001430", "") > >> in > >> new stack > >> == Spawn extension (hemu_default, 1003, 4) exited non-zero on > >> 'SIP/5091-8c001430' > >> > ::Disconnected form Oracle, trying to connect again.. > >> > ::Tried a lot, not getting connected.. > >> -- Got SIP response 477 "Send failed (477/SL)" back from > >> 172.16.16.218 > >> > >> > >> Any idea what could be the problem? > >> > > > _______________________________________________ > Kamailio (OpenSER) - Users mailing list > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > http://lists.openser-project.org/cgi-bin/mailman/listinfo/users > > ---- SIS Blade Server, Desktop & Thin Client is now available on DGS & D rate contract. For more detail kindly visit our website http://www.saicare.com

1 0

[Kamailio-Users] Problem with secure TLS call
by Detlef Pilzecker 27 Mar '10

27 Mar '10

Hi, I am using kamailio 3.0.1 (x86_64/linux) 0822a9 flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. and I am using the client "PhonerLite" (http://www.phonerlite.de). The phone is registered on my server with TLS. If I call someone or myself I get an error message. What is wrong with my server? (TLS calls with PhonerLite with the provider antisip.com are possible without problems!) With UDP calling myself I get "486:Busy Here" on the phone, this is OK and normal. With TLS I get "477:Unfortunately error on sending to next hop occurred(477/SL)" on the phone and some ERROR messages like the following on the kamailio.log (you can see the rest of the log in the attached zip): Mar 21 20:24:00 vs208140 /usr/local/sbin/kamailio[20013]: DEBUG: <core> [msg_translator.c:200]: check_via_address(95.90.205.74, 95.90.205.74, 0) Mar 21 20:24:00 vs208140 /usr/local/sbin/kamailio[20013]: DEBUG: <core> [tcp_main.c:1786]: tcp_send: no open tcp connection found, opening new one Mar 21 20:24:10 vs208140 /usr/local/sbin/kamailio[20013]: ERROR: <core> [tcp_main.c:618]: connect 95.90.205.74:5061 failed (timeout) Mar 21 20:24:10 vs208140 /usr/local/sbin/kamailio[20013]: ERROR: <core> [tcp_main.c:621]: ERROR: tcp_blocking_connect 95.90.205.74:5061: timeout 10 s elapsed from 10 s Mar 21 20:24:10 vs208140 /usr/local/sbin/kamailio[20013]: ERROR: <core> [tcp_main.c:1168]: ERROR: tcp_do_connect: tcp_blocking_connect 95.90.205.74:5061 failed Mar 21 20:24:10 vs208140 /usr/local/sbin/kamailio[20013]: ERROR: <core> [tcp_main.c:1237]: ERROR: tcp_do_connect 95.90.205.74:5061: failed (115) Operation now in progress Mar 21 20:24:10 vs208140 /usr/local/sbin/kamailio[20013]: ERROR: <core> [tcp_main.c:1955]: ERROR: tcp_send 95.90.205.74:5061: connect failed Mar 21 20:24:10 vs208140 /usr/local/sbin/kamailio[20013]: ERROR: tm [../../forward.h:191]: msg_send: ERROR: tcp_send failed The kamailio.cfg file is also in the zip attached. The PC is connected with the router (I opened the TCP ports 5060-5062) that is connected to the Internet. The problem also happens if I disable the firewall of the server and of the PC. Can someone give me help? Thanks in advance! Regards Detlef Pilzecker

3 8

topoh
by dotnetdub 26 Mar '10

26 Mar '10

Hi List, We are using Kamailo 3.01 and testing topoh for starters: Kamailio3 = IP of Kamailio Server and Asterisk=IP of Asterisk server Observations: U 2010/03/26 12:05:56.665583 Kamailio3:5060 -> Asterisk:5060 SIP/2.0 100 trying -- your call is important to us^@ Via: SIP/2.0/UDP Kamailio3:5060;branch=z9hG4bK08fffea4;rport=5060^@ From: "xxxxxxxxx" <sip:xxxxx@asterisk>;tag=as7ac63338^@ To: <sip:Xxxxxxx@Kamailio3>^@ Call-ID: 2f7a1c040f4920d5591695956ec8c42c@Kamailio3^@ CSeq: 103 INVITE^@ Server: kamailio (3.0.1 (i386/linux))^@ Content-Length: 0^@ Warning: 392 Kamailio:5060 "Noisy feedback tells: pid=23782 req_src_ip=Asterisk req_src_port=5060 in_uri=sip:xxxxxx@Kamailioout_uri=sip:Translated@ *UPSTREAMPROVIDERSIP* Provider via_cnt==1"^@ The noisy feedback contains everything that is hidden by topoh in the contact: Contact: <sip:10.1.1.10;line=sr-N6IAzBVAWxFAzx3lzxclMxylPxcsOBVlWGZ6WJZfWlq-W.y6My**>^ Also: U 2010/03/26 12:06:00.125828 Kamailio3:5060 -> Asterisk:5060 SIP/2.0 180 Ringing^@ From: "xxxxxxx"<sip:xxxxxxxx@Kamailio3>;tag=as7ac63338^@ To: <sip:xxxxxx@Kamailio3 >;tag=fccd978-b342ea59-13c4-50022-82e974-27d2fa70-82e974^@ Call-ID: 2f7a1c040f4920d5591695956ec8c42c@Kamailio3^@ CSeq: 103 INVITE^@ Via: SIP/2.0/UDP Asterisk:5060;branch=z9hG4bK08fffea4;rport=5060^@ Record-Route: <sip:10.1.1.10;line=sr-N6IAzBclOBF4WLZfWBF7M.VLz6fLHRQ7z6srpxusg9MXgSIqHReEgJZwgSKEgSjLMc**>^@ Record-Route: <sip:Kamailio3;lr=on;did=bff.60851b12>^@ Allow: INVITE, CANCEL, ACK, BYE, OPTIONS, INFO, REFER, NOTIFY^@ Contact: <sip:10.1.1.10;line=sr-N6IAzBVAWxFAzx3lzxclMxylPxcsOBVlWGZ6WJZfWlq-W.y6My**>^@ Content-Type: application/sdp^@ Content-Length: 228^@ ^@ v=0^@ *o=Upstream Switch Name 160624700 160624700 IN IP4 Upstream Providers IP^@* *s=Upstream Switch Name^@* * * The upstream info appears here also. I am using engage_media_proxy and using topoh with defaul parameters. Am I missing something ? Thanks, Stephen.

3 6

[Kamailio-Users] Recording RTP session
by Hector.Ortiz＠swisscom.com 26 Mar '10

26 Mar '10

Hi everybody I've configured a SIP server (OpenSER 1.3.2) to work with rtpproxy and so far everything is fine, but now I want to be able to record the audio from a conversation. I've read that this is possible by using the function start_recording from the module NATHelper but I'm not able to get it working RTPproxy 1.2.1 is running with the following options: root@openser:/opt/rtpproxy-1.2.1/bin# ps uax | grep rtpproxy rtpproxy 30827 0.0 0.0 26968 964 ? Ssl 14:49 0:00 /opt/rtpproxy-1.2.1/bin/rtpproxy -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -l 192.168.34.1 -s udp:127.0.0.1 7890 -r /etc/openser/stored_conversations -S /tmp -a -d DBUG -P root 31547 0.0 0.0 7524 892 pts/1 R+ 15:59 0:00 grep rtpproxy Output from netstat root@openser:/opt/rtpproxy-1.2.1/bin# netstat -tupna | grep rtpproxy udp 0 0 127.0.0.1:7890 0.0.0.0:* 30827/rtpproxy Relevant parts of the configuration file ... # ------ nathelper params ----- modparam("nathelper", "natping_interval", 30) modparam("nathelper", "ping_nated_only", 1) modparam("nathelper", "sipping_bflag", 7) modparam("nathelper", "sipping_from", "sip:pinger@openser.org") modparam("nathelper", "rtpproxy_sock", "udp:127.0.0.1:7890") modparam("nathelper", "force_socket", "udp:localhost:7890") ... route[6] { xlog("L_INFO", "ROUTE 6"); # NAT handling # Set reply routing block, to which control is passed after a transaction # completed with a negative result but before sending a final reply t_on_failure("1"); # Check if we're NATed if (isflagset(5) || isbflagset(6)) { # Use rtpproxy force_rtp_proxy(); if ( start_recording() ) { xlog("L_INFO", "RECORDING..."); }; } # Set reply routing block, to which control is passed each time a reply # (provisional or final) for the transaction is received t_on_reply("1"); } ... onreply_route[1] { xlog("L_INFO", "ONREPLY_ROUTE"); if ((isflagset(5) || isbflagset(6)) && status=~"(180)|(183)|(2[0-9][0-9])") { xlog("L_INFO", "NAT'd TRANSACTION"); fix_nated_contact(); force_rtp_proxy(); if ( start_recording() ) { xlog("L_INFO", "RECORDING..."); }; } else if (nat_uac_test("1")) { fix_nated_contact(); } exit; } When I start OpenSER I see the following in syslog Mar 19 16:08:45 openser /usr/sbin/openser[31630]: NOTICE:core:main: version: openser 1.3.2-notls (x86_64/linux) Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:core:main: using 256 Mb shared memory Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:core:main: using 1 Mb private memory per process Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:sl:mod_init: Initializing StateLess engine Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:tm:mod_init: TM - initializing... Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:maxfwd:mod_init: initializing... Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:usrloc:ul_init_locks: locks array size 512 Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:registrar:mod_init: initializing... Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:textops:mod_init: initializing... Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:xlog:mod_init: initializing... Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:avpops:avpops_init: initializing... Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:acc:mod_init: initializing... Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:dialog:mod_init: Dialog module - initializing Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255 kb Mar 19 16:08:45 openser /usr/sbin/openser[31630]: INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255 kb Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31632_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31632_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31632_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31632_1 1 " Mar 19 16:08:45 openser /usr/sbin/openser[31632]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31631_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31631_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31633_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31633_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31634_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31634_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31635_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31635_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31636_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31636_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31637_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31637_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31638_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31638_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31637_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31637_1 1 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31631_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31631_1 1 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31634_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31634_1 1 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31636_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31636_1 1 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31633_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31633_1 1 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31635_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31635_1 1 " Mar 19 16:08:45 openser /usr/sbin/openser[31631]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser /usr/sbin/openser[31634]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser /usr/sbin/openser[31637]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser /usr/sbin/openser[31633]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser /usr/sbin/openser[31636]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser /usr/sbin/openser[31635]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser /usr/sbin/openser[31638]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31639_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31639_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31638_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31638_1 1 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31640_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31640_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31642_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31642_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31643_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31643_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31644_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31644_0 20040107 " Mar 19 16:08:45 openser /usr/sbin/openser[31642]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser /usr/sbin/openser[31643]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31645_0 V" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31645_0 20040107 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31639_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31639_1 1 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31642_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31642_1 1 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31644_1 VF 20050322" Mar 19 16:08:45 openser /usr/sbin/openser[31644]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31644_1 1 " Mar 19 16:08:45 openser /usr/sbin/openser[31640]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser /usr/sbin/openser[31639]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31640_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31640_1 1 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31643_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31643_1 1 " Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:handle_command: received command "31645_1 VF 20050322" Mar 19 16:08:45 openser rtpproxy[30827]: DBUG:doreply: sending reply "31645_1 1 " Mar 19 16:08:45 openser /usr/sbin/openser[31645]: INFO:nathelper:rtpp_test: rtp proxy <udp:127.0.0.1:7890> found, support for it enabled But when I place the call no debug info from rtpproxy is being generated nor the RTP session is being saved to file. Any idea what the problem can be? Thanks in advance Héctor

3 18

[Kamailio-Users] Kamailio as proxy and Asterisk as registrar
by Vic Jolin 26 Mar '10

26 Mar '10

Hi all! Kamailio newbie here. Well my setup is like this Kamailio as load balancer and proxy -> Multiple clustered asterisk as registrars What I wanted to do was have all clients registered to asterisk so that most of the pbx stuff will be done thru it and I'm using Asterisk Realtime as well and doing A2billing at the same time so I was thinking if my setup will actually work. I have already configured kamailio to do load balancing and send to my asterisk servers and my xlite is able to register to my asterisk server, the problem I have right now is when I try to call, the call gets dropped. I believe it's something about asterisk not being able to send the correct INVITE or not being able to receive the ACK or something to that effect. Please help me, as I've said I'm just a newbie with kamailio. TIA!

1 0

[Kamailio-Users] Fwd: Kamailio as a proxy between Trunk and PBX.
by Espen Berg 26 Mar '10

26 Mar '10

We are planning a new voip system. The trunk is provided to us on a private 10.x.x.x/29 range, and therefore not available direct to our end customers. We plan to have some kind of SIP/RTP proxy in front of the trunk, and a PBX in front of this. The trunk doesn't have any authentication, the end customers should connect and authenticate to the PBX in front, and the RTP streams should terminate to the proxy. Is this possible to achieve by using Kamailio and RTPProxy? Trunk | | 10.x.x.x/29 | SIP Proxy | PBX Asterisk etc. | Customer I have tried many different configurations and browsed every bundled example and web, but still I am not able to do what I want. This have already given me some grey hears, so I guess it's time to check if this is even possible. If not, is there any other approach that is more recommendable? If someone has done this before I would appreciate some example configuration that I could work with. Regards Espen, Norway

2 2

[Serusers] change in mailing list management
by Pavel Kasparek 26 Mar '10

26 Mar '10

Hello all, since now it is possible to use only web interface to manage mailing lists hosted on lists.iptel.org server. We had to disable the email commands interface as part of fight against spam (it was causing too many messages being sent from us, recognized by some blacklists as spam). This means that for all actions like subscribing, un-subscribing, changing your preferences etc. you have to use the web interface. You can find a link to it at end of every message sent to the mailing list. Sorry if it causes any inconvenience to you. Pavel Kasparek

1 0

[Kamailio-Users] Kamailio 3.0.1
by dotnetdub 26 Mar '10

26 Mar '10

Hi List, I have Kamailio 3.0.1 running from GIT with my old 1.5.3 config file. Everything seems fine except the RPID. I'm not getting any RPID sent in the SIP message and if I put debug=3 I see: DEBUG: auth [rpid.c:177]: no rpid AVP My config: # auth modparam("auth", "rpid_avp", "$avp(s:rpid)") modparam("auth", "rpid_prefix", "<sip:") modparam("auth", "rpid_suffix","@asterisk.ie ;party=calling;id-type=subscriber;privacy=off;screen=yes>") # auth_db modparam("auth_db", "db_url", "mysql://openser:XSXXXX@localhost/openser") modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") modparam("auth_db", "load_credentials", "$avp(s:rpid)=rpid") in my route: append_rpid_hf(); Probably missing something very simple. Any help would be appreciated. Thanks, Stephen.

2 13

route() call with pv argument
by jh＠tutpro.com 25 Mar '10

25 Mar '10

i just made a test and noticed that route() accepts a pv argument. at least i didn't get anhy syntax error from route("$var(test)"); this is good if it works. Core functions section of http://sip-router.org/wiki/cookbooks/core-cookbook/devel#route does not list route() function call at all. -- juha

2 6

[Kamailio-Users] fr_inv_timer not honored (fr_inv_timer/2 is used in fact)
by Iñaki Baz Castillo 25 Mar '10

25 Mar '10

Hi, I set fr_inv_timer=150 and use lcr module to balance (and failover) between two gateways. In the failure route I set (simplified): failure_route[FAILURE_ROUTE_OUT] { if (t_local_replied("last")) { next_gw(); t_relay(); } } This means that if a INVITE routed to gateway-1 replies a provisional response but no final response within 150 seconds, then Kamailio should generate a local 408 and failure route would relaty to gateway-2. But what I see is that such "timeout" time is 75 seconds (the half of 150 !). I remember a similar "issue" when handling with SRV DNS domains returning more than one destinations, but in my case I just use single IP's in lcr module. But the fact is that I use exactly 2 gateways in lcr (150/2 = 75). But anyhow it doesn't make sense. Do I miss something? Thanks. PD: Important, could occur the same with fr_timer? -- Iñaki Baz Castillo <ibc(a)aliax.net>

2 11

route is not called and no error is produced
by jh＠tutpro.com 25 Mar '10

25 Mar '10

i tested if route() with pv arg would work. i created a route block: route [test] { xlog("here we are\n"); return; } and then as the very first thing in the main route block i have: $var(test) = "test"; route("$var(test)"); then i send the proxy a sip request and don't get anything related to this to syslog, i.e., no "here we are" line nor any error message. this looks like i bug to me, since if route() accepts a pv, i should see "here we are" syslog entry or if it doesn't, i should see some kind of error message. comments? -- juha

1 0

[Kamailio-Users] Establish Call but no audio transferred on different network
by RAJNIKANT VANZA 25 Mar '10

25 Mar '10

Hello all, I am using kamailio-1.5.0 + mediaproxy. it works properly when connection is in between two clients between same lan. But when I connecting between two client who are on differet proxy and behind different NAT, call has been established but no audio get transferred. What are the changed i suppose to do, or any parameters should get enabled while compilation, Thanks in advance. -- Best Regards, Rajnikant Vanza

2 1

[Kamailio-Users] Radius
by dotnetdub 25 Mar '10

25 Mar '10

Hi, I'm using Kamailio - posted this to the opensips list as I thought I may get support from the ag guys but nothing.. Has anyone else experienced this or have an idea as to what it may be? Having a very small but annoying issue with Radius Accounting. Everything is getting written fine except for 'Source-Port' This appears in radius.log everytime a record is written/updated. - Error: rlm_radutmp: NAS OpenSER port 5060 unknown packet type 15 It's writing this into the text files and value to the radacct table: Source-Port = "\304\023" All other information is being written correctly. CDRTool version: 7.0 Freeradius version: 1.1.7-4 mediaproxy version: 2.3.10 Kamailio Version: 1.5.3 Using the dictionary files that ship with CDRTool >From accounting: modparam("acc", "db_url", "mysql://openser:XXXXXXXXXXXX@localhost/openser") modparam("acc", "db_flag", 2) modparam("acc", "log_flag", 2) modparam("acc", "db_missed_flag", 3) modparam("acc", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") modparam("acc", "radius_flag", 2) modparam("acc", "radius_missed_flag", 3) modparam("acc", "radius_extra", "User-Name=$Au; \ Calling-Station-Id=$from; \ Called-Station-Id=$to; \ Sip-Translated-Request-URI=$avp(s:translated_uri); \ Sip-RPid=$avp(s:rpid); \ Source-IP=$si; \ Source-Port=$sp; \ Canonical-URI=$avp(s:can_uri); \ Billing-Party=$avp(s:billing_party); \ Divert-Reason=$avp(s:divert_reason); \ X-RTP-Stat=$hdr(X-RTP-Stat); \ Contact=$hdr(contact); \ Event=$hdr(event); \ SIP-Proxy-IP=$avp(s:sip_proxy_ip); \ ENUM-TLD=$avp(s:enum_tld)") Obviously it's not a show stopper but it's just bugging the hell out of me :) If any more info is required please let me know and I will provide ASAP. TIA, Stephen

2 2

[Kamailio-Users] Kamdbctl not installing and Install error
by Nathaniel L Keeling 24 Mar '10

24 Mar '10

I have installed Kamailio 3.0 but without db support. When I tried to add support for postgres, the install errors and the kamdbctl does not install in order to create the database tables. I am installing on Solaris 10 and have included the error from the install: Makefile.defs defs skipped gmake[1]: Entering directory `/usr/local/src/kamailio-3.0.0/modules_k/xlog' touch /usr/local/kamailio-3.0.0/lib/kamailio/modules_k/xlog.so ginstall -m 755 xlog.so /usr/local/kamailio-3.0.0/lib/kamailio/modules_k gmake[1]: Leaving directory `/usr/local/src/kamailio-3.0.0/modules_k/xlog' # other configs /bin/sh: syntax error at line 1: `;' unexpected gmake: *** [install-cfg] Error 2 Thanks Nathaniel

4 7

why is while loop not terminated?
by jh＠tutpro.com 24 Mar '10

24 Mar '10

i'm in the process of enhancing enum mudule enum_query, so that suffic param can be given in a pseudo variable. before committing to git, i tested if the new version is working correctly, and for that purpose wrote this kind of route: route [PERFORM_ENUM_QUERIES] { xlog("L_INFO", "suffix_list = <$var(suffix_list)>\n"); $var(i) = 0; $var(domain) = $(var(domain_list){s.select,0,,}); while ($var(domain) != "") { xlog("L_INFO", "Query $var(i) for $var(domain)\n"); if (enum_query("$var(domain)")) { xlog("L_INFO", "Return success!\n"); return(1); }; $var(i) = $var(i) + 1; $var(domain) = $(var(domain_list){s.select,$var(i),,}); }; return(-1); } looks like the enhanced enum_query works as expected, but the while loop is not terminating by the return(1) statement (see below). i'm puzzled. have i done some stupid mistake that i cannot see? -- juha Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: suffix_list = <e164.test.fi.> Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: enum [enum.c:724]: Got suffix <e164.test.fi.> Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Return success! Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: ERROR: <core> [action.c:1144]: ERROR: runaway while (1342, 25): more then 100 loops

1 1

what is $name?
by jh＠tutpro.com 24 Mar '10

24 Mar '10

i made a typo in script and wrote $domain instead of $var(domain). then i started sip router and didn't get any error messages. what does $name stand for when $name is not any of the ones listed in SIP Router Pseudo-Variables document? -- juha

2 2

Re: [Kamailio-Users] Establish Call on different network.
by john david 24 Mar '10

24 Mar '10

Dear all, started rtpproxy, enabled nat in cfg file. but still there is only connection between two client from different network, unable to get audio if used kamailio server. something more that i should add, except rtpproxy and enabling nathelper from cfg file. or else is there any way to debug where it get stuck. Thanks in advance.

2 1

[Kamailio-Users] need help on xilte
by false 24 Mar '10

24 Mar '10

Hi all i use kamailio sip proxy, its version is: [root@localhost kamailio]# /opt/sbin/kamctl fifo version Server:: kamailio (3.0.1 (i386/linux)) i use 2 xlite softphones to register to sip proxy and register successfull and use xlite make call to another xlite softphone and get 488 Not Accept Here all sip proxy, xlite softphones in the same LAN please help to fix in the sip proxy that doesnt check the SDP Thank you Ha` and the debug log: DEBUG: tm [t_reply.c:1059]: ->>>>>>>>> T_code=100, new_code=488 DEBUG: tm [t_lookup.c:1080]: DEBUG: t_check_msg: msg id=2 global id=2 T start=0xb60ae9f0 DEBUG: tm [t_lookup.c:1152]: DEBUG: t_check_msg: T already found! DEBUG: tm [t_reply.c:1549]: DEBUG: relay_reply: branch=0, save=0, relay=0 DEBUG: <core> [msg_translator.c:1876]: old size: 500, new size: 440 DEBUG: <core> [msg_translator.c:1894]: build_res_from_sip_res: copied siz ontent-Length: 0ull "SDP: Incompatible media format: no common codec."19-1--d87543-;rport=51020 "Tốt hơn, thoáng gọn hơn, nhanh hơn -Trải nghiệm Yahoo! Mail mới hôm nay! http://vn.mail.yahoo.com"

2 1

[Kamailio-Users] need help on ACC modules
by false 24 Mar '10

24 Mar '10

Hi all i use the kamailio version 3.0.1 and try to understand ACC module and found the tutorial http://www.voice-system.ro/docs/uac/ does it still work with kamailio 3.0.1, could you please present a working config with kamailio 3.0.1 How to work with the uac-create.sql, the sip account from VOIP provider username: x.x.x.x password: x.x.x.x outbound proxy: x.x.x.x domain name: sbc.net expired time : 3600s what info should i insert into database l_uuid: l_username: l_domain: r_username: r_domain: realm: auth_username: auth_password: auth_proxy: expires: when i start the sip server with acc module and got error and the config parameter: modparam("uac", "reg_db_url","mysql://openser:openserrw@localhost/openser") DEBUG: <core> [sr_module.c:617]: find_param_export: parameter <reg_db_url> not found in module <uac> ERROR: <core> [modparam.c:143]: set_mod_param_regex: parameter <reg_db_url> not found in module <uac> ERROR: <core> [modparam.c:143]: set_mod_param_regex: parameter <reg_db_url> not found in module <uac> Thank you Phần mềm chống virus và adware miễn phí đã có cùng Yahoo! Thanh Công Cụ. Tải về ngay! Tải ngay. http://vn.toolbar.yahoo.com/

2 1

[Kamailio-Users] Kamailio+asterisk
by Marcus Kvarsell 24 Mar '10

24 Mar '10

Hello everyone! If i want to have Kamailio as front-end and 3 asterisk as back-end. Sip-registration should be done by Kamailio, and usage of meet-me rooms by asterisk-servers which should be load-balanced by Kamailio. is it possible of creating outgoing call with Kamailio and when call is answered, realtime route this call dynamically based on some information coming from unixODBC source, to a meet-me room? any help appreciated!! Regards / Marcus

3 2

[Serusers] Check out my photos on Facebook
by Sarfaraz Chougule 24 Mar '10

24 Mar '10

Hi, I set up a Facebook profile where I can post my pictures, videos and events and I want to add you as a friend so you can see it. First, you need to join Facebook! Once you join, you can also create your own profile. Thanks, Sarfaraz To sign up for Facebook, follow the link below: http://www.facebook.com/p.php?i=520931674&k=54EUZ6Q3QT2BXJMFYDYVPVWZWUKJ64&r Already have an account? Add this email address to your account http://www.facebook.com/n/?merge_accounts.php&e=serusers%40iptel.org&c=71a7… was invited to join Facebook by Sarfaraz Chougule. If you do not wish to receive this type of email from Facebook in the future, please click on the link below to unsubscribe. http://www.facebook.com/o.php?k=679489&u=557896866&mid=213a1b7G2140d4a2G0G8 Facebook's offices are located at 1601 S. California Ave., Palo Alto, CA 94304.

1 0

[Kamailio-Users] Establish Call on different network.
by john david 24 Mar '10

24 Mar '10

Hello all, I am using kamailio server, it works properly when connection is in between two clients between same lan. But when I connecting between two client who are on different proxy and behind different NAT, call has been established but no audio or video get transferred. What are the changed i suppose to do, or any parameters should get enabled while compilation, Thanks in advance.

2 1

[Kamailio-Users] dinner in berlin, thursday, march 25, 19:00
by Daniel-Constantin Mierla 23 Mar '10

23 Mar '10

Hello, couple of developers from SIP and VoIP area are in Berlin this week and plan to meet for dinner and beer Thursday, March 25, 19:00 at the traditional place by now: Lemke Brauhaus Luisenplatz 1, 10585 Berlin Across the corner with Charlottenburg Castle http://www.brauhaus-lemke.com/index.php?area=4 If you are around, just pop up. You can write me if you need more details about how to get there. Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

1 0

[Kamailio-Users] Shared memory
by Bruno Machado 23 Mar '10

23 Mar '10

I have some questions regarding the shared memory. I'm working with the version 1.5.2 and its environment is quite simple. It does'nt storage any informations in the memory, like dialplan, contacts of subscribers, carrierroute, LCR and etc. The only purpose of this server is being a redirect server. Some calls have several possible destinations, reaching easily 12 contacts. The config.h's constant MAX_BRANCHES is set in 12, the default number. Ok. Like I said, almost the requests have more than 12 possible contacts. When it happens, Kamailio logs these messages: /usr/local/kamailio-1.5.2/sbin/kamailio[26188]: ERROR:core:append_branch: max nr of branches exceeded /usr/local/kamailio-1.5.2/sbin/kamailio[26188]: ERROR:pv:pv_set_branch: append_branch action failed Ok. It is not a problem. It is an error but it does not stop the system. The SIP messages still flowing normally. The server works for several days, 24/7 without functional errors, receiving five hundred thousand requests per day . But, usually at the weekends and the clock tells 2:30 am, the company's cell phone rings bringing a message: 'the system is down'. Kamailio shows: /usr/local/kamailio-1.5.2/sbin/kamailio[25492]: ERROR:core:add_avp: no more shm mem /usr/local/kamailio-1.5.2/sbin/kamailio[25492]: ERROR:exec:exec_avp: unable to add avp Kamailio stills running but it is not possible to route any request. All the new incoming calls generates the same error: 'no more shm mem'. I changed the size of shared memory, running Kamailio with '-m 64', but the server stopped again after some days. I see the options: - increase MAX_BRANCHES - increase again 'm' parameter (but it will just add more some days in the running time) - reduce the maximum number of contacts to 11 of the script that returns them to Kamailio So, my doubts are: - is it possible to have a memory leak when the message "max nr of branches exceeded" is showed? - changing '-m parameter' to a higher value, like 256, could affect the performance? tks friends bruno machado ____________________________________________________________________________________ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com

2 4

[Kamailio-Users] Media Bridge tips and hints
by Uriel Rozenbaum 23 Mar '10

23 Mar '10

Hi gentlemen, I'm having a bit of a hard time developing a bridge for media sessions. I have a box with 2 interfaces; eth0 has the private IP p.r.i.v and eth1 has public IP p.u.b.l. When I receive a message in the private IP I try sending the call to a public proxy we have (p.u.b.2) using Carrierroute module but the source IP used is p.r.i.v. It is obvious that p.u.b.2 will not be able to route back messages. # U 192.168.200.11:5060 -> p.r.i.v:5060 INVITE sip:1568767139@p.r.i.v SIP/2.0. Via: SIP/2.0/UDP 192.168.200.11:5060;branch=z9hG4bK5d94bc09. From: "60911000" <sip:60911000@p.r.i.v>;tag=as6d477d46. To: <sip:1568767139@p.r.i.v>. Contact: <sip:60911000@192.168.200.11 <sip%3A60911000(a)192.168.200.11>>. ... # U p.r.i.v:5060 -> p.u.b.2:5060 INVITE sip:1568767139@p.u.b.2 SIP/2.0. Record-Route: <sip:p.r.i.v;lr=on;ftag=as6d477d46>. Via: SIP/2.0/UDP p.r.i.v;branch=z9hG4bKf531.440788e1.0. Via: SIP/2.0/UDP 192.168.200.11:5060 ;rport=5060;received=192.168.200.11;branch=z9hG4bK5d94bc09. From: "60911000" <sip:60911000@p.r.i.v>;tag=as6d477d46. To: <sip:1568767139@p.r.i.v>. Contact: <sip:60911000@192.168.200.11 <sip%3A60911000(a)192.168.200.11>>. ... I try then to set listen=0.0.0.0 so kamailio will be binded to all IPs but then the Route headers and Via use this 0.0.0.0 # U 192.168.200.11:5060 -> p.r.i.v:5060 INVITE sip:1568767139@p.r.i.v SIP/2.0. Via: SIP/2.0/UDP 192.168.200.11:5060;branch=z9hG4bK14a00df7. From: "60911000" <sip:60911000@p.r.i.v>;tag=as502405cf. To: <sip:1568767139@p.r.i.v>. Contact: <sip:60911000@192.168.200.11 <sip%3A60911000(a)192.168.200.11>>. ... # U p.u.b.l:5060 -> p.u.b.2:5060 INVITE sip:1568767139@p.u.b.2 SIP/2.0. Record-Route: <sip:0.0.0.0;lr=on;ftag=as502405cf>. Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK711b.8d28549.0. Via: SIP/2.0/UDP 192.168.200.11:5060 ;rport=5060;received=192.168.200.11;branch=z9hG4bK14a00df7. From: "60911000" <sip:60911000@p.r.i.v>;tag=as502405cf. To: <sip:1568767139@p.r.i.v>. Contact: <sip:60911000@192.168.200.11 <sip%3A60911000(a)192.168.200.11>>. ... In this case the destination UA cannot return the call because it does not have a valid IP to do so. Is there any way to make Kamailio act in a different way? Like letting me modify the IP it will use for Via and Record-Route headers. Be aware that I'm supposed to do some kind of mirror for calls coming from outside the network (origin is public and destination is private). I'm sure I'll be asking some more on this same thread as I test. Thanks in advance! Uriel

2 3

[Kamailio-Users] VUC Podcast: The SIP Router Project
by Daniel-Constantin Mierla 22 Mar '10

22 Mar '10

Hello, the recording of the VUC session last Friday about SIP Router Project is now available online at: http://www.voipusersconference.org/2010/kamailio3/ Here you find some details about who was in the call: http://www.kamailio.org/w/2010/03/vuc-listen-the-sip-router-project-podcast/ Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

1 0

[Kamailio-Users] GSoC 2010 - Call for students
by Daniel-Constantin Mierla 22 Mar '10

22 Mar '10

Hello, if you are a student (or you know a student) interested in working with SIP Router over the summer, earning some money as well, please apply for GSoC Conferencing Presence support (or forward this email). The description of the project is done at: http://www.sip-communicator.org/index.php/GSOC2010/Kamailio4575 If you have technical details about the project please ask them on sr-dev(a)lists.sip-router.org. For GSoC related questions, please address to: gsoc(a)sip-communicator.dev.java.net. A good FAQ for applicants is available at: http://www.sip-communicator.org/index.php/GSOC2010/HowToApply Application must be done directly to the google site, link provided in the FAQ. I will be in charge of mentoring this particular project, helping you as much as possible to understand the current presence server architecture and the core API of sip router. Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

1 0

[Kamailio-Users] Centos 5 kamailio.init-file
by Detlef Pilzecker 22 Mar '10

22 Mar '10

Hi, does someone have a kamailio.init file for Centos5? The .../pkg/kamailio/[debian, fedora, ...]/kamailio.init files don't work! Thank you very much! Detlef Pilzecker

4 3

[Kamailio-Users] Quick RTPproxy question
by Uriel Rozenbaum 22 Mar '10

22 Mar '10

Hi guys, I have some easy doubt about nathelper functions using RTPProxy. I'm trying to bridge from an external IP to an internal IP. The start-line for rtpproxy is: rtpproxy -l PUBLIC_IP/PRIVATE_IP -s udp: 127.0.0.1:7999 -F It starts OK and I see it when kamailio starts. I'm going to use something like Daniel showed on some other mail: if(dst_ip==private) force_rtp_proxy("ocfaei"); else force_rtp_proxy("ocfaei"); if i have the invite from a public IP to someone in private on the request I'll run force_rtp_proxy("ocfaei"); then the reply will be from private to public... should I run "force_rtp_proxy("ocfaei");"? or should it be the same? As allways, thanks for your help. Kind regards, Uriel

3 4

[Kamailio-Users] Monitoring Upstream Carrier Health
by Geoffrey Mina 22 Mar '10

22 Mar '10

Hello, I am wondering if anyone has a clever way to remotely monitor a Kamailio 1.5 server. I am not looking for the standard monitoring, what I am looking to achieve is catching situations where my upstream carrier is having problems. We have a certain level of 404, 500, 503 errors throughout the day which are not indicative of a major carrier problem. I want to be able to monitor the ratio of properly setup calls to failed setups - so I can know when a carrier is having issues and is responding with many 503 errors. Any push in the right direction would be greatly appreciated. thanks.

4 3

[Serusers] ser auth_db registration problem
by Anand Kumar 19 Mar '10

19 Mar '10

Hi All, i m trying to register softphone on ser using modparam("auth_db", "db_url", "mysql://baaaa:dddd@xx.x.x.x/ser") modparam("auth_db", "use_domain", 0) modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "user_column", "username") modparam("auth_db", "password_column", "password") if(!www_authorize("", "subscriber")) { www_challenge("", "1"); break; } and found the following log but phone is not register . please help me... -- 2(28254) find_mod_export: found <db_update> in module mysql [/usr/local/lib/ser/modules/mysql.so] 2(28254) get_connection(): Connection found in the pool 2(28254) DEBUG: register_fifo_cmd: new command (DB) registered 0(28252) DEBUG: init_mod_child (1): dispatcher 0(28252) DISPATCHER:init_child #1 / pid <28252> 0(28252) SIP Request: 0(28252) method: <REGISTER> 0(28252) uri: <sip:123.49.54.226> 0(28252) version: <SIP/2.0> 0(28252) parse_headers: flags=1 0(28252) Found param type 232, <branch> = <z9hG4bK-d8754z-3d07d32ccc286b5c-1---d8754z->; state=6 0(28252) Found param type 235, <rport> = <n/a>; state=17 0(28252) end of header reached, state=5 0(28252) parse_headers: Via found, flags=1 0(28252) parse_headers: this is the first via 0(28252) After parse_msg... 0(28252) preparing to run routing scripts... 0(28252) parse_headers: flags=128 0(28252) DEBUG:maxfwd:is_maxfwd_present: value = 70 0(28252) DBG:maxfwd:process_maxfwd_header: value 70 decreased to 16 0(28252) parse_headers: flags=256 0(28252) end of header reached, state=9 0(28252) DEBUG: get_hdr_field: <To> [39]; uri=[sip:123456@123.49.54.226<sip%3A123456(a)123.49.54.226> ] 0(28252) DEBUG: to body ["123456"<sip:123456@123.49.54.226<sip%3A123456(a)123.49.54.226> > ] 0(28252) get_hdr_field: cseq <CSeq>: <1> <REGISTER> 0(28252) DEBUG: get_hdr_body : content_length=0 0(28252) found end of header 0(28252) find_first_route: No Route headers found 0(28252) loose_route: There is no Route HF 0(28252) grep_sock_info - checking if host==us: 13==13 && [123.49.54.226] == [123.49.54.226] 0(28252) grep_sock_info - checking if port 5060 matches port 80 0(28252) grep_sock_info - checking if host==us: 13==13 && [123.49.54.226] == [123.49.54.226] 0(28252) grep_sock_info - checking if port 5060 matches port 80 0(28252) check_self: host != me 0(28252) parse_headers: flags=-1 0(28252) DEBUG: t_newtran: msg id=1 , global msg id=0 , T on entrance=0xffffffffffffffff 0(28252) parse_headers: flags=-1 0(28252) parse_headers: flags=60 0(28252) t_lookup_request: start searching: hash=57920, isACK=0 0(28252) DEBUG: RFC3261 transaction matching failed 0(28252) DEBUG: t_lookup_request: no transaction found 0(28252) DEBUG: mk_proxy: doing DNS lookup... 0(28252) check_via_address(122.162.142.65, 192.168.1.2, 0) 0(28252) DEBUG: add_to_tail_of_timer[4]: 0x2acf403e64e0 0(28252) DEBUG: add_to_tail_of_timer[0]: 0x2acf403e6500 0(28252) SER: new transaction fwd'ed 0(28252) DEBUG:destroy_avp_list: destroying list (nil) 0(28252) receive_msg: cleaning up 1(28253) DEBUG: timer routine:4,tl=0x2acf403e64e0 next=(nil) 1(28253) DEBUG: retransmission_handler : request resending (t=0x2acf403e6308, REGISTER ... ) 1(28253) DEBUG: add_to_tail_of_timer[5]: 0x2acf403e64e0 1(28253) DEBUG: retransmission_handler : done 1(28253) DEBUG: timer routine:5,tl=0x2acf403e64e0 next=(nil) 1(28253) DEBUG: retransmission_handler : request resending (t=0x2acf403e6308, REGISTER ... ) 1(28253) DEBUG: add_to_tail_of_timer[6]: 0x2acf403e64e0 1(28253) DEBUG: retransmission_handler : done 1(28253) DEBUG: timer routine:6,tl=0x2acf403e64e0 next=(nil) 1(28253) DEBUG: retransmission_handler : request resending (t=0x2acf403e6308, REGISTER ... ) 1(28253) DEBUG: add_to_tail_of_timer[7]: 0x2acf403e64e0 1(28253) DEBUG: retransmission_handler : done 1(28253) DEBUG: timer routine:7,tl=0x2acf403e64e0 next=(nil) 1(28253) DEBUG: retransmission_handler : request resending (t=0x2acf403e6308, REGISTER ... ) 1(28253) DEBUG: add_to_tail_of_timer[7]: 0x2acf403e64e0 1(28253) DEBUG: retransmission_handler : done 1(28253) DEBUG: timer routine:7,tl=0x2acf403e64e0 next=(nil) 1(28253) DEBUG: retransmission_handler : request resending (t=0x2acf403e6308, REGISTER ... ) 1(28253) DEBUG: add_to_tail_of_timer[7]: 0x2acf403e64e0 1(28253) DEBUG: retransmission_handler : done Anand Dayal -- Anand Dayal

1 0

[Serusers] proxy health
by Sabatella, Michael 19 Mar '10

19 Mar '10

So I sent an email out a few weeks ago regarding the stateful stats in ser 0.9.6. Stateful Statistics Current: 6 (200 waiting) Total: 6387581 (0 local) Replied localy: 6869160 The number waiting is slowly going up. Can somebody point me to a developer of ser I can talk to regarding this? So far there is no affect to any of my users but I want to make sure this does not get out of hand. Thanks Mike ________________________________ DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems.

2 2

[Kamailio-Users] Reminder: VUC Today, SIP Router Project
by Daniel-Constantin Mierla 19 Mar '10

19 Mar '10

Hello, a kind reminder for today's audio conference scheduled for 16:00GMT. Check the start time for your zone at: http://vuc.me/next After presenting the achievements so far within SIP Router, with what is new in 3.0.0 release and development version, you have an unique opportunity to ask questions to: - Andrei Pelinescu-Onciul, the creator of SIP Express Router (SER), the architect behind the core (transport layers, memory management, asynchronous processing, timers, etc), who will be also able to answer anything from project's history started in 2001 - Alex Balashov, Kamailio management team member, experienced consultant in building large SIP platforms - myself, as co-founder of Kamailio (OpenSER) You can join via irc on #vuc (note that some of us started to hang out on #sip-router) channel at irc.freenode.net. Dialing to VUC is possible via sip, skype, pstn, web page and more, see: http://vuc.me Five hours to go right now, hear you then! Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

1 0

[Kamailio-Users] Kamailio - SIP Router on GSoC 2010
by Daniel-Constantin Mierla 19 Mar '10

19 Mar '10

Hello, I have the pleasure to announce that our project has an accepted application for Google Summer of Code 2010. The proposed application was done within SIP Communicator Organization and is related to extending the presence server for conference calls notifications. See more: http://www.sip-communicator.org/index.php/GSOC2010/Kamailio4575 http://www.sip-communicator.org/index.php/Development/Gsoc2010 The friends from SEMS project will be part as well, with separate application, implementing the audio mixer part. More details will be published soon. Start thinking about good candidates (they must be students (college or university)), we need them to get the project accepted for implementation. Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

1 0

[Kamailio-Users] uac_replace_from unexpected behavior
by Brandon Armstead 18 Mar '10

18 Mar '10

Hello, As always thank you ahead of time for your help and input! I am currently calling uac_replace_from("", "") in effort to "leave uri" and "toss away display name" Which does seem to work....... for the initial INVITE However upon receiving an ACK with an empty display, however "" <- quotations, it does not clear the display "" which is causing issues with one of my upstream vendors. Example / Scenario: From: "" <sip:uri@host> Expected Result upon uac_replace_from("",""): From: <sip:uri@host> Current Result: From: "" <sip:uri@host> As you can see it is not stripping the "" empty display quotes. Any thoughts / ideas / suggestions to get my desired affect? Sincerely, Brandon Armstead

3 10

[Kamailio-Users] Rtpproxy/Kamailio modification to support high capacity encryption, transcoding
by Vikram Ragukumar 18 Mar '10

18 Mar '10

Hello, We're making initial modifications to rtpproxy to support high channel capacity transcoding and encryption. At this point we want to get some general idea of the scope of changes needed for rtpproxy and Kamailio... so we're starting with small steps. We've been studying rtpproxy source and our current thinking is to add a sub-structure to the existing rtpp_session structure (defined in rtpp_session.h). The new sub-structure would include: -encryption options (type, key length, salt size, type of key mgt protocol, etc) -encode / decode options (type, VAD/CNG, VIF size, etc) Any comments or advice on this approach appreciated. Not sure whether to start a separate thread, but also there is the issue of what changes are necessary to Kamailio to support sending updated commands to rtpproxy. Would modifying Nathelper alone be sufficient? Thanks and Regards, Vikram. PS : I'm posting on Kamailio's mailing list because it seems that both Kamailio and rtpproxy developers closely follow this list.

3 3

[Kamailio-Users] SIP Router Project of VUC, March 19
by Daniel-Constantin Mierla 18 Mar '10

18 Mar '10

Hello, this Friday, March 19, late afternoon, the weekly VoIP User Conference is hosting a session about SIP Router project. My goals are to present the achievements so far within SIP Router projects, what is new in Kamailio 3.0 release and plans for the future. More details can be found at: http://www.kamailio.org/w/vuc-the-sip-router-project/ You can join the audio conference via sip, skype, pstn line or other several options presented on http://vuc.me site. There is a irc channel available for it: #vuc on irc.freenode.net. Cheers, Daniel -- Daniel-Constantin Mierla Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 * http://www.asipto.com/index.php/sip-router-masterclass/

1 1

[Kamailio-Users] kamailio logo artwork
by Daniel-Constantin Mierla 18 Mar '10

18 Mar '10

Hello, courtesy of Elio Rojano (http://www.sinologic.net), very nice logo artworks are available now, using openser or sip-router thematics. You can browse at: http://www.asipto.com/gallery/v/ksr-artwork/ Available for download as well at: http://www.kamailio.org/pub/ksr-artwork/ If you are good at graphic design and have new ideas, please submit. Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

1 0

[Kamailio-Users] Kamailio 3.0.0 Install Error
by Nathaniel L Keeling 17 Mar '10

17 Mar '10

I am trying to install the new release of Kamailio 3.0.0 on Solaris 10. When I perform the install, I am getting this error. Here is the command that I am entering for the install: make prefix=/usr/local/kamailio-3.0.0 INSTALL=install group_include="standard standard-dep postgres" CPU=ultrasparc install install mode make[2]: Entering directory `/usr/local/src/kamailio-3.0.0/lib/kcore' make[2]: Nothing to be done for `install-if-newer'. make[2]: Leaving directory `/usr/local/src/kamailio-3.0.0/lib/kcore' touch /usr/local/kamailio-3.0.0/lib/kamailio/modules_k/speeddial.so install -m 755 speeddial.so /usr/local/kamailio-3.0.0/lib/kamailio/modules_k make[1]: Leaving directory `/usr/local/src/kamailio-3.0.0/modules_k/speeddial' mkdir -p /usr/local/kamailio-3.0.0/etc/kamailio/ # other configs /bin/sh: syntax error at line 1: `;' unexpected make: *** [install-cfg] Error 2 I am new to Kamailio and would appreciate any help. Thanks Nathaniel

3 3

Re: [Kamailio-Users] Is Timestamp supported in kamailio?
by Iñaki Baz Castillo 17 Mar '10

17 Mar '10

2010/3/16 mustafa rifaee <mustafa.rifaee(a)gmail.com>: > Hi all, > I would like to asking you Hi, it's just better to keep the thread in the maillist. > about the Time-stamp header in SIP messages, and > why this header does not supported in most open SIP servers, Is it > recommended or not? > Is this fact true ?? I think The problem is that both UAS and UAC must have > the same system time to generate a useful result. So therefore both or all > SIP devices (think about an intermediate proxy) must have NTP activated. That's not true. The request can contain a header like: TimeStamp: 25 and the proxy/server replies in the 100 Trying: TimeStamp: 25 0.001 This means that it has token 0.001 seconds to the server in order to process the request and generate the 100 response. -- Iñaki Baz Castillo <ibc(a)aliax.net> -- Iñaki Baz Castillo <ibc(a)aliax.net>

4 8

[Kamailio-Users] [OT] MSN presence flow
by Iñaki Baz Castillo 17 Mar '10

17 Mar '10

Hi, does somebody have a MSN protocol flow related to presence rules or buddies management? This is, I would like to know how MSN protocol imlements some tasks as: - Adding a buddy. - Blocking a buddy for presence. - Blocking a contact (not a buddy) for presence. Thanks. -- Iñaki Baz Castillo <ibc(a)aliax.net>

2 3

Re: [Kamailio-Users] kamailio crashes
by Panagiotis Skoulikaritis 17 Mar '10

17 Mar '10

Hello Daniel I do have quite a few core files, please send me the gdb commands. Regards Panagiotis. Daniel-Constantin Mierla wrote: > Hello Panagiotis, > > On 03/16/2010 02:21 PM, Panagiotis Skoulikaritis wrote: >> Hello Daniel >> >> I will need time to recreate the problem, >> attached are the only traces I kept. >> on the amaze-4.cap the calls are originated by a softphone registered >> on the kamailio >> on the crash.cap the calls are originated from the "PSTN". >> >> we do account the $pd and the $pn >> >> I reply to you directly since i don't want to give the traces on the >> mailing list, I hope you will understand. > > I asked to be sent private, it is ok. > >> >> Also for workaround Alex took out the PDT module from the route and >> the kamailio do not crash anymore. > > Hmm, so you say pdt module is related? That is pretty small and old > module... > > Do you still have the core file? I can send you some gdb commands to > get more details out of it. > > Thanks, > Daniel > >> >> Regards >> >> Panagiotis >> >> >> Daniel-Constantin Mierla wrote: >>> Hello, >>> >>> can you send me ngrep/pcap file with ip addresses so I can match >>> which 200ok is causing the problem (coming from B or coming from >>> Asterisk)? The backtrace shows ip while the sip trace is masked. >>> >>> Also, I would need a bit more info from the core file. Please keep >>> one around. The issue seems to be related to P-Asserted-Identity >>> header, but I couldn't find any such header in the sip trace you sent. >>> >>> Are you accounting the PAI header? >>> >>> Thanks, >>> Daniel >>> >>> On 03/10/2010 03:30 PM, Panagiotis Skoulikaritis wrote: >>>> Dear Marius >>>> >>>> The scenario is as follows: >>>> >>>> 1. A Call is placed by a sip subscriber "A" >>>> 2. kamailio forwards the call to the asterisk server >>>> 3. Asterisk plays an IVR message on the subscriber "A", creates a >>>> new call to a "virtual" number which is forwarded to the kamailio >>>> server, and plays an ivr to this leg as well when the call is >>>> answered, then it connects the two calls. >>>> 4. Kamailio translates the "virtual" number to the pstn number of >>>> subscriber B >>>> >>>> >>>> I have attached a picture of the above scenario. >>>> >>>> The modules that are loaded are: >>>> >>>> loadmodule "db_mysql.so" >>>> loadmodule "mi_fifo.so" >>>> loadmodule "mi_datagram.so" >>>> loadmodule "sl.so" >>>> loadmodule "tm.so" >>>> loadmodule "rr.so" >>>> loadmodule "pv.so" >>>> loadmodule "maxfwd.so" >>>> loadmodule "usrloc.so" >>>> loadmodule "registrar.so" >>>> loadmodule "textops.so" >>>> loadmodule "uri_db.so" >>>> loadmodule "siputils.so" >>>> loadmodule "xlog.so" >>>> loadmodule "acc.so" >>>> loadmodule "dispatcher.so" >>>> loadmodule "pdt.so" >>>> loadmodule "dialplan.so" >>>> loadmodule "siptrace.so" >>>> loadmodule "dialog.so" >>>> loadmodule "sqlops.so" >>>> loadmodule "userblacklist.so" >>>> loadmodule "htable.so" >>>> loadmodule "uac.so" >>>> >>>> >>>> The config that does all the routing is : >>>> >>>> route[10] { >>>> >>>> xlog("alx ------- This is Route 10 -------"); >>>> >>>> if($rU =~ "^.*%+") >>>> { >>>> xlog("alx ------- The number contains %23 "); >>>> $rU = $(rU{re.subst,/^(.*)%23(.*)/\1\2/}); >>>> #$rU = $(rU{s.unescape.user}); #It changes the %23 >>>> to # !! >>>> xlog("alx ------- The perl $rU ------- "); >>>> } >>>> >>>> if($rU =~ "^.*#+") >>>> { >>>> xlog("alx ------- The number contains #"); >>>> $rU = $(rU{re.subst,/^(.*)#(.*)/\1\2/}); >>>> #$rU = $(rU{s.unescape.user}); #It changes the %23 >>>> to # !! >>>> xlog("alx ------- The perl $rU ------- "); >>>> } >>>> >>>> if(prefix2domain("2", "0")) { >>>> >>>> $var(dial_grp) = $(rd{s.select,0,.}{s.int}); # >>>> Dialplan group prefix for routing >>>> $var(num_pr) = $(rd{s.select,1,.}{s.int}); # The >>>> number of digits that prefix has >>>> $var(num_translation) = >>>> $(rd{s.select,2,.}{s.int}); # Called number translation >>>> $avp(s:port_translation) = >>>> $(rd{s.select,3,.}{s.int}); # Port number translation >>>> #$var(test_var) = $(rd{s.select,4,.}{s.int}); # >>>> Future property >>>> >>>> $avp(s:cust_prefix) = $(rU{s.substr,0,$var(num_pr)}); >>>> $rU = $(rU{s.substr,$var(num_pr),0}); >>>> >>>> xlog("alx ------- The new rU is $rU and properties $rd >>>> -------"); >>>> >>>> if($var(num_translation) == 1) >>>> { >>>> if($sht(a=>$rU)!=null){ >>>> >>>> $rU = $sht(a=>$rU); >>>> xlog("alx ------- Translation Done. DST >>>> num=$rU ----------"); >>>> >>>> } else { >>>> xlog("alx ------- Translation NOT Done >>>> ----------"); >>>> } >>>> >>>> >>>> #xlog("alx ------- We have DST number >>>> translation for user fU $avp(s:frm_user_name) ----------"); >>>> #if(dp_translate("31", "$rU/$rU")) >>>> #{ >>>> # xlog("alx ------- Translation Done. >>>> DST num=$rU ----------"); >>>> #} else { >>>> # xlog("alx ------- Translation NOT >>>> Done ----------"); >>>> #} >>>> } >>>> >>>> if(dp_translate("$var(dial_grp)", "$rU/$rU")) >>>> { >>>> xlog("alx ------- The $rU and with >>>> attributes :$avp(s:dest) -------\n"); >>>> >>>> $var(i) = 0; >>>> while($(avp(s:dest){s.select,$var(i),.})!="#") >>>> { >>>> $avp(s:dstgrp) = >>>> $(avp(s:dest){s.select,$var(i),.}{s.int}); >>>> $var(i) = $var(i) + 1; >>>> xlog("alx ------- The >>>> avp(s:dstgrp)=$avp(s:dstgrp) var(i)=$var(i) -------"); >>>> } >>>> >>>> # backup the username so we can use >>>> different prefixes >>>> $avp(s:user) = $rU; >>>> >>>> # select destination from first group >>>> >>>> if(ds_select_domain("$avp(s:dstgrp)", "4")) >>>> { >>>> >>>> if($(ru{uri.param,prefix})!=null) >>>> { >>>> $ru >>>> = "sip:" + $(ru{uri.param,prefix}) + $avp(s:user) + "@" + $rd; >>>> >>>> } else { >>>> $ru >>>> = "sip:" + $avp(s:user) + "@" + $rd; >>>> } >>>> } >>>> >>>> $avp(s:dstgrp) = null; >>>> xlog("alx ------- The final >>>> RURI is $ru ------- "); >>>> if($avp(s:port_translation) >>>> == 1) >>>> { >>>> rewriteport("5061"); >>>> } >>>> t_on_failure("3"); >>>> t_relay(); >>>> exit; >>>> >>>> } >>>> >>>> >>>> >>>> >>>> } >>>> >>>> >>>> } >>>> >>>> Attached is the trace >>>> >>>> Regards. >>>> >>>> P. >>>> >>>> marius zbihlei wrote: >>>>> Panagiotis Skoulikaritis wrote: >>>>>> Hello Daniel >>>>>> >>>>>> the kamailio version is 1.5.3 >>>>>> >>>>>> Regards >>>>>> >>>>>> P. >>>>> Hello, >>>>> >>>>> Can you give us more details like the sip message that generates >>>>> the coredump (or if every sip message received generates the >>>>> core), if your config does something more out of the >>>>> ordinary(let's say exotic). Can we reproduce it ? >>>>> >>>>> It would also be helpful if you specify the list of modules you >>>>> have loaded. >>>>> >>>>> Cheers, >>>>> Marius >>>>>> >>>>>> Daniel-Constantin Mierla wrote: >>>>>>> Hello, >>>>>> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >>>>> >>>> >>>> _______________________________________________ >>>> Kamailio (OpenSER) - Users mailing list >>>> Users(a)lists.kamailio.org >>>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >>>> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >>> >>> -- >>> Daniel-Constantin Mierla >>> Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 >>> * http://www.asipto.com/index.php/sip-router-masterclass/ >>> > > -- > Daniel-Constantin Mierla > Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 > * http://www.asipto.com/index.php/sip-router-masterclass/ >

2 1

Re: [Kamailio-Users] Is Timestamp supported in kamailio?
by Iñaki Baz Castillo 16 Mar '10

16 Mar '10

2010/3/16 mustafa rifaee <mustafa.rifaee(a)gmail.com>: > Hi Castillo, > I would like to asking you about the Time-stamp header in SIP messages, and > why this header does not supported in most open SIP servers, Is it > recommended or not? > Is there any open source support the time stamp header. > > Is this fact true ?? I think The problem is that both UAS and UAC must have > the same system time to generate a useful result. So therefore both or all > SIP devices (think about an intermediate proxy) must have NTP activated. > > Please Help me; I think I *already* helped you as you *already* asked me directly. Please, keep the threads in the maillist, nobody likes to give private free support. -- Iñaki Baz Castillo <ibc(a)aliax.net>

1 0

[Kamailio-Users] Is Timestamp supported in kamailio?
by mustafa rifaee 16 Mar '10

16 Mar '10

Hi all; I would like to ask you about the timestamp in kamailio, Is it supported or not ? if yes how i can enable it ? Please Help me; Thanks. Best Regards Mustafa Rifaee

3 3

[Kamailio-Users] [dialog module] dialog is not terminated when no ACK is received
by Iñaki Baz Castillo 16 Mar '10

16 Mar '10

Hi, using Kamailio 1.5.4. I use dlg_manage() for an INVITE. 200 Ok is replied by the callee but the UAC doesn't send the ACK (due to a crash). The dialog remains in Kamailio dialog memory/table in state 3 and would expire after default_timeout (which usually is 3600 seconds or more, unsuitable for this case). Yes, it could occur that the proxy is not doing loose_routing, but in that case it doesn't make sense to use dialog module, so shouldn't dialog module expire dialogs in state 3 after ~32 seconds? I'm using profiles_with_value to limit the number of calls per user, so this issue is a bit important, as a UAC not sending the ACK for a 200 means one less available channel for this user during dialog module default_timeout. -- Iñaki Baz Castillo <ibc(a)aliax.net>

3 8

[Kamailio-Users] maintenance this afternoon
by Daniel-Constantin Mierla 15 Mar '10

15 Mar '10

Hello, some small maintenance tasks will be performed afternoon today to the server hosting the mailing lists and kamailio.org site, if you notice some downtime, try again a bit later. Thanks, Daniel

2 2

[Kamailio-Users] kamailio crashes
by Panagiotis Skoulikaritis 14 Mar '10

14 Mar '10

Dear fellow kaimailio users We have a kamailio server which crashes. below is the backtrace from the core files any idea why the kamailio is crashing Regards Panagiotis core.29568 Mar 10 09:27 #0 fm_status (qm=0x73a040) at mem/f_malloc.c:609 #1 0x0000000000423d5c in sig_usr (signo=15) at main.c:563 #2 <signal handler called> #3 0x00000037e3cd4711 in __recvfrom_nocancel () from /lib64/libc.so.6 #4 0x00000000004790cc in udp_rcv_loop () at udp_server.c:408 #5 0x000000000042760e in main (argc=3, argv=0x7fff8bf6abc8) at main.c:774 core.19350 Mar 10 09:05 (gdb) backtrace #0 free_to (tb=0x775c00) at parser/parse_to.c:79 #1 0x000000000047fd42 in clean_hdr_field (hf=0x2ad2432de100) at parser/hf.c:187 #2 0x00002ad23fe3e525 in run_trans_callbacks (type=<value optimized out>, trans=<value optimized out>, req=0x2ad2432dcf58, rpl=0x772d28, code=<value optimized out>) at sip_msg.h:54 #3 0x00002ad23fe47b46 in t_reply_matching (p_msg=0x772d28, p_branch=<value optimized out>) at t_lookup.c:888 #4 0x00002ad23fe47fa2 in t_check (p_msg=0x772d28, param_branch=0x7ffff9c016bc) at t_lookup.c:964 #5 0x00002ad23fe58ac2 in reply_received (p_msg=0x73a040) at t_reply.c:1395 #6 0x000000000041eebc in forward_reply (msg=0x772d28) at forward.c:521 #7 0x0000000000445313 in receive_msg ( buf=0x718dc0 "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 77.247.97.11;branch=z9hG4bK45f7.70f91294.0;received=77.247.97.11\r\nV", len=920, rcv_info=0x7ffff9c017a0) at receive.c:212 #8 0x00000000004794ae in udp_rcv_loop () at udp_server.c:449 #9 0x000000000042760e in main (argc=3, argv=0x7ffff9c019b8) at main.c:774 (gdb) core.29567 Mar 10 09:27 gdb) backtrace #0 free_to (tb=0x776460) at parser/parse_to.c:79 #1 0x000000000047fd42 in clean_hdr_field (hf=0x2ad1805fa100) at parser/hf.c:187 #2 0x00002ad17d15a525 in run_trans_callbacks (type=<value optimized out>, trans=<value optimized out>, req=0x2ad1805f8f58, rpl=0x771920, code=<value optimized out>) at sip_msg.h:54 #3 0x00002ad17d163b46 in t_reply_matching (p_msg=0x771920, p_branch=<value optimized out>) at t_lookup.c:888 #4 0x00002ad17d163fa2 in t_check (p_msg=0x771920, param_branch=0x7fff8bf6a8cc) at t_lookup.c:964 #5 0x00002ad17d174ac2 in reply_received (p_msg=0x73a040) at t_reply.c:1395 #6 0x000000000041eebc in forward_reply (msg=0x771920) at forward.c:521 #7 0x0000000000445313 in receive_msg ( buf=0x718dc0 "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 77.247.97.11;branch=z9hG4bKddc9.fa58f7e.0;received=77.247.97.11\r\nVia: SIP/2.0/UDP 213.170.194.47:5060;branch=z9hG4bKb973f6a69c9bea270e9db867dd7cc90f\r\nRecord-Route: <si"..., len=919, rcv_info=0x7fff8bf6a9b0) at receive.c:212 #8 0x00000000004794ae in udp_rcv_loop () at udp_server.c:449 #9 0x000000000042760e in main (argc=3, argv=0x7fff8bf6abc8) at main.c:774 (gdb) core.5326 Mar 10 09:02 (gdb) backtrace #0 free_to (tb=0x772c48) at parser/parse_to.c:79 #1 0x000000000047fd42 in clean_hdr_field (hf=0x2b2578e22560) at parser/hf.c:187 #2 0x00002b257597b525 in run_trans_callbacks (type=<value optimized out>, trans=<value optimized out>, req=0x2b2578e213b8, rpl=0x771b50, code=<value optimized out>) at sip_msg.h:54 #3 0x00002b2575984b46 in t_reply_matching (p_msg=0x771b50, p_branch=<value optimized out>) at t_lookup.c:888 #4 0x00002b2575984fa2 in t_check (p_msg=0x771b50, param_branch=0x7fff7cdc63ac) at t_lookup.c:964 #5 0x00002b2575995ac2 in reply_received (p_msg=0x772c48) at t_reply.c:1395 #6 0x000000000041eebc in forward_reply (msg=0x771b50) at forward.c:521 #7 0x0000000000445313 in receive_msg ( buf=0x718dc0 "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 77.247.97.11;branch=z9hG4bKec2f.dc3d97a7.0;received=77.247.97.11\r\nVia: SIP/2.0/UDP 213.170.194.47:5060;branch=z9hG4bK47703457194f5be415efc231f6b3e923\r\nRecord-Route: <s"..., len=918, rcv_info=0x7fff7cdc6490) at receive.c:212 #8 0x00000000004794ae in udp_rcv_loop () at udp_server.c:449 #9 0x000000000042760e in main (argc=5, argv=0x7fff7cdc66a8) at main.c:774 (gdb) quit

3 5

[Kamailio-Users] Loadbalancer/outbound_proxy and ACK problem
by Pavel Miskov 13 Mar '10

13 Mar '10

Hello list, let me first show my scenario: UAC_A ---> LB ---> | | PROXY+REG #1 | or | PROXY+REG #2 UAC_B <--- LB <--- | LB cfg: modparam("path", "use_received", 1) loose_route(); #for REG+PROXY if(is_method("REGISTER")){ add_path_received(); ds_select_dst("1", "0"); fix_nated_register(); } else { record_route(); add_path(); ds_select_dst("1", "0"); fix_nated_register(); } PROXY+REG cfg: ------------- modparam("registrar", "use_path", 1) modparam("registrar", "path_mode", 0) modparam("registrar", "path_use_received", 1) INVITE if working fine until ACK. UAC_A sends ACK to LB "ACK sip:UAC_B@LB_IP:5678;" insted of "ACK sip:UAC_B@UAC_B_PUB_IP:". In "200 OK" which PROXY sends to LB Contact is rewritten with ip addres of LB "Contact: <sip:UAC_B@LB_IP:5678;" and this is why UAC_A sends wrong ACK. Obviously I miss something so if someone could point me where to look. Thanks Pavel U UAC_A_PUB_IP:31488 -> LB_IP:5678 INVITE sip:UAC_B@test.com SIP/2.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport..Max-Forwards: 70..Contact: <sip:UAC_A@UAC_A_PRIV_IP:31488>..To: "UAC_B"<sip:UAC_B@test.com>..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID:ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE.. # U LB_IP:5678 -> UAC_A_PUB_IP:31488 SIP/2.0 100 Giving a try..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488;received=UACs_PUB_IP..To: "UAC_B"<sip:UAC_B@test.com>..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE..Server: Kamailio (1.5.1-tls (x86_64/linux))..Content-Length: 0.... # U LB_IP:5678 -> REG_PROXY_IP:5166 INVITE sip:UAC_B@test.com SIP/2.0..Record-Route: <sip:LB_IP:5678;lr=on>..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Max-Forwards: 69..Contact: <sip:UAC_A@UAC_A_PUB_IP:31488>..To: "UAC_B"<sip:UAC_B@test.com>..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE..Path: <sip:LB_IP:5678;lr>.... # U REG_PROXY_IP:5166 -> LB_IP:5678 SIP/2.0 100 Giving a try..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..To: "UAC_B"<sip:UAC_B@test.com>..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE..Server: Kamailio (1.5.1-tls (x86_64/linux))..Content-Length: 0.... # U REG_PROXY_IP:5166 -> LB_IP:5678 INVITE sip:UAC_B@UAC_B_PRIV_IP:31468;rinstance=ed47096f240b6b6d SIP/2.0..Record-Route: <sip:REG_PROXY_IP:5166;lr=on;nat=yes>..Record-Route: <sip:LB_IP:5678;lr=on>..Via: SIP/2.0/UDP REG_PROXY_IP:5166;branch=z9hG4bKa1b1.c7ca19a7.0..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Route: <sip:LB_IP:5678;lr;received="sip:UAC_B_PUB_IP:31468">..Max-Forwards: 68..Contact: <sip:UAC_A@UAC_A_PUB_IP:31488>..To: "UAC_B"<sip:UAC_B@test.com>..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE..Path: <sip:LB_IP:5678;lr>.... # U LB_IP:5678 -> REG_PROXY_IP:5166 SIP/2.0 100 Giving a try..Via: SIP/2.0/UDP REG_PROXY_IP:5166;branch=z9hG4bKa1b1.c7ca19a7.0;rport=5166;received=REG_PROXY_IP..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..To: "UAC_B"<sip:UAC_B@test.com>..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE..Server: Kamailio (1.5.1-tls (x86_64/linux))..Content-Length: 0.... # U LB_IP:5678 -> UAC_B_PUB_IP:31468 INVITE sip:UAC_B@UAC_B_PRIV_IP:31468;rinstance=ed47096f240b6b6d SIP/2.0..Record-Route: <sip:REG_PROXY_IP:5166;lr=on;nat=yes>..Record-Route: <sip:LB_IP:5678;lr=on>..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.56778065.0..Via: SIP/2.0/UDP REG_PROXY_IP:5166;rport=5166;received=REG_PROXY_IP;branch=z9hG4bKa1b1.c7ca19a7.0..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Max-Forwards: 67..Contact: <sip:UAC_A@UAC_A_PUB_IP:31488>..To: "UAC_B"<sip:UAC_B@test.com>..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE..Path: <sip:LB_IP:5678;lr>.... # U UAC_B_PUB_IP:31468 -> LB_IP:5678 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.56778065.0..Via: SIP/2.0/UDP REG_PROXY_IP:5166;rport =5166;received=REG_PROXY_IP;branch=z9hG4bKa1b1.c7ca19a7.0..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Record-Route: <sip:REG_PROXY_IP:5166;lr;nat=yes>..Record-Route: <sip:LB_IP:5678;lr=on>..Contact: <sip:UAC_B@UAC_B_PRIV_IP:31 468;rinstance=ed47096f240b6b6d>..To: "UAC_B"<sip:UAC_B@test.com>;tag=2e79423e..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41.. Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE..User-Agent: X-Lite release 1100l stamp 47546..Content-Length: 0.... # U LB_IP:5678 -> REG_PROXY_IP:5166 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP REG_PROXY_IP:5166;rport=5166;received=REG_PROXY_IP;branch=z9hG4bKa1b1.c7ca19a7.0..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Record-Route: <sip:REG_PROXY_IP:5166;lr;nat=yes>..Record-Route: <sip: LB_IP:5678;lr=on>..Contact:<sip:UAC_B@UAC_B_PRIV_IP:31468;rinstance=ed47096f240b6b6d>..To: "UAC_B"<sip:UAC_B@test.com>;tag=2e79423e..From:"UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE..User-Agent: X-Lite release 1100l stamp 47546..Content-Length: 0.... # U REG_PROXY_IP:5166 -> LB_IP:5678 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Record-Route: <sip:REG_PROXY_IP:5166;lr;nat=yes>..Record-Route: <sip:LB_IP:5678;lr=on>..Contact: <sip:UAC_B@LB_IP:5678;rinstance=ed47096f240b6b6d>..To:"UAC_B"<sip:UAC_B@test.com>;tag=2e79423e..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE..User-Agent: X-Lite release 1100l stamp 47546..Content-Length: 0.... # U LB_IP:5678 -> UAC_A_PUB_IP:31488 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Record-Route: <sip:REG_PROXY_IP:5166;lr;nat=yes>..Record-Route: <sip:LB_IP:5678;lr=on>..Contact: <sip:UAC_B@LB_IP:5678;rinstance=ed47096f240b6b6d>..To: "UAC_B"<sip:UAC_B@test.com>;tag=2e79423e..From:"UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE..User-Agent: X-Lite release 1100l stamp 47546..Content-Length: 0.... # U UAC_B_PUB_IP:31468 -> LB_IP:5678 SIP/2.0 200 OK..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.56778065.0..Via: SIP/2.0/UDP REG_PROXY_IP:5166;rport=5166;received=REG_PROXY_IP;branch=z9hG4bKa1b1.c7ca19a7.0..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Record-Route: <sip:REG_PROXY_IP:5166;lr;nat=yes>..Record-Route: <sip:LB_IP:5678;lr=on>..Contact: <sip:UAC_B@UAC_B_PRIV_IP:31468;r instance=ed47096f240b6b6d>..To: "UAC_B"<sip:UAC_B@test.com>;tag=2e79423e..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE.. # U LB_IP:5678 -> REG_PROXY_IP:5166 SIP/2.0 200 OK..Via: SIP/2.0/UDP REG_PROXY_IP:5166;rport=5166;received=REG_PROXY_IP;branch=z9hG4bKa1b1.c7ca19a7.0..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Record-Route: <sip:REG_PROXY_IP:5166;lr;nat=yes>..Record-Route: <sip:LB_IP:5678;lr=on>..Contact:<sip:UAC_B@UAC_B_PRIV_IP:31468;rinstance=ed47096f240b6b6d>..To: "UAC_B"<sip:UAC_B@test.com>;tag=2e79423e..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE.. # U REG_PROXY_IP:5166 -> LB_IP:5678 SIP/2.0 200 OK..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Record-Route: <sip:REG_PROXY_IP:5166;lr;nat=yes>..Record-Route: <sip:LB_IP:5678;lr=on>..Contact: <sip:UAC_B@LB_IP:5678;rinstance=ed47096f240b6b6d>..To: "UAC_B"<sip:UAC_B@test.com>;tag=2e79423e..From:"UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE.. # U LB_IP:5678 -> UAC_A_PUB_IP:31488 SIP/2.0 200 OK..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-d33a97176d49f84b-1---d8754z-;rport=31488..Record-Route: <sip:REG_PROXY_IP:5166;lr;nat=yes>..Record-Route: <sip:LB_IP:5678;lr=on>..Contact: <sip:UAC_B@LB_IP:5678;rinstance=ed47096f240b6b6d>..To: "UAC_B"<sip:UAC_B@test.com>;tag=2e79423e..From: "UAC_A"<sip:UAC_A@test.com >;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 INVITE.. # U UAC_A_PUB_IP:31488 -> LB_IP:5678 ACK sip:UAC_B@LB_IP:5678;rinstance=ed47096f240b6b6d SIP/2.0..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;branch=z9hG4bK-d8754z-0472a03b5d1aa106-1---d8754z-;rport..Max-Forwards: 70..Route: <sip:LB_IP:5678;lr>..Route: <sip:REG_PROXY_IP:5166;lr;nat=yes>..Contact: <sip:UAC_A@UAC_A_PRIV_IP:31488>..To: "UAC_B"<sip:UAC_B@test.com>;tag=2e79423e..From: "UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 ACK.. # U LB_IP:5678 -> REG_PROXY_IP:5166 ACK sip:REG_PROXY_IP:5166;lr;nat=yes SIP/2.0..Via: SIP/2.0/UDP LB_IP:5678;branch=z9hG4bKa1b1.46778065.2..Via: SIP/2.0/UDP LB_IP:5678;rport=5678;received=LB_IP;branch=z9hG4bKa1b1.46778065.2..Via: SIP/2.0/UDP UAC_A_PRIV_IP:31488;received=UACs_PUB_IP;branch=z9hG4bK-d8754z-0472a03b5d1aa106-1---d8754z-;rport=31488..Max-Forwards: 68..Contact: <sip:UAC_A@UAC_A_PUB_IP:31488>..To: "UAC_B"<sip:UAC_B@test.com>;tag=2e79423e..From:"UAC_A"<sip:UAC_A@test.com>;tag=8c3b5c41..Call-ID: ZTliZWQ4 YTM5MjVkYjUxYTk3MmUxZmVhOGY5MzlmM2Q...CSeq: 2 ACK..

3 5

[Kamailio-Users] What is the best module for routing INVITE based on DID in R-URI?
by Geoffrey Mina 13 Mar '10

13 Mar '10

Hello, I am putting up a Kamailio server which will do nothing but route INVITE requests from my upstream carrier to individual offices on my side. The office locations will NOT be registered SIP UAs, but other Kamailio proxy servers. What I want to have is a database of DIDs associated with a forwarding IP:Port and/or SRV records. 5555551212 ==> 1.2.3.4:5060 5555551213 ==> 1.2.3.5:5060 etc. Any guidance on what the best approach to achieving my goal would be much appreciated. Thanks, Geoff

4 12

[Kamailio-Users] need help to use the Kamailio register to remote sip proxy
by Cucku Cucku 12 Mar '10

12 Mar '10

Hi all i found the Kamailio supports register to remote sip proxy: http://www.mail-archive.com/users@lists.kamailio.org/msg07451.html it mentions to use : SQL to create the mysql table is in utils/kamctl/mysql/uac-create.sql but i didnt find the sql script My sip proxy version : sercmd> core.version Server: kamailio (3.0.1 (i386/linux)) 679736 my util folder : [root@localhost kamailio-3.0.1]# ls utils/kamctl/mysql/ acc-create.sql domainpolicy-create.sql purple-create.sql alias_db-create.sql drouting-create.sql registrar-create.sql auth_db-create.sql group-create.sql rls-create.sql avpops-create.sql htable-create.sql siptrace-create.sql carrierroute-create.sql imc-create.sql speeddial-create.sql cpl-create.sql lcr-create.sql standard-create.sql dialog-create.sql msilo-create.sql uri_db-create.sql dialplan-create.sql pdt-create.sql userblacklist-create.sql dispatcher-create.sql permissions-create.sql usrloc-create.sql domain-create.sql presence-create.sql please help Thank you Muốn đổi mới cách xưng hô với ông xã/ bà xã của bạn? Xem có bao nhiêu cách xưng hô giữa vợ và chồng nhé! http://vn.answers.yahoo.com

3 3

[Kamailio-Users] Stateless failover
by Santiago Soares 12 Mar '10

12 Mar '10

We're using Kamailio as a stateless load balancer, and would like to add failover support. Is it possible to have failover support in stateless mode? What i want is that when a server doesn't answer to a request, Kamailio set its state to probing, and start to ping it until it answer, then setting its state to active again. And that only active servers are selected by ds_select_dst(). Is it possible? How can I do this? Thank you. Santiago

4 4

[Kamailio-Users] Advanced Call Scenario / One Way Audio
by Brandon Armstead 12 Mar '10

12 Mar '10

Hello, As always, thank you for all / any help and input you may provide in advance. Call Scenario: UA1 -> REGISTRAR-01 -> Kamailio-01 -> Asterisk (New Call-ID + Asterisk in Media Path) -> Kamailio-01 -> REGISTRAR-02 -> UA2 UA1 is behind NAT UA2 is behind NAT The purpose of this is when using a shared "USRLOC" database to simulate calls from "PSTN" to generate both legs of the call, i.e. incoming and outgoing, and also allow for easier / cleaner "traversal" This aids from scenario's happening where UA1 calls UA2 (while UA1 exists on P1 and UA2 exists on P2) this prevents P1 -> UA2, and forces P2 -> UA2 We determine that this is a call from P1 to P2 (internal call) and thus create this "bridge / interconnection" We are running into a problem it seems with one way audio, i.e. the CALLEE can hear the CALLER, however the CALLER CAN NOT hear the CALLEE. REGISTRAR-01 AND REGISTRAR-02 are both "proxying" RTP As well as the initial Asterisk in "the middle" SDP. Let me know if this makes sense and if you guys have any further thoughts on what may possibily be going wrong. Perhaps there are better ways to go about this, let me know if I am way off course, thank you! Sincerely, Brandon Armstead

3 2

[Kamailio-Users] IP Authentication
by Joao Gomes Pereira 12 Mar '10

12 Mar '10

Hello to all Is is possible to implement IP authentication in Kamailio? Does Kamailio has a manual to do that? Thanks regards Joao Pereira -- StarTel - A Rede Livre Joao Gomes Pereira www.startel.pt +351 304500650 sip: gomespereira(a)startel.pt

5 8

basic sip-router installation tutorial
by Meftah Tayeb 12 Mar '10

12 Mar '10

hi all, please could anyone give me a simple step by step tutorial to setup sip-router in a debian OS with mysql and other things? from jit, no zip file... thanks

4 3

[Kamailio-Users] Handling 3XX messages
by Bruno Machado 11 Mar '10

11 Mar '10

Hi! I have a Kamailio 1.5.2 handling 3XX messages. The commands below are executed in a failure route. If the first contact is not reachable or even a negative answer is received, the algorithm will call a second failure route, executing the 't_next_contacts'. Following this logic, the server will try several endpoints. The first 200 OK received from one this endpoints will establish the call. If all the contacts are tried, the server will finish the session with sending an error to the source. get_redirects("15:15","Redirect"); if(!t_load_contacts()) { t_reply("500", "Server Internal Error - Cannot load contacts"); exit; }; if(!t_next_contacts()) t_reply("404", "Not found"); else t_relay(); Ok... I found just one problem. If the 3XX message brings 5 different contacts, (all them with different q value), Kamailio just try 4 of them. Contact: sip:20182#556250982222@aaa.aaa.aaa.aaa;q=0.015, sip:3441#556250982222@bbb.bbb.bbb.bbb;q=0.014, sip:3441#556250982222@ccc.ccc.ccc.ccc;q=0.013, sip:50014#556250982222@ddd.ddd.ddd.ddd;q=0.012, sip:777#556250982222@eee.eee.eee.eee;q=0.011 After the 300 message, the server sends a invite to the first contact. Seconds later, analysing the debug screen, I see: DBG:tm:t_next_contacts: next contact is <sip:3441#556250982222@bbb.bbb.bbb.bbb The INVITEs are sent to this IP. After some seconds the server calls the third contact: DBG:tm:t_next_contacts: next contact is <sip:3441#556250982222@ccc.ccc.ccc.ccc And so on until this, the last contact: DBG:tm:t_next_contacts: next contact is <sip:777#556250982222@eee.eee.eee.eee ERROR:core:add_avp: 0 ID or NULL NAME AVP ERROR:tm:t_next_contacts: setting of fr_inv_timer_avp failed The proxy sent INVITEs for all them, except the last one because this failure. The function 't_next_contact' returns an error value. Somebody has a hint about this? Regards, bruno machado ____________________________________________________________________________________ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com

2 1

[Kamailio-Users] Advanced Call Scenario / One Way Audio
by Brandon Armstead 11 Mar '10

11 Mar '10

**resending as I am not sure if this made it out the first time, I do not believe it did, if this is a duplicate -- my apologies.** Hello, As always, thank you for all / any help and input you may provide in advance. Call Scenario: UA1 -> REGISTRAR-01 -> Kamailio-01 -> Asterisk (New Call-ID + Asterisk in Media Path) -> Kamailio-01 -> REGISTRAR-02 -> UA2 UA1 is behind NAT UA2 is behind NAT The purpose of this is when using a shared "USRLOC" database to simulate calls from "PSTN" to generate both legs of the call, i.e. incoming and outgoing, and also allow for easier / cleaner "traversal" This aids from scenario's happening where UA1 calls UA2 (while UA1 exists on P1 and UA2 exists on P2) this prevents P1 -> UA2, and forces P2 -> UA2 We determine that this is a call from P1 to P2 (internal call) and thus create this "bridge / interconnection" We are running into a problem it seems with one way audio, i.e. the CALLEE can hear the CALLER, however the CALLER CAN NOT hear the CALLEE. REGISTRAR-01 AND REGISTRAR-02 are both "proxying" RTP As well as the initial Asterisk in "the middle" SDP. Let me know if this makes sense and if you guys have any further thoughts on what may possibily be going wrong. Perhaps there are better ways to go about this, let me know if I am way off course, thank you! Sincerely, Brandon Armstead

1 0

[Kamailio-Users] 400 Bad Request
by Ernest Mavrel 10 Mar '10

10 Mar '10

3 2

[Kamailio-Users] cdr_id not registered in acc
by Anders 10 Mar '10

10 Mar '10

Hi, (Kamailio 1.5 + freeradius + cdrtool) After a call is finished, it's INVITE and BYE are registered just fine in the acc table, but the records in acc never receive a cdr_id, and (therefore) nothing is inserted the cdrs table. Ideas on where to start looking? Thanks, Anders

2 2

[Kamailio-Users] DEFINE question
by Uriel Rozenbaum 10 Mar '10

10 Mar '10

Hi guys, The question's simple, is there any pre-processor command to DEFINE constants? Thanks! Uriel

4 6

[Kamailio-Users] OpenSER+Asterisk+BLF
by Mark Sayer 10 Mar '10

10 Mar '10

We are needing to modify the configure of a currently operating OpenSER to properly relay the SUBSCRIBE and SIP-NOTIFY messages that are sent between Asterisk and a phone that supports BLF (like the Snom 300 or Yealink T26). Our setup includes an OpenSER 1.2 & Asterisk 1.4.17 in the same box. OpenSER performs all registration, authentication and NAT. Asterisk handles the media and the accounting. In a pure Asterisk environment a "hint" would be setup in the Asterisk extensions.conf file and the phone (UA) would SUBSCRIBE to that HINT. Once Asterisk has registered that UA to the HINT then it sends SIP-NOTIFY messages to the UA as the status of the channel changes (available, ringing, busy). Our current openser.cfg file makes no mention of either SUBSCRIBE or NOTIFY which is an obvious reason that my Asterisk installation never registers the UA to the HINT. Is anyone interested in getting paid to fix this for us (we're too stupid to do it ourselves) or to offer another solution for controlling BLF in this setup. Thanks, Mark

5 4

[Kamailio-Users] small typo in rewriteport example on Kamailio Wiki
by Andreas Heise 09 Mar '10

09 Mar '10

Hello, there is a small typo in rewriteport example on Kamailio Wiki should be rewriteport("5070"); instead of rewriteport(5070); http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:1.5.x#rewriteport_s… regards, Andreas

2 1

[Kamailio-Users] Kamailio (OpenSER) v3.0.1 Released
by Daniel-Constantin Mierla 08 Mar '10

08 Mar '10

Hello, the first patch release for 3.0 series is out as version 3.0.1. It includes the fixes to issues discovered since 3.0.0. Database structure and configuration file compatibility are preserved so the upgrade from 3.0.0 is straightforward. Links and more details are available at: http://www.kamailio.org/w/2010/03/kamailio-v3-0-1-released/ Cheers, Daniel -- Daniel-Constantin Mierla Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 * http://www.asipto.com/index.php/sip-router-masterclass/

2 3

[Kamailio-Users] [OT] BYE sip:SIMPLE&XCAP@ietf.org SIP/1.0
by Iñaki Baz Castillo 08 Mar '10

08 Mar '10

Hi, if somebody is bored and has 5-10 minutes of spare time I suggest to read the mail I've sent to sip-implementors maillist, full of hate and fury: https://lists.cs.columbia.edu/pipermail/sip-implementors/2010- March/024529.html Enjoy. -- Iñaki Baz Castillo <ibc(a)aliax.net>

3 3

[Serusers] ser numbers going up
by Sabatella, Michael 08 Mar '10

08 Mar '10

Hi all, Running ser 0.9.6. I notice these numbers going up and never going back down: I am a bit concerened with the red text. Is there any reason why that does not come down to 0. Do I need to restart the ser process once a month or something around that timing? So far I have not heard of any issues with user call setup but I just want to remain proactive. Serctl moni outputs the following: Server: Sip EXpress router (0.9.6 (i386/linux)) Now: Mon Mar 8 10:05:18 2010 Up Since: Fri Jan 8 11:24:17 2010 Up time: 5092861 [sec] Transaction Statistics Current: 1 (176 waiting) Total: 5624219 (0 local) Replied localy: 6049354 Completion status 6xx: 0, 5xx: 121, 4xx: 308504, 3xx: 0,2xx: 5316846 Stateless Server Statistics 200: 13145729 202: 0 2xx: 0 300: 0 301: 0 302: 0 3xx: 0 400: 42 401: 0 403: 0 404: 350766 407: 16536998 408: 0 483: 0 4xx: 2 500: 1 5xx: 0 6xx: 0 xxx: 0 failures: 72 Michael Sabatella IPC Systems Network Services Engineer Office: 1-201-253-2280 Cell: 1-908-380-5321 @ IPCGlobalNetworks.com<http://www.ipcglobalnetworks.com/> ________________________________ DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems.

1 0

[Kamailio-Users] Get all the values for dialogs with a specific profile
by Iñaki Baz Castillo 08 Mar '10

08 Mar '10

Hi, by running "kamctl fifo profile_get_size togw" I can see the number of dialog tagged as "togw". Also if I run "kamctl fifo profile_get_size togw 999888777" I can see the number of dialogs tagged as "togw" with value "999888777". Is there any way to display all current values for dialogs with a specific profile/tag (i.e. "togw")? The idea is building a simple script to display the current number of calls per user (having that the value applied to dialog profiles means the calling user). Thanks for any suggestion. -- Iñaki Baz Castillo <ibc(a)aliax.net>

2 3

[Kamailio-Users] new website look
by Daniel-Constantin Mierla 08 Mar '10

08 Mar '10

Hello, http://www.kamailio.org has a new look! The former site was built with a cms system that discontinued the development, providing no longer updates for newer technologies and nicer design. We hope the new design helps to locate project resources easier and makes site navigation more straightforward via comprehensive list of links in the right sidebar. Credits go to Elio Rojano for the logo artwork and to developers of GPL Wordpress theme Cordobo Green Park which was used as start for the new design. If you are skilled in web design and can build a more personalized look on top of wordpress, please contact us. Cheers, Daniel PS. Do not forget, if you are tomorrow in London, UK, consider attending Present and Future of SIP Routing to get latest update about the project: http://www.kamailio.org/w/present-and-future-of-sip-routing-2010-london/ -- Daniel-Constantin Mierla Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 * http://www.asipto.com/index.php/sip-router-masterclass/

1 0

[Kamailio-Users] Dispatcher ds_list results in flag=P
by Geoffrey Mina 08 Mar '10

08 Mar '10

Hello, I have a weird issue with Dispatcher module. When I do a ds_list I get some of my destinations returned with flag=P. It appears that when they are in this state, they are not included in the list of destinations to send traffic to. I have tried restarting Kamailio, and these certain servers always return to flag=P. I have confirmed the servers are up and running fine. They are communicating without issue at the SIP and network level. Any idea what could cause this? Thanks,

3 9

Re: [Kamailio-Users] Users Digest, Vol 57, Issue 85
by Zhe 07 Mar '10

07 Mar '10

Help. Please remove me from this mail list. Thanks 在2010-02-27 19:00:01，users-request@lists.kamailio.org 写道： >Send Users mailing list submissions to > users(a)lists.kamailio.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >or, via email, send a message with subject or body 'help' to > users-request(a)lists.kamailio.org > >You can reach the person managing the list at > users-owner(a)lists.kamailio.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Users digest..." > > >Today's Topics: > > 1. remove parameter (Elgar Onel) > 2. Exotic case (but real) in which RtpProxy doesn't work > (I?aki Baz Castillo) > 3. Re: Exotic case (but real) in which RtpProxy doesn't work > (Daniel-Constantin Mierla) > 4. Re: Exotic case (but real) in which RtpProxy doesn't work > (I?aki Baz Castillo) > 5. Re: Exotic case (but real) in which RtpProxy doesn't work > (Daniel-Constantin Mierla) > 6. Re: Exotic case (but real) in which RtpProxy doesn't work > (I?aki Baz Castillo) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Fri, 26 Feb 2010 03:00:25 -0800 (PST) >From: Elgar Onel <elgaronel(a)yahoo.com> >Subject: [Kamailio-Users] remove parameter >To: users(a)lists.kamailio.org >Message-ID: <444271.31134.qm(a)web114207.mail.gq1.yahoo.com> >Content-Type: text/plain; charset="us-ascii" > >Dear friends, > >how to remove parameters from INVITE sip address? > >tia, e. > > > > >

2 1

[Kamailio-Users] 3.0 Modules
by dotnetdub 07 Mar '10

07 Mar '10

Hi List, I see two modules in particular that I could really do with running on 1.5.3 - I have started testing 3.0 but will not put into production just yet. Call control and topoh Would it be possible to backport these to 1.53 ? Would there be much to it.?. Call Control in particular is something that is very useful for us. We will eventually move to 3.0 of course as it is amazing product with lots of really nice new features just been burned badly before by moving to something so new. TIA. Stephen.

2 1

[Kamailio-Users] 10 years sip express router (ser)
by Daniel-Constantin Mierla 05 Mar '10

05 Mar '10

Hello, yesterday at CeBIT I've run into Fraunhofer booth and a banner attracted my attention, photo at: http://www.asipto.com/gallery/v/cebit2010/P3030721.JPG.html?g2_imageViewsIn… According to the middle right bubble, 2000 was the first year FhG presented SER at CeBIT. Given that, means the project should celebrate (at least) 10 years these days?!? I was among FhG staffers at CeBIT 2002, presenting latest SER at that time. According to CVS repository on BerliOS, files such as Makefile and main.c are dated 2001. Officially, SER was GPL-ed and open sourced in 2002 (year when ser project was registered to berlios.de software forge). Andrei, more insights from non-open-source era? I got into the project in January 2002, would be interesting to trace the birthday... Cheers, Daniel

2 1

[Kamailio-Users] local 408 from fr_timer and fr_inv_timer
by Robert McGilvray 04 Mar '10

04 Mar '10

I'm looking for a way to distinquish between locally generated 408s triggered by the timers. My problem is that I'm using gateway failover in a failure route and on 408s it would retry phones multiple times if they didn't answer (no voicemail etc) - so fr_inv_timer was triggered after receiving a provisional reply. I need to failover in case a gateway doesn't respond with provisional (it's set at 5 seconds currently). Will this work, is there a cleaner solution? I haven't had the oppurtunity to test it so I may have some syntax errors. onreply_route { if (t_check_status("1[0-9][0-9]")) { xlog("L_NOTICE", "KAM_HOST: ($ci) $pr $mi route[$rm][0] $fu TO $ru -> Provisional Response --> $T_reply_code\n"); setflag(FLAG_PR_RECEIVED); } } failure_route[ROUTE_DP_FAILURE] { if (t_local_replied("last") && t_check_status("408") && isflagset(FLAG_PR_RECEIVED)) { xlog("L_INFO", "KAM_HOST: ($ci) $pr $mi route[$rm][0] $fu TO $ru -> Local 408 after provisional response, giving up\n"); exit; } } Thanks! Bob -------------------------------------------------------------------------- This email with all information contained herein or attached hereto may contain confidential and/or privileged information intended for the addressee(s) only. If you have received this email in error, please contact the sender and immediately delete this email in its entirety and any attachments thereto.

2 3

[Kamailio-Users] Present and Future of SIP Routing 2010 London
by Daniel-Constantin Mierla 04 Mar '10

04 Mar '10

Hello, I am pleased to announce a dedicated event in London, Tuesday, March 9 afternoon, where to present the version 3.0 and latest developments in Kamailio and SIP Router projects. The event includes as well presentations from various players in the VoIP and SIP market, more details at: http://www.kamailio.org/mos/view/Present-and-Future-of-SIP-Routing-2010-Lon… It is a free event, the number of seats is limited, room being available courtesy of Sun Microsystems (address 55 King William St, London EC4), therefore the first come first serve policy is applied. You can also enroll for a presentation, just send a short description about the topic in the registration email. Hope to see many of you in London next week, Daniel -- Daniel-Constantin Mierla Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 * http://www.asipto.com/index.php/sip-router-masterclass/

1 0

[Serusers] Is this a SER Problem?
by Samson Luk 03 Mar '10

03 Mar '10

I use SPA3102 with a iptel.org VoIP a/c, whenever my Firewall external IP changed (SPA3102's WAN port only connected to the internal LAN with a static IP, router function not used) the iptel.org VoIP a/c will report registration failed. I have to remove the proxy domain field and re-insert it then reboot to fix the problem, just wonder if this is a problem on the SER side or on the SPA side. I am sorry if this is not a correct appropriate place to ask such a question.

1 0

Re: [Kamailio-Users] Kamailio and SIP <-> XMPP gateway
by Daniel-Constantin Mierla 03 Mar '10

03 Mar '10

On 03/02/2010 11:25 AM, Even André Fiskvik wrote: > Thanks for the answers Daniel. > > On 1. mars 2010, at 12.23, Daniel-Constantin Mierla wrote: > > >> Hello, >> >> On 02/28/2010 06:43 PM, Even André Fiskvik wrote: >> >>> Reading through various earlier discussion though, I've found an issue that I wonder wether has been solved or not. >>> In some mailing-lists I saw that only text/plain MESSAGEs was supported through the xmpp gateway, is this still true? >>> >>> >> yes and 'no' :-). Yes because nothing was done in this respect to the module itself. 'No' because now (kamailio 3.0) you can use transformations to get content of xml documents and if the body is xhtml. >> > That's good to know. > > >>> If that's the case, is there any way to get CounterPath eyeBeam/Bria to work in the decribed scenario? >>> As to my knowledge it can only send text/html ? >>> >>> >> You can build a new message with uac module or update the existing SIP message (content type, body), do msg_apply_changes(): >> http://kamailio.org/docs/modules/3.0.x/modules_k/textops.html#id2513318 >> >> and they use xmpp functions. >> > I did a "quick" hack to support relying the MESSAGE by just setting the content-type to text/plain for now to do some testing. > The error about unsupported content-type thus went away. > > >> You can use ngrep to sniff the network to see connection between kamailio (openser) and xmpp server as well as run kamailio in debug mode in order to get more verbose log messages for each operation. >> > I've tried sniffing traffic on the server, and it doesn't seem like kamailio tries to connect to the XMPP server at all :/ > Any clues what might be causing this? Did you run in debug mode? Can you post the log messages? > I've attached my kamailio config-file as well if anyone would take You sent the email only to me. Did you intend it for mailing list? I recommend to keep sending to mailing list apart of messages with private data. In this way many can reply and other can learn from discussion. > a look at it (the main config is in xmpp.cfg) and also a diagram showing how the components are realated to each other. > I will try to look over configs when I get some time -- because of a trip ahead I am pretty constrained today. Cheers, Daniel -- Daniel-Constantin Mierla Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 * http://www.asipto.com/index.php/sip-router-masterclass/

3 3

[Kamailio-Users] preparing for kamailio 3.0.1
by Daniel-Constantin Mierla 03 Mar '10

03 Mar '10

Hello, I think it is time to prepare for first minor release (3.0.1) in 3.0 series. We are approaching two months since kamailio 3.0.0, period within several issues were reported and fixed. Please report anything you are aware is not currently working in 3.0 to sr-dev(a)lists.sip-router.org or bug tracker: http://sip-router.org/tracker/ As for date, end of this week or beginning of next week would be a good time? Other opinions? Cheers, Daniel -- Daniel-Constantin Mierla Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 * http://www.asipto.com/index.php/sip-router-masterclass/

2 3

[Serusers] Need a way to substitute SIP Response Code 504 for something else
by Frank Durda IV 03 Mar '10

03 Mar '10

There is a commercial switch vendor who has recently decided to make two changes that combined are quite evil: 1, They decided to devivate from RFC 3398 and when a given call INVITE timer expire (any of the SS7 ones, plus the SIP ones, including any limit specified in the INVITE itself), instead of translating the ISUP Release Cause 102 into a SIP Response Code of 504 (Gateway Timeout), they send out a 503 (Service Unavailable) instead. (503 is commonly used in low-cost carriers and the commercial equipment they use to trigger a route-advance, where the call doesn't end but is relaunched via another slightly more expensive route/carrier who perhaps can get the call to the destination. Some of these low-cost outfits may retry the same call with five or six carriers before reluctantly sending to the local access tandem which is usually the most expensive choice, but almost certain to work. This probably isn't what the inventors of the 503 code had in mind, but that is how it is used. A minority use 404 the same way.) 2. The same vendor implemented an automatic "Address Reach" testing mechanism for outbound calls. This thing means that when sending a call to a distant switch, if a single or small number of calls are returned from that distant switch with a SIP Response Code of 504 from the destination, the sending switch will take that destination switch completely out of route ("blacklist") and not send any calls at all to that destination until the blacklist is manually reset. So a result that applies to one call is fatal to all subsequent calls. This also means that if you sent the INVITE Expires timer to a value less than the number of seconds the calling party is willing to let the called number ring (called party doesn't have voice mail or it doesn't pick up for several rings), you trigger a 504 and bingo, you have killed the route between those two switches. So your own choices for how long to wait on ring-back for a call dictate how quickly it could kill the entire route for that call. Now, the two changes taken together are also somewhat convienent because this equipment maker just happened to make it impossible for their own equipment to ever return a 504 and do can never trip off their own booby-trap. So in a way what these two changes effectively create a not-our-hardware-detector, triggering route failures only when in contact with RFC-compliant equipment made by somebody else. I think that behavior is anti-competitive, and probably illegal in quite a few countries (notably the EU), but that is what exists at the moment. This creation started getting deployed in the past few months. So, to get around this nonsense, I need a way in SER to detect that a 504 has come in and change it to something else before sending it on. I won't quibble about the "proxies can't forward a 503", so I won't try that. I would like to turn the 504 into a 404, which is better than having route get pulled all over the place. Now, the last time (a year or so ago) I asked about trying to change a SIP Response Code in SER, the suggested ser.cfg "fix" created all sorts of strange warnings in the logs about timers expiring and I was told to not worry about that. Well, it seemed to cause a lot more problems than just warnings like memory leaks or cores caused by something, so I ended up having to hard-code the translation I wanted into the SER source code and not use rules in ser.cfg to do this. I'm writing now to (A) alert people about what this major brand switch maker is doing with regard to 504s so you will recognize it if you encounter it, but also (B) to see if maybe has a more elegant way to change SIP Responses via the ser.cfg file has emerged. The obvious things like subst subst_uri don't appear to work, obviously busily editing the non-existent INVITE method message and ignoring the reply message. Using a reply/drop combination to generate a new reply and kill the real one doesn't seem to work either. As I recall it ends up sending the response specified in the reply, and then passing the original response as well. "drop" apparently doesn't kill it completely and I suspect reply is really meant to be used only during handling of the method messages, and not the response messages. Suggestions appreciated.

2 2

[Kamailio-Users] kam 1.5/asterisk 1.6 hints/blf?
by Robert McGilvray 02 Mar '10

02 Mar '10

Please excuse the noob questions, I'm not very familiar with presence. Users are registered to kamailio, authenticated against radius with LDAP backend. I'd like to setup some queues on asterisk for helpdesk call center but in order to do it correctly asterisk needs the device state (ringing, in use etc). I assume I'll need to use realtime ldap and setup device entries for all my phones, then use hints on the extensions as if they were local. If I understand correctly this will make asterisk subscribe to kamailio (I will use kams IP in host field), kam then has the responsibility of handling the subscribe/publish/notify stuff. What needs to be done on the kam side? Thanks! Bob -------------------------------------------------------------------------- This email with all information contained herein or attached hereto may contain confidential and/or privileged information intended for the addressee(s) only. If you have received this email in error, please contact the sender and immediately delete this email in its entirety and any attachments thereto.

3 4

[Kamailio-Users] Kamailio (1.5 rev5834) and/or rtpproxy gets frozen
by Iñaki Baz Castillo 01 Mar '10

01 Mar '10

Hi, I'm experimenting an annoying issue in a Debian Lenny 32 bits under a DELL 850 (2 cores). Same occured before with Debian Etch 32 and 64 bits in other host (also DELL 850). Kamailio (1.5 rev 5834) behaves as a load balancer in front of 2 PSTN gateways. There are ~200 calls and for all of them rtpproxy is applied. Sometimes, with no reason (not just in the moments of highest traffic) kamailio gets totally frozen, this is, it doesn't reply to SIP messages, neither relays them. Then Kamailio cannot be killed (just with -9). Sometimes it occurs when performing a fifo command (i.e. "kamctl fifo address_reload"). After killing it, kamailio cannot be started again. It starts and logs the usual logs (to syslog) but after "rtp proxy <unix:/var/run/rtpproxy.sock> found, support for it enabled" there is no more logs. Then if I do a "ps aux | grep kamailio" I just see a single process, it's like the children fail when connecting to rtpproxy and die but the master process doesn't realize of it and remains alive showing no error at all. So I suspect from rtpproxy as even when kamailio was killed rtpproxy process consumes lot of CPU. I'll try with rtpproxy-1.2.1 (the latest stable version) as before I was using a old "truk" version (unfortunatelly I've no idea about how to know the CVS revision of a CVS working directory...). Anyhow I also suspect that the problem could be in the server itself, as sometimes the above problem occurs when reloading iptables and so on, very very strange, no a definitive cause or reason, very annoying. So nothing is clear for me. But I know that the problem occurs: - In two DELL 850, one with 32 and the other with 64 bits. - In both Debian Leeny and Etch. - With kamailio 1.5 rev 5834. - With rtpproxy rev XXX (how to get the last modification date in a CVS working dirrectory?) So, the fact is that I'm completely lost, no idea of what is happening. Any suggestion? Thanks a lot. -- Iñaki Baz Castillo <ibc(a)aliax.net>

2 12

[Kamailio-Users] Project Update, London Meeting, March 9
by Daniel-Constantin Mierla 01 Mar '10

01 Mar '10

Hello, Tuesday, March 9, I am going to be in London and plan to organize a social networking event for folks around SIP/VoIP, Kamailio (OpenSER) & SIP Router. One is going to be the usual evening dinner/pub meeting, see pics from some past events: http://www.asipto.com/gallery/v/social_meeting_barcelona2008/ http://www.asipto.com/gallery/v/FOSDEM2009/ I addition, if there are people interested, I would like to have a session in the afternoon (2-3 hours) to give an update about Kamailio (OpenSER) 3.0, present and future development of SIP Router. Time is rather short, but I encourage attendees to prepare short presentations as well, about their products and services, to have more information exchanged there. Let me know if you wish to attend such event in order to find a proper place to host it (drop me an email). Participation is free for everybody, at the dinner, the classic rule, everyone is going to pay for himself/herself. Looking forward to meeting many of you in London. Cheers, Daniel -- Daniel-Constantin Mierla Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 * http://www.asipto.com/index.php/sip-router-masterclass/

1 0

[Kamailio-Users] Kamailio and SIP <-> XMPP gateway
by Even André Fiskvik 01 Mar '10

01 Mar '10

Hi. I've just started looking at kamailio, and I'm experimenting a bit with configuring a SIP <-> XMPP gateway with it using the pua_xmpp module. The configuration part hasn't beed straight-forward, but I think I'm starting to get somewhere. Both kamailio and XMPP/Jabber are new technologies for me serverside, so I don't have a great deal of experience with either. In short, what I'm trying to accomplish at this stage is: - Have CounterPath eyeBeam/Bria to register to my kamailio server - Have Aastra 6755i register to my kamailio server - Connect an XMPP client to my XMPP server - The CounterPath eyeBeam/Bria, Aastra and the XMPP client should all be able to see each others presence - The CounterPath eyeBeam/Bria should be able to IM other eyeBeams/Brias - The CounterPath eyeBeam/bria should be able to IM the XMPP clients and the other way around Reading through various earlier discussion though, I've found an issue that I wonder wether has been solved or not. In some mailing-lists I saw that only text/plain MESSAGEs was supported through the xmpp gateway, is this still true? If that's the case, is there any way to get CounterPath eyeBeam/Bria to work in the decribed scenario? As to my knowledge it can only send text/html ? Could anyone with a good knowledge of Kamailio and the various modules pua_xmpp, xmpp, pua, pua_bla comment on this kind of setup is at all possible with kamailio and it's current state? Is there any way I can verify that opensips connects to the XMPP server correctly? I tried connecting FreeSWITCH to my XMPP server (Openfire) in component mode, and it would show up connected in Openfire's administration GUI, however I can not see the same when I try to configure kamailio. If anyone has experience with this setup and have another XMPP server they have tested it with, I would also want to try to swap Openfire with that (given they also have some guidance on XMPP server configuration). Best regards, Even André Fiskvik

2 1

[Kamailio-Users] remove parameter
by Elgar Onel 26 Feb '10

26 Feb '10

Dear friends, how to remove parameters from INVITE sip address? tia, e.

1 0

[Kamailio-Users] ratelimit enhancements
by Daniel-Constantin Mierla 26 Feb '10

26 Feb '10

Hi Marius, since you did some updates to this module, I am opening for debate some needed enhancements I did during 3.0 testing phase and want to get opinions how to get in the code repo. Practically is a new module I named for now ratelimit2 and my last idea is to get it named pipelimit in the trunk. The reason for a new module are some major changes. The module uses the same algorithm but its core is overhaul. - definitions of pipes are loaded from database - there can be unlimited number of pipes - pipes are identified by string names - should be possible to reload pipes at runtime (iirc, not yet in) - new pipes can be added at runtime - functions accept variables to identify the pipe Since I never used queues from this module and haven't spent time to understand the concept behind, this functionality is completely missing. The old module might be good to keep in place, probably many people are using it in this form. So, proposals? What is the way to go on? Common code (algorithms) can be made lib at some point. Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

6 14

[Kamailio-Users] tracking new features
by Daniel-Constantin Mierla 25 Feb '10

25 Feb '10

Hello, a reminder for developers to write a short note for each new feature either to NEWS file in source tree or to wiki page: http://sip-router.org/wiki/features/new-in-devel Makes life much easier when the next major release is going to happen and help people to spot quickly what new features are already available in devel branch, hopefully attracting some of them to go for it and test. Now the wiki page is updated with most of NEWS content for 3.1. Thanks, Daniel -- Daniel-Constantin Mierla Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 * http://www.asipto.com/index.php/sip-router-masterclass/

1 0

[Kamailio-Users] CeBIT 2010
by Daniel-Constantin Mierla 25 Feb '10

25 Feb '10

Hello, I am going to visit CeBIT 2010 in Hannover next week. Drop me an email if you are around and want to meet and chat about Kamailio, SIP Router projects, etc. Cheers, Daniel -- Daniel-Constantin Mierla Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 * http://www.asipto.com/index.php/sip-router-masterclass/

1 0

[Kamailio-Users] Storing nonscalar types (lists)
by Alex Balashov 24 Feb '10

24 Feb '10

Are AVP arrays still the only way to create a list of scalars as of K 3.0.0? Or are there other, more graceful ways to accommodate this need now? AVPs are a very useful feature, though the syntax is not documented in 'avpops' or the cookbook except rather incidentally: $var(i) = 0; while(is_avp_set("$(avp(s:somename)[$var(i)])")) { xlog("L_INFO", "Value at index $var(i): $(avp(s:somename)][$var(i)])\n"); $var(i) = $var(i) + 1; } Is there a better way to handle this now, perhaps via some features imported from SER? Script variables ($var(...)) do not support subscripts judging by the cookbook; do they? Are there other options I am unaware of? Thanks, -- Alex Balashov - Principal Evariste Systems LLC Tel : +1 678-954-0670 Direct : +1 678-954-0671 Web : http://www.evaristesys.com/

3 9

[Kamailio-Users] Logging of db_extra parameters + serial forking
by Alex Balashov 24 Feb '10

24 Feb '10

Here is a problem I am sure is not new (1.5.x): modparam("acc", "db_extra", "gateway_id=$avp(s:gateway_id)") route { ... $avp(s:gateway_id) = 13; $ru = "some.gw1"; t_on_failure("1"); if(!t_relay()) sl_reply_error(); } # Serial forking rollover route failure_route[1] { if(t_was_cancelled()) exit; $avp(s:gateway_id) = 14; $rd = "some.gw2"; append_branch(); t_relay(); } The problem is, when serial forking happens, the CDR rows in 'acc' still show a value of 13 for 'gateway_id'. This is obviously because the value is sampled at the time of the initial stateful relay processing and is not updated afterward. Any easy/elegant fix? I can think of several fixes that don't involve using 'acc', obviously, but I'd rather avoid that... -- Alex Balashov - Principal Evariste Systems LLC Tel : +1 678-954-0670 Direct : +1 678-954-0671 Web : http://www.evaristesys.com/

1 1

Re: [SR-Users] function calling in the config script with $var() as attribute(s)
by Klaus Feichtinger 24 Feb '10

24 Feb '10

Klaus, Alex, you're right. I've seen Klaus's suggestion only after writing my email message. This is the best solution and solves my problem! regards, Klaus > > > Am 24.02.2010 15:41, schrieb Klaus Feichtinger: > > Hello SR-users and -developers, > > > > I have the question if parameters for a function in the config script > > (e.g. "t_relay(host, port)") in general can be set with a variable > > ($var(xy)). Because of having a set of SIP servers / gateways > distributed > > over a wide area and therefore keeping the configuration as simple as > > possible, I would like to define a custom variable, assign it to a $var > > and use this variable as attribute for a relay function. In this case > the > > variable would represent a string of an IP-address (e.g. "10.1.1.55"). > > When this would work I only have to adapt the custom variables on top of > > each config script and could let the rest "as it is". > > > > > > First practical tests have shown, that the functions are NOT happy with > these "attributes". It can be used without any problems for if-else- > > statements, but I fear not for functions.... > > > > The practical scenario looks like: > > > > tc.ip11 = "10.16.65.101" desc ""; > > [...] > > route { > > $var(test) = $sel(cfg_get.tc.ip11); > > [...] > > if (!t_relay($var(test), "5061")) > > A workaround for t_relay: > > $du = "sip:"+$var(test)+":5061"; > t_relay(); > > > klaus > > > > [...] > > } > > > > This configuration resulted in following error messages: > > > > <core> [cfg.y:3326]: parse error in config file > /usr/local/etc/kamailio/kamailio.cfg, line 413, column 18-35: syntax error > > <core> [cfg.y:3326]: parse error in config file > /usr/local/etc/kamailio/kamailio.cfg, line 413, column 18-35: call params error#012 > > <core> [cfg.y:3326]: parse error in config file > /usr/local/etc/kamailio/kamailio.cfg, line 413, column 18-35: call params error#012 > > <core> [cfg.y:3326]: parse error in config file > /usr/local/etc/kamailio/kamailio.cfg, line 413, column 38-41: Function parameter with integer > value not allowed#012 > > > > > > Please, could anybody clarify if this should work or not? If not - is > any > > alternative possibility available for "automating" function attributes > > instead of re-writing each function using the same string attribute? > > > > Thanks in advance, > > > > Klaus > > -- GMX DSL: Internet, Telefon und Entertainment für nur 19,99 EUR/mtl.! http://portal.gmx.net/de/go/dsl02

1 0

function calling in the config script with $var() as attribute(s)
by Klaus Feichtinger 24 Feb '10

24 Feb '10

Hello SR-users and -developers, I have the question if parameters for a function in the config script (e.g. "t_relay(host, port)") in general can be set with a variable ($var(xy)). Because of having a set of SIP servers / gateways distributed over a wide area and therefore keeping the configuration as simple as possible, I would like to define a custom variable, assign it to a $var and use this variable as attribute for a relay function. In this case the variable would represent a string of an IP-address (e.g. "10.1.1.55"). When this would work I only have to adapt the custom variables on top of each config script and could let the rest "as it is". First practical tests have shown, that the functions are NOT happy with these "attributes". It can be used without any problems for if-else- statements, but I fear not for functions.... The practical scenario looks like: tc.ip11 = "10.16.65.101" desc ""; [...] route { $var(test) = $sel(cfg_get.tc.ip11); [...] if (!t_relay($var(test), "5061")) [...] } This configuration resulted in following error messages: <core> [cfg.y:3326]: parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 413, column 18-35: syntax error <core> [cfg.y:3326]: parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 413, column 18-35: call params error#012 <core> [cfg.y:3326]: parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 413, column 18-35: call params error#012 <core> [cfg.y:3326]: parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 413, column 38-41: Function parameter with integer value not allowed#012 Please, could anybody clarify if this should work or not? If not - is any alternative possibility available for "automating" function attributes instead of re-writing each function using the same string attribute? Thanks in advance, Klaus -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/chbrowser

3 4

[Kamailio-Users] Kamailio 3.0.0: configuration request regarding VARIABLES usage (custom variables + $var(x))
by Klaus Feichtinger 24 Feb '10

24 Feb '10

Hello Kamailio-3 users, I have two questions regarding usage of variables within the config file (as published in the NEW FEATURES of Kamailio 3.0.0). The reason why I want to use variables instead of standard configuration lines is the maintainability of my SIP servers. I have a group of about 20 sip servers distributed over a wide area. Especially routing rules might change during operation of the servers and must be adapted on all servers. Therefore I want to use variables, defined at the beginning of each config file. Within the config file / the different routing blocks I want to reference to these variables. That would be much easier for automatic config script adaptation with a linux script (e.g.) than parsing the whole config file for special text phrases. QUESTION 1: ========== Is it impossible using a variable for requesting a SRC_IP address? With my current configuration I always see an entry in the SYSLOG that looks as follows: "<core> [route.c:1531]: BUG: comp_ip: invalid type for src_ip or dst_ip (20)" The configuration lines look like: $var(lst_gwIpRange) = "10.16.48.6[0-2]"; [...] if (src_ip=~$var(lst_gwIpRange)) { [...] } Is maybe a transformation missing/necessary to avoid the error message (which causes a malfunction)? Can anybody give me a hint? QUESTION 2: ========== The second problem I found is, that the config variables can be configured within a route block only and not - as expected - e.g. at the top of the config file (in the same way as the custom variables). I can't use the custom variables as they are, because I will use more complex variables, which are a mixture of up to three custom variables. These "complex" variables will be used in more than one routing block. Therefore I have to define these variables in every routing block...... Is an alternative (easier) solution with a single definition available, too? An example of my problem is as follows: # custom variables defined on top of the kamailio.cfg file tst.loc_ipaddr = "10.10.1.1" desc "IP addr of the local SIP Server" tst.loc_prefix = "11" desc "prefix of this SRV" tst.distRu1 = "51[0-9].*" desc "variable representing ID1" # the final variable should look like "sip:1151[0-9].*@10.10.1.1" # and is used in 3 routing blocks route[] $var(test) = "sip:" + $sel(cfg_get.tst.loc_prefix) + $sel(cfg_get.tst.distRu1) + "@" + $sel(cfg_get.tst.loc_ipaddr); [...] route[TEST1] $var(test) = "sip:" + $sel(cfg_get.tst.loc_prefix) + $sel(cfg_get.tst.distRu1) + "@" + $sel(cfg_get.tst.loc_ipaddr); [...] route[TEST2] $var(test) = "sip:" + $sel(cfg_get.tst.loc_prefix) + $sel(cfg_get.tst.distRu1) + "@" + $sel(cfg_get.tst.loc_ipaddr); [...] Thanks in advance for any hints! Regards, Klaus Feichtinger -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser

4 7

[Kamailio-Users] 3.0.0 and snmpstats
by Kelvin Chua 24 Feb '10

24 Feb '10

hi guys, anybody here tried using snmpstats with 3.0.0? i keep on getting "No such Object" already verified that kamailio is talking to agentx master. net-snmp version 5.3.3 compiled from source also disabled openssl and md5 in net-snmp to prevent any undefined symbols been reading the mailing lists and so far nothing helped. seems like only a couple of guys are using this module? Kelvin Chua

2 4

[Kamailio-Users] Freeing sqlops results
by Alex Balashov 23 Feb '10

23 Feb '10

Should sql_result_free() always be called, no matter what the circumstance, in order to discharge memory allocated to query result sets and/or metadata? Or is it not necessary in certain situations, for example when script is broken via 'exit', i.e. sql_query("db", "SELECT ...", "res"); if(! $dbr(res=>rows)) { # Is it necessary to call sql_result_free() here? sl_send_reply("404", "Not Found"); exit; } Are results implicitly freed at the end of route script execution anyway? Are they tied to transaction persistence in any way? Thanks, -- Alex Balashov - Principal Evariste Systems LLC Tel : +1 678-954-0670 Direct : +1 678-954-0671 Web : http://www.evaristesys.com/

3 3

[Kamailio-Users] Forward calls from Asterisk to SIP provider via Kamailio for termination
by Slot Zero 23 Feb '10

23 Feb '10

Hello, I am a Kamailio noob :). I am trying to get Asterisk to forward calls to my SIP provider via Kamailio. The same machine is running Kamailio and Asterisk. I do not want to consume credentials as they have to be passed on all the way to my SIP provider. There is no NAT of any sorts. SIP Phone/Users connect to Asterisk.I do not need to authenticate when forwarding call from Asterisk to Kamailio as they are both running on the same server but I do need to make sure that Kamailio dials and forwards 011+number to be sent from local host port 5062(Asterisk listener) to SIP provider only. I have 6 Public IP addresses mapped on the server. I want to use the force_send_socket to allow me to change source IP of SIP requests when being sent to the SIP provider on the basis of credentials username in the request. I have pasted my config below. Please tell me what am I doing wrong here. In the kamctlrc file i have SIP_DOMAIN=localhost Thank you #------CONFIG BEGINS------------------ mpath="/lib/kamailio/modules_k/" debug=3 fork=yes children=4 auto_aliases=no alias=localhost alias=192.168.10.1 alias=192.168.10.2 alias=192.168.10.3 alias=192.168.10.4 alias=192.168.10.5 alias=192.168.10.6 disable_tcp=yes loadmodule "sl.so" loadmodule "rr.so" loadmodule "maxfwd.so" loadmodule "/lib/kamailio/modules/tm.so" loadmodule "textops.so" modparam("rr", "enable_full_lr", 1) route { # Sanity Check # ------------ # filter too old messages if (!mf_process_maxfwd_header("10")) { log("LOG: Too many hops\n"); sl_send_reply("483","Too Many Hops"); break; }; if(msg:len>2048) { sl_send_reply("413", "message too large to be forwarded over UDP without fragmentation"); exit; }; # Record Route and NAT Preset # -------------------- if (method != "REGISTER") { record_route(); }; # Loose Route # ----------- if (loose_route()) { route(1); return; }; # Call Type Processing # -------------------- if (uri != myself) { route(1); return; }; if (uri == myself) { if (method == "BYE") { route(4); return; } else if (method == "CANCEL") { route(4); return; } else if (method == "INVITE") { route(3); return; } else if (method == "NOTIFY") { sl_send_reply("200", "Understood"); return; } else if (method == "OPTIONS") { sl_send_reply("200", "Got it"); return; } }; route(1); } # Default Message Handling # ----------------------- route[1] { t_on_reply("1"); if (!t_relay()) { sl_reply_error(); }; } # INVITE Message Handling # ---------------------------------- # ---------------------------------- route[3] { if (uri =~ "^sip:011[0-9]@*") { rewritehostport("sip.voipprovider.com:5060"); if (search("^(Contact|m): .*user01*(a)(127\.0\.0\.1|localhost)")) { force_send_socket(192.168.0.2:5060); }; route(1); return; }; } # CANCEL and BYE Message Handling # ---------------------------------- route[4] { route(1); }

3 8

[Kamailio-Users] Rtpproxy hook
by Vikram Ragukumar 22 Feb '10

22 Feb '10

Hello, I am trying to encrypt/decrypt all packets belonging to an RTP stream. I am using Kamailio v1.5 with rtpproxy, where Kamailio forces the rtpstream through rtpproxy. Does rtpproxy provide a hook so that i can gain access to each RTP packet to perform encryption/decryption ? I do not want to end up having a patch for rtpproxy that i need to update whenever there is a new release of rtpproxy. -- Thanks and Regards, Vikram Ragukumar.

2 1

[Kamailio-Users] Error in Registration with TLS on
by Hemanshu Patel 22 Feb '10

22 Feb '10

Dear friends, Since last few days i am working on Kamailio with TLS support. I had followed each and every steps in installation docs...created certificates as well. Then i started testing the server with TLS on using SIPP. First i didnt added any certificate to SIPP, and Registration wasnt happening... When i added a certificate and key to SIPP....it started working fine....i was been able to test Registrations Successfully. Then i started working with one open source soft phone supporting TLS named mumble. IT Supports. Now i hadnt added any certificate to Mumblem. In my settings of kamailio i have set clietn_verify = 0 and require_client_certificate = 0. So without certificate as well i should be able to Authenticate my self successfully. Instead it gives following error in kamailio log: Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:print_ip: tcpconn_new: new tcp connection to: 172.16.16.218 Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tcpconn_new: on port 58125, type 3 Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tls_tcpconn_init: entered: Creating a whole new ssl connection Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tls_tcpconn_init: looking up socket based TLS server domain [172.16.16.218:5091] Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tls_find_server_domain: socket based TLS server domain found Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tls_tcpconn_init: found socket based TLS server domain [172.16.16.218:5091] Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tls_tcpconn_init: Setting in ACCEPT mode (server) Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tcpconn_add: hashes: 929, 1 Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:handle_new_connect: new connection: 0x7fd6f4a58208 23 flags: 0002 Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:send2child: to tcp child 0 0(3296), 0x7fd6f4a58208 Feb 22 09:50:51 localhost ./sbin/kamailio[3296]: DBG:core:handle_io: received n=8 con=0x7fd6f4a58208, fd=18 Feb 22 09:50:51 localhost ./sbin/kamailio[3296]: DBG:core:io_watch_add: io_watch_add(0x73a0a0, 18, 2, 0x7fd6f4a58208), fd_no=1 Feb 22 09:50:51 localhost ./sbin/kamailio[3296]: DBG:core:tls_update_fd: New fd is 18 Feb 22 09:50:51 localhost ./sbin/kamailio[3296]: ERROR:core:tls_accept: SSL_accept failed: SSL_ERROR_SSL Feb 22 09:50:51 localhost ./sbin/kamailio[3296]: DBG:core:io_watch_del: io_watch_del (0x73a0a0, 18, -1, 0x10) fd_no=2 called Feb 22 09:50:51 localhost ./sbin/kamailio[3296]: DBG:core:release_tcpconn: releasing con 0x7fd6f4a58208, state -2, fd=18, id=1 Feb 22 09:50:51 localhost ./sbin/kamailio[3296]: DBG:core:release_tcpconn: extra_data 0x7fd6f4a683a0 Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:handle_tcp_child: reader response= 7fd6f4a58208, -2 from 0 Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tcpconn_destroy: destroying connection 0x7fd6f4a58208, flags 0002 Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tls_close: closing SSL connection Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tls_update_fd: New fd is 23 Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tls_shutdown: shutdown successful Feb 22 09:50:51 localhost ./sbin/kamailio[3300]: DBG:core:tls_tcpconn_clean: Cleanup function entered Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:print_ip: tcpconn_new: new tcp connection to: 172.16.16.218 Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tcpconn_new: on port 58126, type 3 Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tls_tcpconn_init: entered: Creating a whole new ssl connection Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tls_tcpconn_init: looking up socket based TLS server domain [172.16.16.218:5091] Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tls_find_server_domain: socket based TLS server domain found Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tls_tcpconn_init: found socket based TLS server domain [172.16.16.218:5091] Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tls_tcpconn_init: Setting in ACCEPT mode (server) Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tcpconn_add: hashes: 930, 2 Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:handle_new_connect: new connection: 0x7fd6f4a58208 23 flags: 0002 Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:send2child: to tcp child 0 0(3296), 0x7fd6f4a58208 Feb 22 09:51:01 localhost ./sbin/kamailio[3296]: DBG:core:handle_io: received n=8 con=0x7fd6f4a58208, fd=18 Feb 22 09:51:01 localhost ./sbin/kamailio[3296]: DBG:core:io_watch_add: io_watch_add(0x73a0a0, 18, 2, 0x7fd6f4a58208), fd_no=1 Feb 22 09:51:01 localhost ./sbin/kamailio[3296]: DBG:core:tls_update_fd: New fd is 18 Feb 22 09:51:01 localhost ./sbin/kamailio[3296]: ERROR:core:tls_accept: SSL_accept failed: SSL_ERROR_SSL Feb 22 09:51:01 localhost ./sbin/kamailio[3296]: DBG:core:io_watch_del: io_watch_del (0x73a0a0, 18, -1, 0x10) fd_no=2 called Feb 22 09:51:01 localhost ./sbin/kamailio[3296]: DBG:core:release_tcpconn: releasing con 0x7fd6f4a58208, state -2, fd=18, id=2 Feb 22 09:51:01 localhost ./sbin/kamailio[3296]: DBG:core:release_tcpconn: extra_data 0x7fd6f4a683a0 Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:handle_tcp_child: reader response= 7fd6f4a58208, -2 from 0 Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tcpconn_destroy: destroying connection 0x7fd6f4a58208, flags 0002 Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tls_close: closing SSL connection Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tls_update_fd: New fd is 23 Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tls_shutdown: shutdown successful Feb 22 09:51:01 localhost ./sbin/kamailio[3300]: DBG:core:tls_tcpconn_clean: Cleanup function entered And in Mumble soft phone log it gives me following Error: [9:50 AM] Welcome to Mumble. [9:50 AM] Server connection failed: Error during SSL handshake: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure. [9:51 AM] Reconnecting. [9:51 AM] Server connection failed: Error during SSL handshake: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure. [9:51 AM] Reconnecting. [9:51 AM] Server connection failed: Error during SSL handshake: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure. [9:51 AM] Reconnecting. [9:51 AM] Server connection failed: Error during SSL handshake: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure. Can any one suggest what could be the problem? My Server works great with SIPP with TLS....so i dont think theres any config related error and i have set client_require_certificate = 0 thats for sure.... In real life scenario, hard or soft phones wont have certificates...so they should be able to connect to server and authenticate/Authorize themselves if server has valid certificate.But its not happening. So i need help from experienced guys.... -- Regards, Hemanshu Patel M: 09601295238

2 2

[Kamailio-Users] acc
by Anders 22 Feb '10

22 Feb '10

Hi, Probably a simpel fix some...not for me ;-) I get this here below in the log when I try to start Kamailio on a new installation. I suspect something is wrong with the acc module. What I read elsewhere is that it needs to recompile... - could that be, and if so, how would I recompile only a module? Thanks!! //Anders Feb 19 07:52:12 vn1031 kamailio: ERROR:core:set_mod_param_regex: parameter <radius_config> not found in module <acc> Feb 19 07:52:12 vn1031 kamailio: CRITICAL:core:yyerror: parse error in config file, line 140, column 25-26: Can't set module parameter Feb 19 07:52:12 vn1031 kamailio: ERROR:core:set_mod_param_regex: parameter <radius_flag> not found in module <acc> Feb 19 07:52:12 vn1031 kamailio: CRITICAL:core:yyerror: parse error in config file, line 141, column 27-28: Can't set module parameter Feb 19 07:52:12 vn1031 kamailio: ERROR:core:set_mod_param_regex: parameter <radius_missed_flag> not found in module <acc> Feb 19 07:52:12 vn1031 kamailio: CRITICAL:core:yyerror: parse error in config file, line 142, column 20-21: Can't set module parameter Feb 19 07:52:12 vn1031 kamailio: ERROR:core:set_mod_param_regex: parameter <radius_extra> not found in module <acc> Feb 19 07:52:12 vn1031 kamailio: CRITICAL:core:yyerror: parse error in config file, line 157, column 2-3: Can't set module parameter Feb 19 07:52:12 vn1031 kamailio: ERROR:core:main: bad config file (4 errors)

2 1

[Kamailio-Users] Demerits of using normal Authentication insted of radius or diameter auth
by Hemanshu Patel 21 Feb '10

21 Feb '10

Hello guys..... Recent now i had started taking keen interest in kamailio. I was testing kamailio, and i had test it under two scenario. first of all let me tell u about my configuration. I am testing on normal Desktop pc, installed kamailio,mysql, radius everything on same pc. I am using MYSQL anyway for both sort of testing. When i test with radius authentication, means using radius_www_authorize at max i am getting around 500 cps for Registration, but when i use normal www_authorize i am getting around 2000 CPS.... whopping difference guys..... So, i was wondering what is merits and demerits of not using Radius based authentication. Is it insecure if i use normal Authentication? Its not in my knowledge that radius do encryption...so i dont think by using radius it provides more security. What is your opinions about it? -- Regards, Hemanshu Patel M: 09601295238

3 3

[Kamailio-Users] Username of P-Asserted-Identity header
by Marco Bungalski 19 Feb '10

19 Feb '10

Hi, all! Is there an easy possibility to get the Username of the P-Asserted-Identity header? When i use $ai i get for example "sip:+4942317769999@testdomain.de". I need only "+4942317769999" in a variable. I know for example that i can use $fU and get only the Username (and $fu gives me the whole From URI).... Cheers, Marco Marco Bungalski GmbH Traversale 5 27283 Verden Telefon: +49 4231 - 776 9999 Fax: +49 4231 - 776 9998 Mobil: +49 172 4204774 e-mail: Marco(a)Bungalski.de www.bungalski.de www.t-m-net.de Geschäftsführender Gesellschafter: Marco Bungalski Sitz der Gesellschaft: D-27283 Verden, AG Walsrode HRB 120586

3 3

[Kamailio-Users] CANCEL goes bananas!
by Anders 19 Feb '10

19 Feb '10

Ok, "bananas" might not be the right word, but it resembles what is happening ;-) When I get a CANCEL from my customer to Kamailio, it is not passed on to my vendor - this is with a specific customer using VoipSwitch. The result is that the phone called keeps ringing even though it's been (attempted) cancelled, and a sideeffect is that it goes nuts at the carrier side because it can send anymore and returns 480 or 486. Below is the dialog from the Session Progress to when the call is cancelled - and then it goes bananas. Any ideas? Thanks a lot! U 2010/02/12 14:40:25.435793 MyKamailioIP:5060 -> MyCustomerIP:5060 SIP/2.0 183 Session Progress. To: <sip:890912551184517324@MyKamailioIP>;tag=3474974816-620042. From: "69912390" <sip:001128650136@MyCustomerIP:5060>;tag=1202461012501320412156. Contact: <sip:84370551184517324@MyVendorIP:5060>. Call-ID: GWV0iI5c5vUSEUnPBz@MyCustomerIP. CSeq: 1 INVITE. Content-Type: application/sdp. Via: SIP/2.0/UDP MyCustomerIP:5060;rport=5060;received=MyCustomerIP;branch=z9hG4bk120246101250121320412156. Content-Length: 210. . v=0. o=prxams02 0 0 IN IP4 MyVendorIP. s=sip call. c=IN IP4 62.93.140.13. t=0 0. m=audio 42972 RTP/AVP 18 101. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. U 2010/02/12 14:40:30.625842 MyCustomerIP:5060 -> MyKamailioIP:5060 CANCEL sip:890912551184517324@MyKamailioIP SIP/2.0. CSeq: 1 CANCEL. Via: SIP/2.0/UDP MyCustomerIP:5060;branch=z9hG4bk120246101250121320412156. From: "69912390" <sip:001128650136@MyCustomerIP:5060>;tag=1202461012501320412156. Call-ID: GWV0iI5c5vUSEUnPBz@MyCustomerIP. To: <sip:890912551184517324@MyKamailioIP>;tag=3474974816-620042. Contact: <sip:MyCustomerIP:5060;transport=udp>. Content-Length: 0. . U 2010/02/12 14:41:25.496605 MyVendorIP:5060 -> MyKamailioIP:5060 SIP/2.0 480 Temporarily Unavailable. To: <sip:890912551184517324@MyKamailioIP>;tag=3474974816-620042. From: "69912390" <sip:001128650136@MyCustomerIP:5060>;tag=1202461012501320412156. Contact: <sip:84370551184517324@MyVendorIP:5060>. Call-ID: GWV0iI5c5vUSEUnPBz@MyCustomerIP. CSeq: 1 INVITE. Via: SIP/2.0/UDP MyKamailioIP;branch=z9hG4bKf18c.fa7b81d2.0. Via: SIP/2.0/UDP MyCustomerIP:5060;rport=5060;received=MyCustomerIP;branch=z9hG4bk120246101250121320412156. Content-Length: 0. . U 2010/02/12 14:41:25.496888 MyKamailioIP:5060 -> MyVendorIP:5060 ACK sip:84370551184517324@MyVendorIP:5060 SIP/2.0. Via: SIP/2.0/UDP MyKamailioIP;branch=z9hG4bKf18c.fa7b81d2.0. From: "69912390" <sip:001128650136@MyCustomerIP:5060>;tag=1202461012501320412156. Call-ID: GWV0iI5c5vUSEUnPBz@MyCustomerIP. To: <sip:890912551184517324@MyKamailioIP>;tag=3474974816-620042. CSeq: 1 ACK. Max-Forwards: 70. User-Agent: Kamailio. Content-Length: 0.

2 3

[Kamailio-Users] Testing of Kamailio TLS with Sipp TLS
by Hemanshu Patel 19 Feb '10

19 Feb '10

Hello friendsm, I am testing TLS feature of both kamailio and Sipp. I first downloaded kamailio 1.5.x TLS supported version, uncommented TLS=1 from Makefiel and then build the kamailio. first i test kamailio without TLS with sipp for registration and everything works file. Then i follow "http://www.kamailio.org/docs/tls-devel.html" and creates rootCA, user certificates and all configuration parameters to kamailio.cfg file Config paras are as below: /* uncomment the following lines to enable TLS support (default off) */ disable_tls = no listen = tls:172.16.16.218:5091 tls_verify_server = 1 tls_verify_client = 1 tls_require_client_certificate = 1 tls_method = TLSv1 tls_certificate = "/data/hemanshu/install/kam-tls/etc/kamailio/tls/user/user-cert.pem" tls_private_key = "/data/hemanshu/install/kam-tls/etc/kamailio/tls/user/user-privkey.pem" tls_ca_list = "/data/hemanshu/install/kam-tls/etc/kamailio/tls/user/user-calist.pem" and restart kamailio server It works and i can see via netstat on port 5091. but when i starts sipp it gives me following error. [hemanshu@localhost sipp.3.1]$ ./sipp -sf ./data/rauth.xml -inf ./data/user.csv -r 1 -m 1 -trace_err -trace_stat -nd -fd 1 -i 172.16.16.218 172.16.16.218:5091 -t l1 2010-02-18 13:51:40:244 1266481300.244432: FI_init_ssl_context: SSL_CTX_use_certificate_file failed. I know i have built sipp with TLS support, then i can not figure out where is the problem. Sipp says user certification file failed ..but client doesnt need any certification file...or does it? i even tried with tls_verify_client = 1 , tls_require_client_certificate = 1, playing with different combinations...but still same ans. Can anyone suggest me what could be wrong? Have i made any mistake in configuring kamailio or theres some problem in SIPP. -- Regards, Hemanshu Patel M: 09601295238

2 7

[Kamailio-Users] Issue with dialog module
by Santiago Gimeno 19 Feb '10

19 Feb '10

Hi, I'm using kamailio 1.5 from the branch. In a conditional forwarding scenario with this call flow: Phone A Kamailio Phone B Phone C | | | | | | | | | | | | |INVITE | | | |------------->| | | |100 Trying | | | |<-------------| | | | |INVITE | | | |------------->| | | |100 trying | | | |<-------------| | | |180 Ringing | | | |<-------------| | |180 Ringing | | | |<-------------| | | | |486 Busy Here | | | |<-------------| | | |ACK | | | |------------->| | | |INVITE | | | |---------------------------->| | |100 trying | | | |<----------------------------| | |180 Ringing | | | |<----------------------------| |180 Ringing | | | |<-------------| | | | |200 OK | | | |<----------------------------| |200 OK | | | |<-------------| | | |ACK | | | |------------->| | | | |ACK | | | |---------------------------->| | | | | | | | | What I'm observing is that when Kamailio receives the 486 from B, the dialog between A and B is not destroyed, so when the call is finally established between A and C there are two active dialogs as I could check with `kamctl fifo get_statistics active_dialogs`. Shouldn't there be only one active dialog? Is this a problem in my script or a problem with the dialog module? Thanks in advance, Santi

3 3

[Serusers] tell me module of ser for nideo streaming..
by city spider 18 Feb '10

18 Feb '10

i want to use ser for streaming . please tell me the specific module for streaming... in streaming me using RTSP (Real Time Streaming Protocol) suggest me the specific module that will be added to fulfil my purpose.

1 0

[Kamailio-Users] Help me on 'No matching subscription dialog found'
by Asterisk User 18 Feb '10

18 Feb '10

Hi Group, I have one more problem regarding a SIP subscribe packet. When my phone registers first time, it gets OK for SUBSCRIBE sent from phone. But after couple of hours it(phone) keeps on sending subsequent SUBSCRIBE requests but the response from Kamailio is 481 Subscription does not exist. Here are my packets, =======================> For first SUBSCRIBE SUBSCRIBE sip:ABC.com SIP/2.0 Via: SIP/2.0/UDP 172.18.100.89:5060;branch=z9hG4bK-4082dbb From: DEF <sip:307@ABC.com>;tag=802bf23e23f4741 To: DEF <sip:307@ABC.com> Call-ID: 9f465e4b-2207f239(a)172.18.100.89 CSeq: 30004 SUBSCRIBE Max-Forwards: 70 Contact: DEF <sip:307@172.18.100.89:5060> Accept: application/simple-message-summary Expires: 2147483647 Event: message-summary User-Agent: Linksys/PAP2T-3.1.15(LS) Content-Length: 0 ------------------------------------------------------- SIP/2.0 202 OK Via: SIP/2.0/UDP 172.18.100.89:5060;branch=z9hG4bK-4082dbb;rport=5060;received=220.224.237.54 From: DEF <sip:307@ABC.com>;tag=802bf23e23f4741 To: DEF <sip:307@ABC.com>;tag=0cca86077d334bd53b00d2c8eab3d5fb.dfeb Call-ID: 9f465e4b-2207f239(a)172.18.100.89 CSeq: 30004 SUBSCRIBE Expires: 3600 Contact: <sip:192.168.94.30:5060> Server: Kamailio (1.5.0-notls (i386/linux)) Content-Length: 0 =======================> For subsequent SUBSCRIBEs SUBSCRIBE sip:ABC.com SIP/2.0 Via: SIP/2.0/UDP 172.18.100.89:5060;branch=z9hG4bK-69712d2e From: DEF <sip:307@ABC.com>;tag=5d3bd6c2989f0839 To: DEF <sip:307@ABC.com>;tag=0cca86077d334bd53b00d2c8eab3d5fb.dfeb Call-ID: 7f6d2c36-97569155(a)172.18.100.89 CSeq: 55947 SUBSCRIBE Max-Forwards: 70 Contact: DEF <sip:307@172.18.100.89:5060> Accept: application/simple-message-summary Expires: 2147483647 Event: message-summary User-Agent: Linksys/PAP2T-3.1.15(LS) Content-Length: 0 ------------------------------------------------------- SIP/2.0 481 Subscription does not exist Via: SIP/2.0/UDP 172.18.100.89:5060;branch=z9hG4bK-69712d2e;rport=5060;received=220.224.237.54 From: DEF <sip:307@ABC.com>;tag=5d3bd6c2989f0839 To: DEF <sip:307@ABC.com>;tag=0cca86077d334bd53b00d2c8eab3d5fb.dfeb Call-ID: 7f6d2c36-97569155(a)172.18.100.89 CSeq: 55947 SUBSCRIBE Server: Kamailio (1.5.0-notls (i386/linux)) Content-Length: 0 ---------------------------------------------------------------------------------------------------------------------------------------------- ===>The error which I get on kamailio is, ERROR:presence:get_database_info: No matching subscription dialog found in database ===>Have already loaded the module presence.so modparam("presence", "db_url", "mysql://XYZ:XYZ@192.168.90.12/openser") modparam("presence", "max_expires", 3600) modparam("presence", "presentity_table", "presentity") modparam("presence", "active_watchers_table", "active_watchers") modparam("presence", "watchers_table", "watchers") modparam("presence", "clean_period", 100) modparam("presence", "db_update_period", 100) modparam("presence", "to_tag_pref", 'pres') modparam("presence", "expires_offset", 10) modparam("presence", "server_address", "sip:192.168.94.30:5060") modparam("presence", "fallback2db", 1) modparam("presence", "subs_htable_size", 11) modparam("presence", "pres_htable_size", 11) loadmodule "presence_mwi.so" loadmodule "presence_xml.so" modparam("presence_xml", "force_active", 1) modparam("presence_xml", "db_url", "mysql://XYZ:XYZ@192.168.90.12/openser") --------------------------------------------------------------------------------------------------------------------------------------------- Please help me on this. --SM

3 11

[Kamailio-Users] starting
by Andrew Matthews 17 Feb '10

17 Feb '10

I'm looking for a tutorial of some sort to help me with getting openser running. What I need from it, are a basic proxy with both IP and username/password authentication, and an lcr. I've searched the net and can't seem to find what I need. I'm new to openser, I came from the asterisk world. If anyone can point me in the right direction I'd appreciate it. Thanks, Exstatica

2 1

Number Portability Functionality
by Asim Riaz 17 Feb '10

17 Feb '10

Hi list, Can someone explain me about PDB server? what I understand that PDB server have all the routing information for all the numbers and SIP-Router receive that information and route the call accordingly but how PDB server receive the routing data? Do we need to load this routing data manually? What happen if the routing information for a number is changed, do we need to update manually? Thanks, Asim

3 2

[Kamailio-Users] Inbound call no way audio
by RAJNIKANT VANZA 17 Feb '10

17 Feb '10

Hi Friends, Outbound calling works fine. When I receive an inbound call, the phone rings, but when I pick up the phone, the conversation does not get established. I have call from inside NAT extension number to Outside NAT extension ( Outboud call ) then call get established and two-way audio work fine but when I have call from Outside NAT extension to Inside NAT extension (Inbound call ) then phone rings, but when pickup the phone, audio is not present. During inboud call RTP packets are not transmit whereas Outboud call RTP packets transmit successful. Sometimes, Inbound and Outbound call only one-way audio present. Can anybody help me, or point me to a previous thread where this issue was discussed and solved? Thanks in advance. -- Best Regards, Rajnikant Vanza

2 4

[Kamailio-Users] What is the best (and secure) way to change FROM_URI using regexp?
by Fernando Frota M Morais 16 Feb '10

16 Feb '10

Before sending this message I looked for an answer and found some options, two of them are followed: 1) SUBST function, sample listed here: if (is_present_hf("User-Agent")) { remove_hf("User-Agent"); remove_hf("P-Asserted-Identity"); subst("/^From: \".+\" (<sip: *[a-zA-Z0-9_\.-]+ <at> .*>)/From: \1/ig"); subst("/^To: \".+\" (<sip: *[a-zA-Z0-9_\.-]+ <at> .*>)/To: \1/ig"); } 2-a) uac_replace: if (from_uri=~"^sip:10804007\@voip.mydomain") { xlog("L_ALERT", "TESTANDO - Original From is ($fu-$fn)\n"); # uac_replace_from("sip:031" . $fU . "\(a)voip.mydomain"); uac_replace_from("Frota10804007","sip:03110804007@voip.mydomain"); xlog("L_ALERT", "TESTANDO - From changed to ($fu-$fn)\n"); }; OR : 2-b) uac _replace #2: if (from_uri=~"^sip:10804007\@.*") { xlog("L_ALERT", "Route 21 - Original from is ($fu-$fn)\n"); $avp(from)=$fu; # $avp(to)=$ru; # avp_pushto("$ru", "$avp(from)"); avp_subst("$avp(from)", "/(sip:)/sip:031/"); uac_replace_from("$avp(from)"); # xlog("L_ALERT", "Route 21 - From changed to ($fu-$fn)\n"); # avp_pushto("$ru", "$avp(to)"); }; } OR Looks like uac_replace is safer then "subst" function, because it can be reverted, but I did not found a way to use concatenation or any other kind of string operation as a parameter for it. I don't want to start a discussion, I need only a few lines showing me how to change from_uri_from from "sip:108xxxx" to "sip:031108xxxx". Thanks in advance, -- Fernando Frota Machado de Morais Divisao de Redes de Comunicacao Centro de Computacao Universidade Federal de Minas Gerais Brasil Tel. +55(31)3409.4007 Fax. +55(31)3409.4004

2 1

[Kamailio-Users] What is wrong with this NOTIFY packet
by Asterisk User 15 Feb '10

15 Feb '10

Hi Group, I know this issue has to do bit more with SIP and off from kamailio problems, but just wanted to know your opinions on this. I have my sip extensions registered to kamilio and Asterisk works as a voicemail server. Now to implement MWI i send NOTIFY packet from Asterisk to Kamailio and from kamailio to SIP extension (Grandstream GXP2000). here is the packet that travels from kamailio to extension and the response sent from extension to kamilio. =========================== NOTIFY sip:1111111@arzoo.com <sip%3A1111111(a)arzoo.com> SIP/2.0 Max-Forwards: 10 Record-Route: <sip:172.18.100.74;lr;nat=yes> Via: SIP/2.0/UDP 172.18.100.74;branch=z9hG4bK3c3.e1003f03.0 Via: SIP/2.0/UDP 127.0.0.1:45382 ;received=172.18.100.73;branch=z9hG4bK.4f83530d;rport=45382;alias Via: SIP/2.0/UDP 172.18.100.73:5060 From: <sip:111@arzoo.com <sip%3A111(a)arzoo.com>> To: <sip:1111111@arzoo.com <sip%3A1111111(a)arzoo.com>> Contact: <sip:1111111@arzoo.com <sip%3A1111111(a)arzoo.com>> Call-ID: 4d61cf9e505d40e905032a18329d61ec(a)172.19.100.42 CSeq: 1 NOTIFY User-Agent: VoiceMail Event: message-summary Content-Type: application/simple-message-summary Content-Length: 39 =========================== SIP/2.0 415 Unacceptable Content-Type Via: SIP/2.0/UDP 172.18.100.74;branch=z9hG4bK3c3.02003f03.0 Via: SIP/2.0/UDP 127.0.0.1:43416 ;received=172.18.100.73;branch=z9hG4bK.7be73901;rport=43416;alias Via: SIP/2.0/UDP 172.18.100.73:5060 Record-Route: <sip:172.18.100.74;lr;nat=yes> From: <sip:111@arzoo.com <sip%3A111(a)arzoo.com>> To: <sip:1111111@arzoo.com <sip%3A1111111(a)arzoo.com>>;tag=3c6ba3e4a93d6864 Call-ID: 4d61cf9e505d40e905032a18329d61ec(a)172.19.100.42 CSeq: 1 NOTIFY User-Agent: Grandstream GXP2000 1.1.4.14 Accept: application/sdp, application/simple-message-summary, application/octet-stream, application/dialog-info+xml, application/pidf+xml, message/sipfrag;version=2.0 Content-Length: 0 =========================== Please guide me in right direction to get rid of 'Unacceptable Content-Type' problem. Thanks in advance, --SM

5 10

[Kamailio-Users] Problems with parallel forking to different users
by Anton Roman 15 Feb '10

15 Feb '10

Hi all, I'm trying to implement parallel forking to different users registered on a Kamailio server. I want to fork the call to a number of different users (not including the called user). To do this I added the piece of code below to the default 3.0.0 config file: ... # account only INVITEs if (is_method("INVITE")) { setflag(1); # do accounting setflag(4); #dialog aware if(avp_db_load("$ru/username","$avp(s:fork)")) { avp_pushto("$ru/username","$avp(s:fork)/g"); }; } .... This is usr_preference table content: +----+------+----------+--------+-----------+------+-------+---------------------+ | id | uuid | username | domain | attribute | type | value | last_modified | +----+------+----------+--------+-----------+------+-------+---------------------+ | 4 | | 1000 | | fork | 0 | 1001 | | | 3 | | 1000 | | fork | 0 | 1005 | | +----+------+----------+--------+-----------+------+-------+---------------------+ Kamailio correctly forks the call to 1001 and 1005, but the Request-URI of the 1005 user is not correctly set, because the proxy IP is used instead of the IP where the user is registered (10.1.2.15). You can see the INVITEs below. Could anybody tell me what I'm doing badly? Thanks for your time, best regards Anton ---------------------------------------------------------------------------------------------------------------------------------------- # U +0.000328 10.1.20.103:5060 -> 10.1.3.18:5061 INVITE sip:1001@10.1.3.18:5061 SIP/2.0 Record-Route: <sip:10.1.20.103;lr=on;did=c34.3ed81d77> Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKc40b.ec3572a3.0 Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-213aa77 From: "1002" <sip:1002@10.1.20.103 <sip%3A1002(a)10.1.20.103> >;tag=280da520d15d62cfo1 To: "1000" <sip:1000@10.1.20.103 <sip%3A1000(a)10.1.20.103>> Call-ID: 8973c34-427096cb(a)10.1.3.15 CSeq: 102 INVITE Max-Forwards: 69 Contact: "1002" <sip:1002@10.1.3.15:5061> Expires: 240 User-Agent: Linksys/SPA941-5.1.5 Content-Length: 202 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 2003696 2003696 IN IP4 10.1.3.15 ... # U +0.000052 10.1.20.103:5060 -> 10.1.20.103:5060 INVITE sip:1005@10.1.20.103 <sip%3A1005(a)10.1.20.103> SIP/2.0 Record-Route: <sip:10.1.20.103;lr=on;did=c34.3ed81d77> Via: SIP/2.0/UDP 10.1.20.103;branch=z9hG4bKc40b.ec3572a3.1 Via: SIP/2.0/UDP 10.1.3.15:5061;branch=z9hG4bK-213aa77 From: "1002" <sip:1002@10.1.20.103 <sip%3A1002(a)10.1.20.103> >;tag=280da520d15d62cfo1 To: "1000" <sip:1000@10.1.20.103 <sip%3A1000(a)10.1.20.103>> Call-ID: 8973c34-427096cb(a)10.1.3.15 CSeq: 102 INVITE Max-Forwards: 69 Contact: "1002" <sip:1002@10.1.3.15:5061> Expires: 240 User-Agent: Linksys/SPA941-5.1.5 Content-Length: 202 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 2003696 2003696 IN IP4 10.1.3.15 ... ----------------------------------------------------------------------------------------------------------------------------------------

2 1

[Kamailio-Users] Registration Timeout Retransmission
by Hemanshu Patel 13 Feb '10

13 Feb '10

Hello to all users, I am very new to kamailio and just started using it. I have installed it and my phones are getting register successfully. But sometimes i am seeing a scenario, which makes my phones unusable for sometime. please see the condition as below | phone |--------------| Kamailio | | REGISTER-----------------> <----------------------401 | REGISTER-----------------> Tricky condition here | timeout <--------------200 OK phone shows itself as unregistered | REGISTER----------------> <--------------------401 After several retries phone stops to retry till say next 20 seconds, during that time though there's an entry in location table in kamailio (i am using mysql) my phone shows itself as unregistered phone. Due to load or any other conditions Server takes a bit time to send 200OK back to phone and During that time timer expires and phone sends REGISTER once again. now phone will keep sending REGISTER request with same nonse and other value, and kamailio is configured to not to entertained same credentials with nonce if it is authenticated once. So kamailio generates new 401 Message with new nonce value to which phone understands as the previous reply thet he send for previous 401 was rejected, and the most probable reason is wrong user credentials..... Hope you guys have got my problem? i can not allow kamailio to let use the same credentials+ response with nonce if it has used it once for security reason. Then what could be the solution for this. I am very good in Programming, but just that i have just started to use kamailio and not very much aware about its architecture. -- Regards, Hemanshu Patel M: 09601295238

3 5

[Serusers] stateful statistics
by Sabatella, Michael 12 Feb '10

12 Feb '10

I know somebody else posted this a while ago but I did not see any response. I tried to research it but could not come up with any answers and would like to get an understanding of this . On the stateful statistics what does 130 waiting and 6 current mean Stateful Statistics Current: 6 (130 waiting) Total: 3540496 (0 local) Replied localy: 3809867 Is it recommended to restart the process once a week or once a month? I am running ser 0.9.6 Thanks for the help. Michael ________________________________ DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems.

1 0

[Kamailio-Users] Error in header - where and how?
by Anders 12 Feb '10

12 Feb '10

Hi, My carrier doesn't like the invites that come from two specific customers I have, who both use something called VoipSwitch. It returns from the carrier as a Bad Request. Below is the dialog - I'm not sharp enough to see what's wrong - anyone? Thanks! //Anders U 2010/02/01 17:53:42.355689 CustomerIP:5060 -> MyProxyIP:5060 INVITE sip:890912551128650136@MyProxyIP SIP/2.0. CSeq: 1 INVITE. Via: SIP/2.0/UDP CustomerIP:5060;branch=z9hG4bk01025810150801381470578. From: "SERVER BR" <sip:001184517324@CustomerIP:5060>;tag=010258101508381470562. Call-ID: GW6d4c945d2c573c27@CustomerIP. To: <sip:890912551128650136@MyProxyIP>. Contact: <sip:CustomerIP:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 250. Remote-Party-ID: "SERVER BR"<sip:69912390@customerDNS>;privacy=off;screen=no. . v=0. o=VoipSwitch 9298 9298 IN IP4 CustomerIP. s=VoipSIP. i=Audio Session. c=IN IP4 CustomerIP. t=0 0. m=audio 8298 RTP/AVP 18 101. a=rtpmap:18 G729/8000/1. a=fmtp:18 annexb=no. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv. U 2010/02/01 17:53:42.355990 MyProxyIP:5060 -> CustomerIP:5060 SIP/2.0 100 Giving a try. CSeq: 1 INVITE. Via: SIP/2.0/UDP CustomerIP:5060;branch=z9hG4bk01025810150801381470578;rport=5060;received=187.45.218.17$ From: "SERVER BR" <sip:001184517324@CustomerIP:5060>;tag=010258101508381470562. Call-ID: GW6d4c945d2c573c27@CustomerIP. To: <sip:890912551128650136@MyProxyIP>. Server: Kamailio. Content-Length: 0. . U 2010/02/01 17:53:42.356010 MyProxyIP:5060 -> CarrierIP:5060 INVITE sip:84370551128650136@CarrierIP:5060 SIP/2.0. Max-Forwards: 10. Max-Forwards: 5. Record-Route: <sip:MyProxyIP;lr=on;nat=yes;did=e4c.e1f33ad5>. CSeq: 1 INVITE. Via: SIP/2.0/UDP MyProxyIP;branch=z9hG4bK139a.a74691c5.0. Via: SIP/2.0/UDP CustomerIP:5060;rport=5060;received=CustomerIP;branch=z9hG4bk0102581015080138147057$ From: "SERVER BR" <sip:001184517324@CustomerIP:5060>;tag=010258101508381470562. Call-ID: GW6d4c945d2c573c27@CustomerIP. To: <sip:890912551128650136@MyProxyIP>. Contact: <sip:CustomerIP:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 250. Remote-Party-ID: "SERVER BR"<sip:69912390@customerDNS>;privacy=off;screen=no. . v=0. o=VoipSwitch 9298 9298 IN IP4 CustomerIP. s=VoipSIP. i=Audio Session. c=IN IP4 CustomerIP. t=0 0. m=audio 8298 RTP/AVP 18 101. a=rtpmap:18 G729/8000/1. a=fmtp:18 annexb=no. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv. U 2010/02/01 17:53:42.608917 CarrierIP:5060 -> MyProxyIP:5060 SIP/2.0 400 Bad Request. Via: SIP/2.0/UDP MyProxyIP;branch=z9hG4bK139a.a74691c5.0. Via: SIP/2.0/UDP CustomerIP:5060;rport=5060;received=CustomerIP;branch=z9hG4bk0102581015080138147057$ From: "SERVER BR" <sip:001184517324@CustomerIP:5060>;tag=010258101508381470562. To: <sip:890912551128650136@MyProxyIP>. Call-ID: GW6d4c945d2c573c27@CustomerIP. CSeq: 1 INVITE. Content-Length: 0.

2 4

[Kamailio-Users] Drouting Question
by Sven Schulz 12 Feb '10

12 Feb '10

Hello, Ive been testing Kamailio 3.0 and drouting. In the documentation it states (Section 1.5 Routing Rule Processing) ³The module will execute serial forking for each address in chain. The next address in chain is used only if the previously has failed.² What exactly defines a failure? Does it use ping or OPTIONS to determine if a GW is busy or down? Id like to know exactly how drouting figures this out. Sven Schulz Penn State University Telecommunications and Network Services 814.865.6116 sip:sven@psu.edu

3 4

[Kamailio-Users] acc module
by Denis Putyato 12 Feb '10

12 Feb '10

Hello everybody! I have a such problem with ACC module. Calls was accounted but only INVITE and BYE requests has appeared in acc table. ACK is absent. Kamailio 3.0 was installed from GIT. Thank you for any help loadmodule "db_mysql.so" loadmodule "mi_fifo.so" loadmodule "tm.so" loadmodule "sl.so" loadmodule "tmx.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "acc.so" loadmodule "avpops.so" loadmodule "siptrace.so" loadmodule "dialplan.so" loadmodule "lcr.so" loadmodule "sqlops.so" loadmodule "carrierroute.so" loadmodule "drouting.so" loadmodule "kex.so" # ----- acc params ----- modparam("acc", "early_media", 0) modparam("acc", "report_ack", 1) modparam("acc", "report_cancels", 1) modparam("acc", "detect_direction", 1) modparam("acc", "db_flag", 1) modparam("acc", "db_missed_flag", 2) modparam("acc", "failed_transaction_flag", 29) modparam("acc", "db_table_acc", "acc") modparam("acc", "db_table_missed_calls", "missed_calls") modparam("acc", "acc_method_column", "method") modparam("acc", "acc_from_tag_column", "from_tag") modparam("acc", "acc_to_tag_column", "to_tag") modparam("acc", "acc_callid_column", "callid") modparam("acc", "acc_sip_code_column", "sip_code") modparam("acc", "acc_sip_reason_column", "sip_reason") modparam("acc", "acc_time_column", "time") modparam("acc", "db_url", "xxxxxxxxxxxxxxxxxxxxxxxx") modparam("acc", "db_extra", "src_user=$avp(i:2);src_domain=$si;dst_ouser=$avp(i:1);dst_user=$rU;dst_doma in=$rd") route { sip_trace(); setflag(30); if (has_totag()) { if (loose_route()) { if (is_method("BYE")) { setflag(1); setflag(29); } if (is_method("ACK")) { xlog("L_NOTICE", "ACK detected"); # I see this line in syslog setflag(1); setflag(29); } route("relay"); exit; } else { if ( is_method("ACK") ) { if ( t_check_trans() ) { setflag(1); route("relay"); exit; } else { exit; } } } }

1 0

[Kamailio-Users] acc & radius
by Kris Amy 12 Feb '10

12 Feb '10

Hi all, Is there anything special required to get radius support into the acc module? I have tried the following... make distclean make config modules_include="mediaproxy auth_radius group_radius uri_radius misc_radius" group_include="mysql standard" make deb But alas it still seems to not have it. I have confirmed that the radius libraries are installed aswell. ii libradiusclient-ng-dev 0.5.6-1 Enhanced RADIUS client library development f ii libradiusclient-ng2 0.5.6-1 Enhanced RADIUS client library Cheers, Kris

2 1

[Kamailio-Users] Extra byte in Content-length header
by Vikram Ragukumar 11 Feb '10

11 Feb '10

Hello, I am testing a cellphone software that registers with an Asterisk server through an outbound proxy (Kamailio+rtpproxy). I am capturing network traffic using wireshark and i notice that the SIP Register message from the cellphone has an extra byte in the Content-Length header, which causes Kamailio to discard the message with the following error output : - ERROR:core:parse_content_length: parse error near char [13][^M] - ERROR:core:get_hdr_field: bad content_length header Could it be that this byte was appended somewhere downstream(possibly at the wireless router..) or can i be sure that the byte was added during SIP Message construction by the cellphone software ? Thanks in advance, Vikram.

4 7

Re: [Kamailio-Users] Siremis Accounting
by Daniel-Constantin Mierla 11 Feb '10

11 Feb '10

Hello, please use public mailing list for such questions. Direct messages get long delayed or lost in most of the cases. Mailing list has plenty of developers and community users that can help you faster. Besides that, new people can benefit of older discussions. On 2/11/10 2:14 AM, Kris Amy wrote: > Hi Daniel, > > It would seem to me that the stored procedure on > http://siremis.asipto.com/install-accounting/ is for PostgreSQL. I'm > going to try and getting it working with MySQL. it is for mysql. Cheers, Daniel > > Just thougth you may want to update the page. > > -- Daniel-Constantin Mierla eLearning class for Kamailio 3.0.0 * http://www.asipto.com/

4 3

Re: [Kamailio-Users] Siptrace and Kamailio 3.0.0
by Daniel-Constantin Mierla 11 Feb '10

11 Feb '10

On 2/11/10 11:16 AM, Kris Amy wrote: > On Thu, Feb 11, 2010 at 8:09 PM, Daniel-Constantin Mierla > <miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: > > Hello, > > ok, then the only point in mod_init of siptrace that causes > initialization error without printing a log message is when you > haven't set the trace_flag parameter: > http://kamailio.org/docs/modules/3.0.x/modules_k/siptrace.html#id2520001 > > Cheers, > Daniel > > > Hi Daniel, > > That fixed it. > > Perhaps there is a bug in that it's not picking up the default of 0? in the sources the default is -1, which means disabled -- docs needs to be updated. Thanks for pointing, Daniel -- Daniel-Constantin Mierla eLearning class for Kamailio 3.0.0 *http://www.asipto.com/

1 0

[Kamailio-Users] SDP IP address not rewritten
by Vikram Ragukumar 11 Feb '10

11 Feb '10

Hello, I am running Kamailio version 1.5 and rtpproxy version 1.2. I have enabled NAT support in Kamailio.cfg. I have a UA behind NAT (UA IP:192.168.2.101), and the UA registers with an Asterisk server (Public IP) through an outbound proxy running Kamailio and rtpproxy with Public IP. Registration succeeds, however when making an outbound call from the UA to a cellphone, there is only one sided voice. This is happening because Asterisk is addressing rtp streams to the UA's local IP address instead of its PublicIP:port. Why is the IP address not being rewritten in the SDP ? Is there an alternate way of invoking rtpproxy (with flags) such that the IP address in the SDP is rewritten ? Thanks and Regards, Vikram. PS : Below is the main routing section of my kamailio.cfg route{ if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } # NAT detection route(4); if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { if (is_method("BYE")) { setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails } route(1); } else { if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(2); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # non loose-route, but stateful ACK; must be an ACK after a 487 or e.g. 404 from upstream server t_relay(); exit; } else { # ACK without matching transaction ... ignore and discard.\n"); exit; } } sl_send_reply("404","Not here"); } exit; } # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) t_relay(); exit; } t_check_trans(); # record routing if (!is_method("REGISTER|MESSAGE")) record_route(); # account only INVITEs if (is_method("INVITE")) { setflag(1); # do accounting } if (!uri==myself) { append_hf("P-hint: outbound\r\n"); route(1); } # requests for my domain if( is_method("PUBLISH|SUBSCRIBE")) route(2); if (is_method("REGISTER")) { if (isflagset(5)) { setbflag(6); # setbflag(7); } if (!save("location")) sl_reply_error(); exit; } if ($rU==NULL) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } # apply DB based aliases (uncomment to enable) ##alias_db_lookup("dbaliases"); if (!lookup("location")) { switch ($retcode) { case -1: case -3: t_newtran(); t_reply("404", "Not Found"); exit; case -2: sl_send_reply("405", "Method Not Allowed"); exit; } } # when routing via usrloc, log the missed calls also setflag(2); route(1); } route[1] { if (check_route_param("nat=yes")) { setbflag(6); } if (isflagset(5) || isbflagset(6)) { route(5); } /* example how to enable some additional event routes */ if (is_method("INVITE")) { #t_on_branch("1"); t_on_reply("1"); t_on_failure("1"); } if (!t_relay()) { sl_reply_error(); } exit; } # Presence route /* uncomment the whole following route for enabling presence server */ route[2] { # if presence enabled, this part will not be executed if (is_method("PUBLISH") || $rU==null) { sl_send_reply("404", "Not here"); exit; } return; } # Caller NAT detection route /* uncomment the whole following route for enabling Caller NAT Detection */ route[4]{ force_rport(); if (nat_uac_test("19")) { if (method=="REGISTER") { fix_nated_register(); } else { fix_nated_contact(); setflag(6);#VR } setflag(5); } return; } # RTPProxy control /* uncomment the whole following route for enabling RTPProxy Control */ route[5] { if (is_method("BYE")) { unforce_rtp_proxy(); } else if (is_method("INVITE")){ force_rtp_proxy(); } if (!has_totag()) add_rr_param(";nat=yes"); return; } branch_route[1] { xdbg("new branch at $ru\n"); } onreply_route[1] { xdbg("incoming reply\n"); if ((isflagset(5) || isbflagset(6)) && status=~"(183)|(2[0-9][0-9])") { force_rtp_proxy(); } if (isbflagset(6)) { fix_nated_contact(); } } failure_route[1] { if (is_method("INVITE") && (isbflagset(6) || isflagset(5))) { unforce_rtp_proxy(); } if (t_was_cancelled()) { exit; } }

2 4

[Kamailio-Users] [kamailio-users] Method NOTIFY not supported ...
by Chandrakant Solanki 11 Feb '10

11 Feb '10

Hi below line is in my configuration... loadmodule "pua.so" modparam("pua", "db_url", "mysql:// kamailio:kamailio@172.16.0.10:3306/kamailio") modparam("pua", "db_table", "pua") ---- ---- if(is_method("NOTIFY") && src_ip==172.16.0.15) { xlog("L_INFO", "NOTIFY Method found\n"); if(!t_relay()){ sl_reply_error(); } } ---- ---- I found following error in log... Feb 10 15:14:40 kamailio_1 /sbin/kamailio[5597]: Method not supported - M=NOTIFY RURI=sip:172.16.0.15 F=sip:2222222@pbxusers.net<sip%3A2222222(a)pbxusers.net>T=sip:172.16.0.15 IP=172.18.100.89 ID= 17dd4bb9-81d132a0(a)172.18.100.89 -- Regards, Chandrakant Solanki

2 7

[Kamailio-Users] Fwd: Siptrace and Kamailio 3.0.0
by Kris Amy 11 Feb '10

11 Feb '10

---------- Forwarded message ---------- From: Kris Amy <kris(a)amy.id.au> Date: 2010/2/11 Subject: Re: [Kamailio-Users] Siptrace and Kamailio 3.0.0 To: Daniel-Constantin Mierla <miconda(a)gmail.com> On Thu, Feb 11, 2010 at 8:09 PM, Daniel-Constantin Mierla <miconda(a)gmail.com > wrote: > Hello, > > ok, then the only point in mod_init of siptrace that causes initialization > error without printing a log message is when you haven't set the trace_flag > parameter: > http://kamailio.org/docs/modules/3.0.x/modules_k/siptrace.html#id2520001 > > Cheers, > Daniel >

1 0

[Kamailio-Users] Siptrace and Kamailio 3.0.0
by Kris Amy 11 Feb '10

11 Feb '10

Hi, Just wondering if anyone is using Siptrace with Kamailio 3.0.0. The module fails to load and I have no idea why (or how to get more information than from debug = 99). 0(13453) DEBUG: <core> [sr_module.c:871]: DEBUG: init_mod: siptrace 0(13453) ERROR: <core> [sr_module.c:874]: init_mod(): Error while initializing module siptrace ERROR: error while initializing modules Cheers, Kris

2 4

[Kamailio-Users] kamailio crashes during connection attempt
by Dmitri 10 Feb '10

10 Feb '10

Hello list, I have fresh installation of Debian Squeeze on X86_64. I downloaded source tarball http://www.kamailio.org/pub/kamailio/latest/src/kamailio-3.0.0_src.tar.gz and did 'make deb' there. So, I got following debian packages: kamailio_3.0.0_amd64.deb, kamailio-berkeley-modules_3.0.0_amd64.deb, kamailio-carrierroute-modules_3.0.0_amd64.deb kamailio-cpl-modules_3.0.0_amd64.deb, kamailio-ldap-modules_3.0.0_amd64.deb, kamailio-memcached-modules_3.0.0_amd64.deb kamailio-mysql-modules_3.0.0_amd64.deb, kamailio-nth_3.0.0_amd64.deb, kamailio-perl-modules_3.0.0_amd64.deb kamailio-postgres-modules_3.0.0_amd64.deb, kamailio-presence-modules_3.0.0_amd64.deb, kamailio-purple-modules_3.0.0_amd64.deb kamailio-radius-modules_3.0.0_amd64.deb, kamailio-snmpstats-modules_3.0.0_amd64.deb, kamailio-tls-modules_3.0.0_amd64.deb kamailio-unixodbc-modules_3.0.0_amd64.deb, kamailio-utils-modules_3.0.0_amd64.deb, kamailio-xmlrpc-modules_3.0.0_amd64.deb kamailio-xmpp-modules_3.0.0_amd64.deb I installed packages: kamailio_3.0.0_amd64.deb, kamailio-mysql-modules_3.0.0_amd64.deb, kamailio-presence-modules_3.0.0_amd64.deb, kamailio-xmlrpc-modules_3.0.0_amd64.deb Created database, changed passwords for openser and openserro users in MySQL as well as in kamailio config files, enabled MySQL. DUMP_CORE=yes in /etc/default/kamailio, also added '-w /var/run/kamailio' to options. Created test user with kamctl. Started kamailio with init script: /etc/init.d/kamailio start: Feb 7 22:05:10 kamailio kamailio: INFO: <core> [tcp_main.c:4150]: init_tcp: using epoll_lt as the io watch method (auto detected) Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: usrloc [hslot.c:53]: locks array size 512 Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core> [udp_server.c:166]: INFO: udp_init: SO_RCVBUF is initially 124928 Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core> [udp_server.c:217]: INFO: udp_init: SO_RCVBUF is finally 262142 Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core> [udp_server.c:166]: INFO: udp_init: SO_RCVBUF is initially 124928 Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core> [udp_server.c:217]: INFO: udp_init: SO_RCVBUF is finally 262142 Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core> [udp_server.c:166]: INFO: udp_init: SO_RCVBUF is initially 124928 Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core> [udp_server.c:217]: INFO: udp_init: SO_RCVBUF is finally 262142 Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2695]: INFO: ctl [io_listener.c:224]: io_listen_loop: using epoll_lt io watch method (config) Then I tried to connect to kamailio server with softphone Zoiper, and kamailio crashes immediately: Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2700]: : <core> [pass_fd.c:283]: ERROR: receive_fd: EOF on 21 Feb 7 22:05:20 kamailio kernel: [ 1051.407643] kamailio[2689]: segfault at c2 ip 00007fa8b5947b19 sp 00007fff48ff9700 error 4 in tm.so[7fa8b5917000+72000] Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2678]: ALERT: <core> [main.c:722]: child process 2689 exited by a signal 11 Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2678]: ALERT: <core> [main.c:725]: core was not generated Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2678]: INFO: <core> [main.c:737]: INFO: terminating due to SIGCHLD Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2691]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2699]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2698]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2687]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2697]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2690]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2696]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2688]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2695]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2680]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2694]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2693]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2692]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2686]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2685]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2681]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2684]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2682]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2700]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2683]: INFO: <core> [main.c:788]: INFO: signal 15 received Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2678]: ERROR: ctl [ctl.c:379]: ERROR: ctl: could not delete unix socket /tmp/ser_ctl: Operation not permitted (1) Feb 7 22:05:20 kamailio kernel: [ 1051.432646] kamailio[2678]: segfault at 12 ip 00007fa8b592ae43 sp 00007fff48ff9f40 error 4 in tm.so[7fa8b5917000+72000] For unknown reason core was not generated. Any ideas ? Many thanks in advance, Dmitri

5 35

[Kamailio-Users] save() function
by Kris Amy 10 Feb '10

10 Feb '10

Hi All, It was to my understanding that this function was part of the core and thus didn't come from a module. The relevant code snippet is if(!save("location")) { xlog("L_ERR", "Saving contact failed - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); sl_reply_error(); exit; } The error I'm getting is.. 0(20467) DEBUG: <core> [sr_module.c:516]: find_export_record: <save> not found 0(20467) DEBUG: <core> [sr_module.c:516]: find_export_record: <save> not found 0(20467) : <core> [cfg.y:3329]: parse error in config file /etc/kamailio/kamailio.cfg, line 656, column 21: unknown command, missing loadmodule? Cheers, Kris

2 2

[Kamailio-Users] Carrierroute issue
by michel freiha 10 Feb '10

10 Feb '10

Hi all, I'm using carrierroute module and ie seems that it's not working well...Suppose I have 2 entries in carrierroute table...Entry 1 with scan prefix 00 and prob 0 and a second entry with scan prefix 00 and prob=1...As soon as i make a call, this call will be forwarded to the entry with prob 0 because i guess it appears before the one with prob 1 in the table... When starting Kamailio I got the below: Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 1, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: domain 0 not found, add it Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_tree: tree default has 1 trees Jul 29 12:30:11 [23143] DBG:carrierroute:add_route_tree: tree 0Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: created route tree: 0, with id 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix , prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 011, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 00, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 111, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 00, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix , prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 011, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 011, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix , prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules It seems that kamailio is not reading probability entry in carrier route table Please find below carrierroute table structure: CREATE TABLE IF NOT EXISTS `carrierroute` ( `id` int(10) unsigned NOT NULL auto_increment, `carrier` int(10) unsigned NOT NULL default '0', `domain` varchar(64) NOT NULL default '', `scan_prefix` varchar(64) NOT NULL default '', `flags` int(11) unsigned NOT NULL default '0', `mask` int(11) unsigned NOT NULL default '0', `prob` float NOT NULL default '0', `strip` int(11) unsigned NOT NULL default '0', `rewrite_host` varchar(128) NOT NULL default '', `rewrite_prefix` varchar(64) NOT NULL default '', `rewrite_suffix` varchar(64) NOT NULL default '', `description` varchar(255) default NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=23 ; Can someone help me to find this issue? Regards

5 13

[Kamailio-Users] check_user_blacklist function
by Antonio Reale 10 Feb '10

10 Feb '10

Hi all, the function check_user_blacklist in kamailio 1.4 returns -1 (FALSE based on the doc) "if a match is found and it is not set to whitelist", otherwise it returns 1 (TRUE). So the function returns the same value if a match is found and is set to whitelist and if there are no matches. I need to differentiate the two situations. The userblacklist module in kamailio 3.0 has a new function "check_user_whitelist" that can solve my problem, but at this time I can't upgrade. I solved the problem, changing only the return value in case of whitelisted entry (userblacklist.c file), but I don't know if it is a safe (and suffice) modification. Below the piece of code in the userblacklist.c: if (dt_longest_match(dt_root, ptr, &whitelist) >= 0) { if (whitelist) { /* LM_ERR("whitelisted"); */ return 2; /* found, but is whitelisted */ <===== CHANGED HERE. IT WAS return 1 } } else { /* LM_ERR("not found"); */ return 1; /* not found is ok */ } Thanks. Regards. -- Antonio

2 2

[Kamailio-Users] LCR
by Kris Amy 10 Feb '10

10 Feb '10

Hi All, I've been ripping my hair out for a little with load_gws(). How do I know what the lcr_id is and the caller_uri? I would have thought that $fu for caller_uri would have been sufficient but it seems not. Cheers, Kris

3 2

[Kamailio-Users] kamctl and lcr table
by Kris Amy 10 Feb '10

10 Feb '10

Hi, Could we get the lcr-create.sql updated to have the ping field? Cheers, Kris

2 3

[Kamailio-Users] irc devel meeting
by Daniel-Constantin Mierla 09 Feb '10

09 Feb '10

Hello, I was thinking of having an IRC meeting to discuss next steps within sip router. Now that 3.0 branches are out for a while, would be good to plan a bit 3.1. For me Friday (or even Thursday if not too early for others to make arrangements) this week would be good, say 14:00 or 15:00UTC to allow fair time for US. If this date does not fit, please make proposals. The channel is #sip-router on freenode.net. Cheers, Daniel -- Daniel-Constantin Mierla eLearning class for Kamailio 3.0.0 * http://www.asipto.com/

1 0

[Kamailio-Users] problems with mi_xmlrpc command
by Anton Roman 09 Feb '10

09 Feb '10

Hi all, I'm trying to send xmlrpc commands to Kamailio with Siremis but I get the error below: Fault Code: 5 Fault Reason: Didn't receive 200 OK from remote server. (HTTP/1.1 400 Bad Request) I get the same error when I manually send the xmlrpc command with curl. On the other hand, mi_xmlrpc module seems to be correctly loaded, but nothing is written in the log file (set with modparam("mi_xmlrpc", "log_file", "/var/log/abyss.log")). Does anybody know where the problem might be? Best regards, thanks in advance. Anton Roman These are the traces of the xmlrpc message flow: T +11.569284 127.0.0.1:37821 -> 127.0.0.1:8080 [AP] POST HTTP/1.0 User-Agent: PEAR XML_RPC Host: 127.0.0.1 Content-Type: text/xml Content-Length: 135 <?xml version="1.0" encoding="UTF-8"?> <methodCall> <methodName>system.listMethods</methodName> <params> </params> </methodCall> ## T +0.000363 127.0.0.1:8080 -> 127.0.0.1:37821 [AP] HTTP/1.1 400 Bad Request # T +0.000146 127.0.0.1:8080 -> 127.0.0.1:37821 [AP] Content-type: text/html # T +0.001982 127.0.0.1:8080 -> 127.0.0.1:37821 [AFP] Connection: close Date: Mon, 08 Feb 2010 14:04:08 GMT Server: XMLRPC_ABYSS/1.06 <HTML><HEAD><TITLE>Error 400</TITLE></HEAD><BODY><H1>Error 400</H1>Bad Request<HR><a href="http://xmlrpc-c.sourceforge.net">ABYSS Web Server for XML-RPC For C/C++</a> version 1.06 </BODY></HTML> ####

2 2

[Kamailio-Users] Stateless forward
by Antonio Reale 09 Feb '10

09 Feb '10

Hi all, I'm trying to setup a very basic scenario with kamailio 3.0. It is placed in front of a softswitch and it has to modify some headers before forward (stateless) messages to softswitch. If I use route { rewritehost("192.168.10.1"); t_relay(); } all work, but if I want to do that stateless and I use forward() or send() instead of t_relay(), I get a syntax error: "bad forward argument" or "bad send argument". If I use ... forward("udp:192.168.10.1:5060"); ... I see in the log /usr/local/sbin/kamailio[3675]: : <core> [proxy.c:271]: ERROR: mk_proxy: could not resolve hostname: "udp:192.168.10.1:5060" /usr/local/sbin/kamailio[3675]: ERROR: <core> [route.c:1026]: fixing failed (code=-478) at cfg:/usr/local/etc/kamailio/kamailio.cfg:77 Same error using the long format of send() function. I can't see any particular hint on the documentation, what I'm missing? Thank you. Best regards. -- Antonio

3 6

[Kamailio-Users] Install Documentation
by Kris Amy 09 Feb '10

09 Feb '10

Hi All, Just thought that you might want to put down that libpcre is required for lcr in the install document. (Since the other main modules have their requirements listed). Cheers, Kris

2 1

[Kamailio-Users] change domain at to header
by Adnan Çelikel 09 Feb '10

09 Feb '10

Dear All, I want to change a field (Sip to address host part) at sip message header. I think avpops will solve this.If anybody has a sample confg and send to me I will be very glad.Regards,Adnan. #---------------------------------------------------- #7777 CALL ROUTING #-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* if(is_method("INVITE") && (uri=~"sip:7777")){ rewritehostport("192.168.1.10:5060"); route(1); exit; } #---------------------------------------------------- at this rule, the invite is going to 192.168.1.10 with the host part as abc.com, we want to send with another domain. Instead of abc.com domain, I want to use 192.168.1.10 domain ; To:<sip:7777@abc.com> To:<sip:7777@192.168.1.10> _________________________________________________________________ Windows Live Hotmail: Arkadaşlarınız Facebook'taki güncellemelerinizi doğrudan Hotmail®'den alır. http://www.microsoft.com/windows/windowslive/see-it-in-action/social-networ…

5 11

Routing Problems
by Andreas Rehbein 08 Feb '10

08 Feb '10

Hello, we use Kamailio 3.0 on a Red Hat EL5.4 system with openssl 0.9.8e (the current Red Hat OpenSSL version). We want to use Kamailio 3.0 in front of our Call Server (OpenSER 1.3.2) as a security gateway. So the Call Server should only deal tcp, while the Security Gateway terminates the TLS Data which he receives from the User Agents but forwards the SIP-Messages via TCP to the Call Server. UA ---SIP_over_TLS---> Security Gateway (Kam3.0) ---SIP_over_TCP---> Call Server (OpenSER1.3.2) UA<---SIP_over_TLS--- Security Gateway (Kam3.0) <---SIP_over_TCP--- Call Server (OpenSER1.3.2) Nearly everything works fine in this scenario: User Agents are able to register and when they are sending INVITES the callee receives it. The problem we have right now is: if Kamailio 3.0 receives BYE we get 477 Unfortunatly error on sending to next hop occured. It seems that the messages are ok... I attached a text file with the BYE message and the errors. Explanation for the text file: * UA1: 192.168.0.126 * UA2: 192.168.0.176 *Security Gateway (Kam3.0): 192.168.0.89 *Call Server (OpenSER1.3.2): 192.168.0.106 Do you have any suggestions? Thank you very much in advance! Regards Andreas Dipl.-Ing. (FH) Andreas Rehbein FH Frankfurt am Main - University of Applied Sciences FB 2 - Informatik und Ingenieurwissenschaften Forschungsgruppe für Telekommunikationsnetze Kleiststraße 3 60318 Frankfurt am Main Tel.: +49 (0) 69 1533 3613 Fax: +49 (0) 69 1539 5224 961 E-Mail: <mailto:rehbein@e-technik.org> rehbein(a)e-technik.org Internet: <http://www.e-technik.org/frame_forschung.htm> http://www.e-technik.org/frame_forschung.htm

2 2

[Kamailio-Users] Maximum retries exceeded on transmission
by Daniel-Constantin Mierla 06 Feb '10

06 Feb '10

On Sat, Feb 6, 2010 at 11:10 AM, Jon Farmer <viperdudeuk(a)gmail.com> wrote: > Sorry it was a problem I had with gmail. > It happens to me from time to time, but I couldn't find the real cause, whether is gmail or thunderbird. Thunderbird hangs a while, reports a delivery error, then message appears twice... Daniel > On 5 Feb 2010 12:21, "Iñaki Baz Castillo" <ibc(a)aliax.net> wrote: > > 2010/2/5 Jon Farmer <viperdudeuk(a)gmail.com>: > > Hi > > Please don't send the same smail twice. Thanks. > > > _______________________________________________ > Kamailio (OpenSER) - Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > http://lists.openser-project.org/cgi-bin/mailman/listinfo/users > -- Daniel-Constantin Mierla http://www.asipto.com -- Daniel-Constantin Mierla http://www.asipto.com

1 0

[Kamailio-Users] Maximum retries exceeded on transmission
by Daniel-Constantin Mierla 06 Feb '10

06 Feb '10

Hello, On Fri, Feb 5, 2010 at 10:56 AM, Jon Farmer <viperdudeuk(a)gmail.com> wrote: > Hi > > I am getting this dreaded error on a asterisk box when call from one > UA to another using Asterisk as a media relay and openser as a SBC and > proxy. > > chan_sip.c:3779 retrans_pkt: Maximum retries exceeded on transmission > 1310650592(a)10.100.0.101 > > If I make a call from a UA to the PSTN through Asterisk all is > fine. This only happens when calling from one UA to another on the > same LAN. > > I have posted an example sip trace here http://pastebin.com/m2262b0ef > ACK is not accepted as I could spot quickly, 200ok being retransmitted. Probably there is something wrong with dialog attributes, after Fosdem I can check it better. Daniel > My openser.cfg is here http://pastebin.com/d5e84aaf7 > > I realise this is a issue with Asterisk but I have not been able to > find a fix. Therefore I figure there might be something I can do on > openser. The problem seems to be with a ACK not being returned but my > SIP knowledge is not good enough to know how to fix it. Any help is > greatly appreciated. > > Regards > > Jon > -- > Jon Farmer > Tel: 07795 118140 > Email: viperdudeuk(a)gmail.com > Twitter: @viperdudeuk > > _______________________________________________ > Kamailio (OpenSER) - Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > http://lists.openser-project.org/cgi-bin/mailman/listinfo/users > -- Daniel-Constantin Mierla http://www.asipto.com -- Daniel-Constantin Mierla http://www.asipto.com

1 0

[Kamailio-Users] Maximum retries exceeded on transmission
by Jon Farmer 06 Feb '10

06 Feb '10

Hi I am getting this dreaded error on a asterisk box when call from one UA to another using Asterisk as a media relay and openser as a SBC and proxy. chan_sip.c:3779 retrans_pkt: Maximum retries exceeded on transmission 1310650592(a)10.100.0.101 If I make a call from a UA to the PSTN through Asterisk all is fine. This only happens when calling from one UA to another on the same LAN. I have posted an example sip trace here http://pastebin.com/m2262b0ef My openser.cfg is here http://pastebin.com/d5e84aaf7 I realise this is a issue with Asterisk but I have not been able to find a fix. Therefore I figure there might be something I can do on openser. The problem seems to be with a ACK not being returned but my SIP knowledge is not good enough to know how to fix it. Any help is greatly appreciated. Regards Jon -- Jon Farmer Tel: 07795 118140 Email: viperdudeuk(a)gmail.com Twitter: @viperdudeuk

2 2

[Serusers] RECEIVED column in SER.LOCATION table
by Bill McNamara 05 Feb '10

05 Feb '10

Question, when does a value get inserted into the ser.location table’s received column. We have some UA’s with a contact like value and some with null values – different devices (Polycom 331/450/55, Grandstream 286/486) behind the same firewall. I’m just curious to know why some have a received value and some don’t. Thanks, Bill SER 2.0 Linux 2.6.9-78 x86_64 MySQL 5.1.30

2 1

[Kamailio-Users] CRITICAL:dialog:log_next_state_dlg
by alex pappas 05 Feb '10

05 Feb '10

Dear users, I'm doing some stress test with kamailio 1.5. When I'm at 50 CPS a see some strange messages: /usr/sbin/kamailio[12754]: CRITICAL:dialog:log_next_state_dlg: bogus event 2 in state 3 for dlg 0x2b0b911831b0 [3345:993496027] with clid '297-19089@IP-address' and tags '19089SIPpTag00297' '15519SIPpTag01304' Does anyone before experienced this before? Thanks Alex

1 0

[Kamailio-Users] Maximum retries exceed on transmission
by Jon Farmer 05 Feb '10

05 Feb '10

Hi I am getting this dreaded error on a asterisk box when call from one UA to another using Asterisk as a media relay and openser as a SBC and proxy. If I make a call from a UA to the PSTN through Asterisk all is fine. This only happens when calling from one UA to another on the same LAN. I have posted an example sip trace here http://pastebin.com/m2262b0ef My openser.cfg is here http://pastebin.com/d5e84aaf7 I realise this is a issue with Asterisk but I have not been able to find a fix. Therefore I figure there might be something I can do on openser. The problem seems to be with a ACK not being returned but my SIP knowledge is not good enough to know how to fix it. Any help is greatly appreciated. Regards Jon -- Jon Farmer Tel: 07795 118140 Email: viperdudeuk(a)gmail.com Twitter: @viperdudeuk

3 5

[Kamailio-Users] new: interactive debugger for config
by Daniel-Constantin Mierla 05 Feb '10

05 Feb '10

Hello, the new debugger module can be used to do runtime debugging of SIP Router config file, in similar manner of gdb. The module is controlled via the RPC interface, therefore investigation can be done from a remote site. That makes it very handy to use with sercmd as well. One features is to print a log message for each action executed in the config for a SIP message, showing the execution path. The option can be enabled/disabled per process. The other one is step by step execution of config file. When a SIP message message comes it, SIP Router process will stop at first action and wait for commands, like: execute the action, evaluate a pseduo-variable, print to syslog a pseudo-variable, remove the breakpoints and continue execution without interruption, ... See the readme for more: http://sip-router.org/docbook/sip-router/branch/master/modules/debugger/deb… It is still some stuff to complete, some known issues to remove, but the module is usable and may help some of you to troubleshoot migrations from older versions to 3.0 (use master branch until your config is updated and running fine, then use it with stable 3.0). Hope is going to be useful and waiting for feedback to improve. Of course, contributions are most welcome! Cheers, Daniel -- Daniel-Constantin Mierla eLearning class for Kamailio 3.0.0 Starting Feb 8, 2010 * http://www.asipto.com/

4 5

[Kamailio-Users] Kamailio/SIPRouter Training
by Bruce McAlister 05 Feb '10

05 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, Are there any planned dates for Kamailio/SIPRouter training events around Europe in the next couple months. Looking forward to your replies..... Thanks Bruce -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLa+kVAAoJEGJOkoTLLvBntMUIAJZEb7AaFDAdwKmTxlyokq30 A5eebX8mTUXk9fkzcHX0IoRRrl8eQKGqUbIl2312oQZtxJrffTksY3xiFFOdpBCp 78RDmKjLvmhAwq7jYPExk91BiV4no+dcAKuHsntwz8EfW9uHd34NRlp+TEc8Q2A8 QB7Ztfq8J+8KjGWJoRE27gqiHEIwZp7F7/rvn4N/VAuaTcaTtYhaiI52iIOA+aNM UTgkGMVzjjpPrwXh7C/DZERKThTifF01PzCx1DSlPiMczrGCGxHy8NEgAaHHsXb9 yrrtd/B4qWAbaYT8mRXisw9hNaGktdmCAA6Ksrq/xz/qjjVa84Tflo9d754PTGw= =kgI0 -----END PGP SIGNATURE-----

1 0

[Kamailio-Users] load_credentials problem
by Dubravko Caric 05 Feb '10

05 Feb '10

Hi all, i have a problem when using AVPs which are loaded on client registration by the "load_credentials". in the "subscriber" table i have "rpid" column (value 12345), "email address" (bob(a)example.com) and "acl" (value 3). when client registers, these three AVPs are loaded as you can see in debug. But when i want to use these AVPs it seems that they are empty. i don't understand if they are ready for use or do i need to load them and how? i'm not doing any actions on AVPs so i could by mistake delete or replace the original ones... version of kamailio is 1.5.1 Thanks Dubravko modparam("auth_db", "load_credentials", "$avp(i:66)=rpid;email_address;$avp(i:67)=acl") DBG:db_mysql:db_mysql_get_columns: allocate 16 bytes for RES_NAMES[0] at 0x783400 DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x783400)[0]=[password] DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type DBG:db_mysql:db_mysql_get_columns: allocate 16 bytes for RES_NAMES[1] at 0x783420 DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x783420)[1]=[acl] DBG:db_mysql:db_mysql_get_columns: use DB_INT result type DBG:db_mysql:db_mysql_get_columns: allocate 16 bytes for RES_NAMES[2] at 0x783440 DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x783440)[2]=[email_address] DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type DBG:db_mysql:db_mysql_get_columns: allocate 16 bytes for RES_NAMES[3] at 0x783460 DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x783460)[3]=[rpid] DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type DBG:core:db_allocate_rows: allocate 16 bytes for rows at 0x783480 DBG:core:db_allocate_row: allocate 128 bytes for row values at 0x7834a0 DBG:core:db_str2val: converting STRING [1234] DBG:core:db_str2val: converting INT [3] DBG:core:db_str2val: converting STRING [bob(a)example.com] DBG:core:db_str2val: converting STRING [12345] DBG:auth_db:get_ha1: HA1 string calculated: 649766733fe475191f6c32d338aae51d DBG:auth:check_response: our result = 'f929dd9729d3c9447c4a4d632a762c85' DBG:auth:check_response: authorization is OK DBG:auth:post_auth: nonce index= 0 DBG:auth_db:generate_avps: set int AVP ""/67 = 3 DBG:auth_db:generate_avps: set string AVP "email_address"/0 = "bob(a)example.com" DBG:auth_db:generate_avps: set string AVP ""/66 = "12345" DBG:core:db_free_columns: freeing 4 columns ################# if (is_method("INVITE")) { xlog("L_INFO", "RPID AVP VALUE $avp(i:66)\n"); xlog("L_INFO", "EMAIL AVP VALUE $avp(s:email_address)\n"); xlog("L_INFO", "ACL AVP VALUE $avp(i:67)\n"); } ./kamailio[21687]: PRID AVP VALUE <null> ./kamailio[21687]: EMAIL AVP VALUE <null> ./kamailio[21687]: ACL AVP VALUE <null>

4 5

[Kamailio-Users] Kamailio v1.5.4 and v1.4.5 released
by Daniel-Constantin Mierla 05 Feb '10

05 Feb '10

Hello, Kamailio version 1.5.4 is out, built from latest svn version of SVN branch 1.5. All details about it are available at: http://www.kamailio.org/mos/view/News/NewsItem/Kamailio-v1.5.4-Released/ Also Kamailio v1.4.5 was released to mark the end of official maintenance for SVN branch 1.4. Details at: http://www.kamailio.org/mos/view/News/NewsItem/Kamailio-v1.4.5-Released/ If you are using a version from these release series, consider updating to the last one. Personally I recommend that you upgrade to the latest stable branch release v3.0.0 -- you get access lot of new features and improvements. Cheers, Daniel

3 5

Re: [Kamailio-Users] [kamailio-users] can't connect with remote database
by Chandrakant Solanki 05 Feb '10

05 Feb '10

On Thu, Feb 4, 2010 at 5:38 PM, Chandrakant Solanki < solanki.chandrakant(a)gmail.com> wrote: > > > On Thu, Feb 4, 2010 at 5:31 PM, marius zbihlei <marius.zbihlei(a)1and1.ro>wrote: > >> Chandrakant Solanki wrote: >> >>> Hi >>> >>> I have 3 server with 172.16.0.10/13/14 <http://172.16.0.10/13/14> IP >>> address. >>> >>> >>> My DB is located for 172.16.0.10. I tried to connect mysql from terminal, >>> it works great. >>> >>> But when I start kamailio it gives me following error.. >>> >>> Hello >> >> Just to double check Have you tried: >> >> mysql --user=openser -p --host=172.16.0.10 openser >> >> from 172.16.0.13 and it works? >> >> From localhost afaik mysql client might use Unix socks(/tmp/mysql.sock) . >> Use should double check that your MySQL server allows TCP connections >> >> Cheers >> >> Marius >> > > Hi mysql --user=openser -p --host=172.16.0.10 openser --socket=/var/lib/mysql/mysql. i have used this command from 172.16.0.13/14 it will works fine and connect to DB on 172.16.0.10 -- Regards, Chandrakant Solanki

1 0

[Kamailio-Users] OK, I've had enough "Ausente"
by Alex Balashov 04 Feb '10

04 Feb '10

Basta. Ya me has dicho que no estás. -- Alex Balashov - Principal Evariste Systems LLC Tel : +1 678-954-0670 Direct : +1 678-954-0671 Web : http://www.evaristesys.com/

3 3

[Kamailio-Users] Openser with MySql Cluster
by Ricardo Coelho 04 Feb '10

04 Feb '10

Hi Right now I have a single openser server configured to work with a single mysql database. I want to enhance availability by adding another openser server and use Mysql Cluster. When failover occurs, despite the fact that he databases have the same data, on one of the softphones i receive a message saying "User not found" and on the other softphone i receive a message saying "Security check failed". Do I need to change something in openser's configuration to make it work with mysql cluster? Thanks in advanced

3 4

Re: [Kamailio-Users] break a call?
by BERGANZ Francois 04 Feb '10

04 Feb '10

Where can I activate it? -----Message d'origine----- De : Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Envoyé : jeudi 4 février 2010 14:09 À : BERGANZ Francois Objet : Re: [Kamailio-Users] break a call? probably the problem is that you can not use tm module functions in onreply_route. You have to handle the responses in the failure route (every final response >=300 triggers the failure_route (if activated)). regards klaus Am 04.02.2010 13:40, schrieb BERGANZ Francois: > Line 254 is t_reply("406", "Not Acceptable"); > > > > -----Message d'origine----- > De : Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > Envoyé : jeudi 4 février 2010 13:08 > À : BERGANZ Francois > Objet : Re: [Kamailio-Users] break a call? > > > > Am 04.02.2010 12:37, schrieb BERGANZ Francois: >> I have that error: >> >> >> onreply_route[1] { >> if(t_check_status("3[0-9][0-9]")){ >> xlog("L_ERR", "3XX!!!!!!!!!!!\n"); >> t_reply("406", "Not Acceptable"); >> exit; >> } >> } >> >> Feb 4 12:36:41 [4584] CRITICAL:core:yyerror: parse error in config >> file, line 254, column 16-17: Command cannot be used in the block > > How will I know what line 254 is? > > The code I sent uses the failure-route, not the reply-route. > > klaus > > >> >> >> Any idea? >> >> Thank you >> >> >> >> -----Message d'origine----- >> De : Klaus Darilion [mailto:klaus.mailinglists@pernau.at] >> Envoyé : jeudi 4 février 2010 08:59 >> À : BERGANZ Francois >> Cc : users(a)lists.kamailio.org >> Objet : Re: [Kamailio-Users] break a call? >> >> e.g.: >> >> failure_route[1] { >> if(t_check_status("302")) { >> xlog("L_INFO","302 redirect received\n"); >> t_reply("403","received 302 from downstream client"); >> exit; >> } >> } >> >> klaus >> >> Am 04.02.2010 08:37, schrieb BERGANZ Francois: >>> Hello, >>> >>> I know that we can break a call with sl_reply(). >>> >>> But, in the on_reply route, how can I break a call if I receive a >>> 3XX (I cant use a sl_reply() function!) ? >>> >>> Thank you >>> >>> >>> >>> _______________________________________________ >>> Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org >>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >>> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >> >

2 1

Routing Problems (Sorry, Text file is now included)
by Andreas Rehbein 04 Feb '10

04 Feb '10

Hello, we use Kamailio 3.0 on a Red Hat EL5.4 system with openssl 0.9.8e (the current Red Hat OpenSSL version). We want to use Kamailio 3.0 in front of our Call Server (OpenSER 1.3.2) as a security gateway. So the Call Server should only deal tcp, while the Security Gateway terminates the TLS Data which he receives from the User Agents but forwards the SIP-Messages via TCP to the Call Server. UA ---SIP_over_TLS---> Security Gateway (Kam3.0) ---SIP_over_TCP---> Call Server (OpenSER1.3.2) UA<---SIP_over_TLS--- Security Gateway (Kam3.0) <---SIP_over_TCP--- Call Server (OpenSER1.3.2) Nearly everything works fine in this scenario: User Agents are able to register and when they are sending INVITES the callee receives it. The problem we have right now is: if Kamailio 3.0 receives BYE we get "477 Unfortunatly error on sending to next hop occured". It seems that the messages are ok... I attached a text file with the BYE message and the errors. Explanation for the text file: * UA1: 192.168.0.126 * UA2: 192.168.0.176 *Security Gateway (Kam3.0): 192.168.0.89 *Call Server (OpenSER1.3.2): 192.168.0.106 No. Time Source Destination Protocol Info 101 7.964015 192.168.0.106 192.168.0.89 SIP Request: BYE sip:+497118113608227@192.168.0.89:37260;transport=TLS Frame 101 (1138 bytes on wire, 1138 bytes captured) Ethernet II, Src: AlliedTe_3e:b8:05 (00:15:77:3e:b8:05), Dst: Dell_a0:e2:3f (00:1c:23:a0:e2:3f) Internet Protocol, Src: 192.168.0.106 (192.168.0.106), Dst: 192.168.0.89 (192.168.0.89) Transmission Control Protocol, Src Port: 50445 (50445), Dst Port: sip (5060), Seq: 1234, Ack: 1, Len: 1072 Session Initiation Protocol Request-Line: BYE sip:+497118113608227@192.168.0.89:37260;transport=TLS SIP/2.0 Message Header Record-Route: <sip:192.168.0.106;transport=tcp;lr=on;ftag=ba3448a0> Record-Route: <sip:192.168.0.89;transport=tcp;r2=on;lr=on> Record-Route: <sip:192.168.0.89:5061;transport=tls;r2=on;lr=on> Via: SIP/2.0/TCP 192.168.0.106;branch=z9hG4bK854f.b305c913.0;i=19 Via: SIP/2.0/TCP 192.168.0.89;rport=37260;branch=z9hG4bK854f.dac34f77.0;i=a Via: SIP/2.0/TLS 192.168.0.126:62399;branch=z9hG4bK-d8754z-51f50d6cfa997da7-1---d8754z-;rport =1876 Max-Forwards: 68 Route: <sip:192.168.0.89;transport=tcp;r2=on;lr=on> Route: <sip:192.168.0.89:5061;transport=tls;r2=on;lr=on> Contact: <sip:+497118113608226@192.168.0.89:37260;transport=TLS;rinstance=972e46956fc 87f26> To: "+497118113608227"<sip:+497118113608227@192.168.0.106>;tag=15c25277 From: <sip:+497118113608226@192.168.0.106>;tag=ba3448a0 Call-ID: ZjdiMWY5NTYxMTMyN2Q5NTkwOWVmZWExOTEwMDhjYzQ. CSeq: 2 BYE User-Agent: Bosch Communicator release 2.5.4.2 GAC4 stamp 54836 Reason: SIP;description="User Hung Up" Content-Length: 0 P-hint: rr-enforced No. Time Source Destination Protocol Info 103 7.964791 192.168.0.89 192.168.0.106 SIP Status: 477 Unfortunately error on sending to next hop occurred (477/SL) Frame 103 (887 bytes on wire, 887 bytes captured) Ethernet II, Src: Dell_a0:e2:3f (00:1c:23:a0:e2:3f), Dst: AlliedTe_3e:b8:05 (00:15:77:3e:b8:05) Internet Protocol, Src: 192.168.0.89 (192.168.0.89), Dst: 192.168.0.106 (192.168.0.106) Transmission Control Protocol, Src Port: sip (5060), Dst Port: 50445 (50445), Seq: 1, Ack: 2306, Len: 821 Session Initiation Protocol Status-Line: SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/SL) Message Header Via: SIP/2.0/TCP 192.168.0.106;branch=z9hG4bK854f.b305c913.0;i=19 Via: SIP/2.0/TCP 192.168.0.89;rport=37260;branch=z9hG4bK854f.dac34f77.0;i=a Via: SIP/2.0/TLS 192.168.0.126:62399;branch=z9hG4bK-d8754z-51f50d6cfa997da7-1---d8754z-;rport =1876 To: "+497118113608227"<sip:+497118113608227@192.168.0.106>;tag=15c25277 From: <sip:+497118113608226@192.168.0.106>;tag=ba3448a0 Call-ID: ZjdiMWY5NTYxMTMyN2Q5NTkwOWVmZWExOTEwMDhjYzQ. CSeq: 2 BYE Server: kamailio (3.0.0 (i386/linux)) Content-Length: 0 [truncated] Warning: 392 192.168.0.89:5060 "Noisy feedback tells: pid=10378 req_src_ip=192.168.0.106 req_src_port=50445 in_uri=sip:+497118113608227@192.168.0.89:37260;transport=TLS out_uri=sip:+497118113608227@192.168.0.89:37260;transport No. Time Source Destination Protocol Info 104 7.964845 192.168.0.89 192.168.0.106 SIP Status: 477 Unfortunately error on sending to next hop occurred (477/TM) Frame 104 (887 bytes on wire, 887 bytes captured) Ethernet II, Src: Dell_a0:e2:3f (00:1c:23:a0:e2:3f), Dst: AlliedTe_3e:b8:05 (00:15:77:3e:b8:05) Internet Protocol, Src: 192.168.0.89 (192.168.0.89), Dst: 192.168.0.106 (192.168.0.106) Transmission Control Protocol, Src Port: sip (5060), Dst Port: 50445 (50445), Seq: 822, Ack: 2306, Len: 821 Session Initiation Protocol Status-Line: SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/TM) Message Header Via: SIP/2.0/TCP 192.168.0.106;branch=z9hG4bK854f.b305c913.0;i=19 Via: SIP/2.0/TCP 192.168.0.89;rport=37260;branch=z9hG4bK854f.dac34f77.0;i=a Via: SIP/2.0/TLS 192.168.0.126:62399;branch=z9hG4bK-d8754z-51f50d6cfa997da7-1---d8754z-;rport =1876 To: "+497118113608227"<sip:+497118113608227@192.168.0.106>;tag=15c25277 From: <sip:+497118113608226@192.168.0.106>;tag=ba3448a0 Call-ID: ZjdiMWY5NTYxMTMyN2Q5NTkwOWVmZWExOTEwMDhjYzQ. CSeq: 2 BYE Server: kamailio (3.0.0 (i386/linux)) Content-Length: 0 [truncated] Warning: 392 192.168.0.89:5060 "Noisy feedback tells: pid=10378 req_src_ip=192.168.0.106 req_src_port=50445 in_uri=sip:+497118113608227@192.168.0.89:37260;transport=TLS out_uri=sip:+497118113608227@192.168.0.89:37260;transport Do you have any suggestions? Thank you very much in advance! Regards Andreas

1 0

[Kamailio-Users] Sip MESSAGE
by Abdul Hakeem 04 Feb '10

04 Feb '10

Hello, Does anyone knows if Kamalito supports MESSAGE method & where I can find the documentation or API's ? Regards, Abdul Hakeem

6 18

[Kamailio-Users] new module: mqueue
by Elena-Ramona Modroiu 04 Feb '10

04 Feb '10

Hi, few details about the new module mqueue. It provides a generic message queue for SIP Router inter process communication. Items in the queue are pairs of (key, value), both string. The items are consumed in the order they were added in the queue (first in first out). More details at: http://sip-router.org/docbook/sip-router/branch/master/modules/mqueue/mqueu… http://sip-router.org/wiki/cookbooks/pseudo-variables/devel#mqueue_module_p… The module is handy to use for time consuming and/or blocking operations (eg, email notifications). Not to hold the SIP worker process, you can add an item in a queue that is going to be consumed by another process (like timer processes created via rtimer module). Best regards, Ramona

1 0

[Kamailio-Users] [kamailio-users] can't connect with remote database
by Chandrakant Solanki 04 Feb '10

04 Feb '10

Hi I have 3 server with 172.16.0.10/13/14 IP address. My DB is located for 172.16.0.10. I tried to connect mysql from terminal, it works great. But when I start kamailio it gives me following error.. *kamailio.cfg* loadmodule "usrloc.so" ----- ----- ----- modparam("usrloc", "socket_column", "socket") modparam("usrloc", "use_domain", 0) modparam("usrloc", "desc_time_order", 0) modparam("usrloc", "timer_interval", 60) modparam("usrloc", "db_url", "mysql://openser:openserrw@172.16.0.10/openser ") *error.... *Feb 4 17:10:53 localhost /usr/local/sbin/kamailio[28792]: ERROR:core:db_do_init: could not add connection to the pool Feb 4 17:10:53 localhost /usr/local/sbin/kamailio[28792]: ERROR:usrloc:child_init: child(8): failed to connect to database Feb 4 17:10:53 localhost /usr/local/sbin/kamailio[28792]: ERROR:core:init_mod_child: failed to initializing module usrloc, rank 8 Feb 4 17:10:53 localhost /usr/local/sbin/kamailio[28792]: ERROR:core:main_loop: init_child failed for UDP listener Feb 4 17:10:53 localhost /usr/local/sbin/kamailio[28793]: ERROR:db_mysql:db_mysql_new_connection: driver error: Can't connect to MySQL server on '172.16.0.10' (4)* * -- Regards, Chandrakant Solanki

2 1

[Kamailio-Users] break a call?
by BERGANZ Francois 04 Feb '10

04 Feb '10

Hello, I know that we can break a call with sl_reply(). But, in the on_reply route, how can I break a call if I receive a 3XX (I cant use a sl_reply() function!) ? Thank you

2 2

[Kamailio-Users] xlog enhancements
by Elena-Ramona Modroiu 04 Feb '10

04 Feb '10

Hi, I added two new functions to xlog (modules_k): - xlogl(level, message) - xdbgl(message) They are similar to the existing functions, in addition they print the config line at the beginning of the message. The printed value is: "cfglineno:message" In this way you can spot easily in the logs where the function was used to print a particular message. http://sip-router.org/docbook/sip-router/branch/master/modules_k/xlog/xlog.… Regards, Ramona

3 5

[Kamailio-Users] Loose Route / Re-Invite
by Brandon Armstead 04 Feb '10

04 Feb '10

Hello everyone, I'm just curious as to see what some of you guys do in regards to handling a Re-Invite that comes back downstream to a NATTED UAC. For example, call scenario: UAC -> Kamailio (Fix Nated Contact) -> PSTN Re-Invite Occurs: PSTN -> Kamailio -> UAC UAC (200 OK w/ NAT RFC1918 contact) -> Kamailio (branch flags at this point are not notifying of NAT, due to the downstream direction of the INVITE, so RFC1918 address exists, but does not fix_nated_contact) -> PSTN PSTN does not appropriately ACK. So, what are your guys solutions for solving this problem? Is the best way to add an attribute onto the contact header sent in original INVITE? Are there other ways of handling? What is the best, cleanest method. Possible to handle with AVP's? Thanks in advanced for all of your input! Sincerely, Brandon

6 22

[Kamailio-Users] [OT] acabrera@sintys.gov.ar is away, did you know?
by Iñaki Baz Castillo 04 Feb '10

04 Feb '10

Hi, am I the only person receiving an auto-reply mail from acabrera(a)sintys.gov.ar with subject "Ausente" ("Away") for each mail sent to this list (and perhaps to others)? I've already sent him a direct mail. However, why do people use such auto- reply stuf in mail?? this is mail, an asynchronous communication, the receipt can read the mail whenever he prefers, not need to tell me "I'm away now". grrrr -- Iñaki Baz Castillo <ibc(a)aliax.net>

3 3

Re: [Kamailio-Users] Loose Route / Re-Invite (brandon@cryy.com)
by Brandon Armstead 03 Feb '10

03 Feb '10

Hello, Please refer to sip trace: http://pastebin.org/86010. On LINE 294, PSTN sends the Re-INVITE On LINE 378, REGISTRAR sends 200 OK to SIP SBC (with RFC 1918 Address, that is being relayed from the UAC that also sends this same address upon 200 OK of the Re-Invite). Let me know if this makes sense, this trace was taken on the SBC.

4 5

[Kamailio-Users] Registration delays when using Kamailio proxy
by Vikram Ragukumar 03 Feb '10

03 Feb '10

Hello, I am using an x-lite softphone to register with my SIP domain, (a) Without an outbound proxy - Registration is successful and takes about 3 seconds (b) With an outbound proxy - Registration is successful but takes nearly 15 seconds I briefly describe below the sequence of SIP messages while using the outbound proxy Register softphone -> proxy Register proxy -> SIP server Register softphone -> proxy 407 Proxy authentication reqd. SIP server -> proxy Register softphone -> proxy 407 Proxy authentication reqd. proxy -> softphone Register softphone -> proxy (With Digest response) Register proxy -> SIP server (With Digest response) 200 OK Sip server -> proxy Register softphone -> proxy (With Digest response) I am attaching a log with wireshark captures that show SIP messages exchanged between the SIP server,SIP proxy and the x-lite softphone. The log shows several messages being duplicated (REGISTER, 200 OK) 1) Why does the softphone continue to send REGISTER messages after receiving a 200 OK response ? (almost 15 repetitions of REGISTER after receiving 200 OK) 2) What is the reason for the delay in registration times with/without the proxy ? Thanks and Regards, Vikram. No. Time Source Destination Protocol Info 1 0.000000 ab.cde.fgh.ijx(xlite) ab.cde.fgh.ijk(proxy) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 1 (611 bytes on wire, 611 bytes captured) Ethernet II, Src: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: 33374 (33374), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-c252300b156adb6c-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 1 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 3 0.839564 ab.cde.fgh.ijk(proxy) lm.nop.qrs.tu(server) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 3 (722 bytes on wire, 722 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: Unispher_40:b5:39 (00:90:1a:40:b5:39) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK31c8.d11a2c71.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;received=ab.cde.fgh.ijx(xlite);branch=z9hG4bK-d8754z-c252300b156adb6c-1---d8754z-;rport=33374 Max-Forwards: 69 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 1 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 P-hint: outbound No. Time Source Destination Protocol Info 4 0.952097 lm.nop.qrs.tu(server) ab.cde.fgh.ijk(proxy) SIP Status: 407 Proxy Authentication Required (0 bindings) Frame 4 (555 bytes on wire, 555 bytes captured) Ethernet II, Src: Unispher_40:b5:39 (00:90:1a:40:b5:39), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 407 Proxy Authentication Required Message Header CSeq: 1 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK31c8.d11a2c71.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-c252300b156adb6c-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030240100052 Proxy-Authenticate: DIGEST realm="VoipSwitch", nonce="126513605203001203402405205305" Content-Length: 0 No. Time Source Destination Protocol Info 5 1.404504 ab.cde.fgh.ijk(proxy) lm.nop.qrs.tu(server) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 5 (722 bytes on wire, 722 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: Unispher_40:b5:39 (00:90:1a:40:b5:39) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK31c8.d11a2c71.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;received=ab.cde.fgh.ijx(xlite);branch=z9hG4bK-d8754z-c252300b156adb6c-1---d8754z-;rport=33374 Max-Forwards: 69 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 1 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 P-hint: outbound No. Time Source Destination Protocol Info 6 1.517292 lm.nop.qrs.tu(server) ab.cde.fgh.ijk(proxy) SIP Status: 407 Proxy Authentication Required (0 bindings) Frame 6 (555 bytes on wire, 555 bytes captured) Ethernet II, Src: Unispher_40:b5:39 (00:90:1a:40:b5:39), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 407 Proxy Authentication Required Message Header CSeq: 1 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK31c8.d11a2c71.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-c252300b156adb6c-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030240100053 Proxy-Authenticate: DIGEST realm="VoipSwitch", nonce="126513605303001203402405305305" Content-Length: 0 No. Time Source Destination Protocol Info 7 1.522829 ab.cde.fgh.ijx(xlite) ab.cde.fgh.ijk(proxy) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 7 (611 bytes on wire, 611 bytes captured) Ethernet II, Src: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: 33374 (33374), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-c252300b156adb6c-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 1 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 No. Time Source Destination Protocol Info 8 2.522300 ab.cde.fgh.ijk(proxy) ab.cde.fgh.ijx(xlite) SIP Status: 407 Proxy Authentication Required (0 bindings) Frame 8 (492 bytes on wire, 492 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)) User Datagram Protocol, Src Port: sip (5060), Dst Port: 33374 (33374) Session Initiation Protocol Status-Line: SIP/2.0 407 Proxy Authentication Required Message Header CSeq: 1 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-c252300b156adb6c-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030240100052 Proxy-Authenticate: DIGEST realm="VoipSwitch", nonce="126513605203001203402405205305" Content-Length: 0 No. Time Source Destination Protocol Info 9 2.730896 ab.cde.fgh.ijx(xlite) ab.cde.fgh.ijk(proxy) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 9 (801 bytes on wire, 801 bytes captured) Ethernet II, Src: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: 33374 (33374), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-4248775550708257-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605203001203402405205305",uri="sip:lm.nop.qrs.tu(server)",response="2c0d7d2f3b4cc218792ebef30e0eb2e6",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 No. Time Source Destination Protocol Info 10 2.796109 ab.cde.fgh.ijk(proxy) ab.cde.fgh.ijx(xlite) SIP Status: 407 Proxy Authentication Required (0 bindings) Frame 10 (492 bytes on wire, 492 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)) User Datagram Protocol, Src Port: sip (5060), Dst Port: 33374 (33374) Session Initiation Protocol Status-Line: SIP/2.0 407 Proxy Authentication Required Message Header CSeq: 1 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-c252300b156adb6c-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030240100052 Proxy-Authenticate: DIGEST realm="VoipSwitch", nonce="126513605203001203402405205305" Content-Length: 0 No. Time Source Destination Protocol Info 11 3.308767 ab.cde.fgh.ijx(xlite) ab.cde.fgh.ijk(proxy) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 11 (801 bytes on wire, 801 bytes captured) Ethernet II, Src: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: 33374 (33374), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-4248775550708257-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605203001203402405205305",uri="sip:lm.nop.qrs.tu(server)",response="2c0d7d2f3b4cc218792ebef30e0eb2e6",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 No. Time Source Destination Protocol Info 12 4.099907 ab.cde.fgh.ijk(proxy) lm.nop.qrs.tu(server) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 12 (912 bytes on wire, 912 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: Unispher_40:b5:39 (00:90:1a:40:b5:39) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK01c8.2e6fe072.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;received=ab.cde.fgh.ijx(xlite);branch=z9hG4bK-d8754z-4248775550708257-1---d8754z-;rport=33374 Max-Forwards: 69 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605203001203402405205305",uri="sip:lm.nop.qrs.tu(server)",response="2c0d7d2f3b4cc218792ebef30e0eb2e6",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 P-hint: outbound No. Time Source Destination Protocol Info 13 4.216914 lm.nop.qrs.tu(server) ab.cde.fgh.ijk(proxy) SIP Status: 407 Proxy Authentication Required (0 bindings) Frame 13 (555 bytes on wire, 555 bytes captured) Ethernet II, Src: Unispher_40:b5:39 (00:90:1a:40:b5:39), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 407 Proxy Authentication Required Message Header CSeq: 2 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK01c8.2e6fe072.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-4248775550708257-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030240100055 Proxy-Authenticate: DIGEST realm="VoipSwitch", nonce="126513605503001203402405505305" Content-Length: 0 No. Time Source Destination Protocol Info 14 4.324392 ab.cde.fgh.ijx(xlite) ab.cde.fgh.ijk(proxy) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 14 (801 bytes on wire, 801 bytes captured) Ethernet II, Src: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: 33374 (33374), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-4248775550708257-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605203001203402405205305",uri="sip:lm.nop.qrs.tu(server)",response="2c0d7d2f3b4cc218792ebef30e0eb2e6",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 No. Time Source Destination Protocol Info 15 4.704708 ab.cde.fgh.ijk(proxy) lm.nop.qrs.tu(server) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 15 (912 bytes on wire, 912 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: Unispher_40:b5:39 (00:90:1a:40:b5:39) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK01c8.2e6fe072.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;received=ab.cde.fgh.ijx(xlite);branch=z9hG4bK-d8754z-4248775550708257-1---d8754z-;rport=33374 Max-Forwards: 69 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605203001203402405205305",uri="sip:lm.nop.qrs.tu(server)",response="2c0d7d2f3b4cc218792ebef30e0eb2e6",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 P-hint: outbound No. Time Source Destination Protocol Info 16 4.822244 lm.nop.qrs.tu(server) ab.cde.fgh.ijk(proxy) SIP Status: 407 Proxy Authentication Required (0 bindings) Frame 16 (555 bytes on wire, 555 bytes captured) Ethernet II, Src: Unispher_40:b5:39 (00:90:1a:40:b5:39), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 407 Proxy Authentication Required Message Header CSeq: 2 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK01c8.2e6fe072.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-4248775550708257-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030240100056 Proxy-Authenticate: DIGEST realm="VoipSwitch", nonce="126513605603001203402405605305" Content-Length: 0 No. Time Source Destination Protocol Info 17 5.710292 ab.cde.fgh.ijk(proxy) ab.cde.fgh.ijx(xlite) SIP Status: 407 Proxy Authentication Required (0 bindings) Frame 17 (492 bytes on wire, 492 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)) User Datagram Protocol, Src Port: sip (5060), Dst Port: 33374 (33374) Session Initiation Protocol Status-Line: SIP/2.0 407 Proxy Authentication Required Message Header CSeq: 2 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-4248775550708257-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030240100055 Proxy-Authenticate: DIGEST realm="VoipSwitch", nonce="126513605503001203402405505305" Content-Length: 0 No. Time Source Destination Protocol Info 18 5.724689 ab.cde.fgh.ijk(proxy) ab.cde.fgh.ijx(xlite) SIP Status: 407 Proxy Authentication Required (0 bindings) Frame 18 (492 bytes on wire, 492 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)) User Datagram Protocol, Src Port: sip (5060), Dst Port: 33374 (33374) Session Initiation Protocol Status-Line: SIP/2.0 407 Proxy Authentication Required Message Header CSeq: 2 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-4248775550708257-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030240100055 Proxy-Authenticate: DIGEST realm="VoipSwitch", nonce="126513605503001203402405505305" Content-Length: 0 No. Time Source Destination Protocol Info 19 5.832474 ab.cde.fgh.ijx(xlite) ab.cde.fgh.ijk(proxy) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 19 (801 bytes on wire, 801 bytes captured) Ethernet II, Src: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: 33374 (33374), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-316786162159173a-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 3 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605503001203402405505305",uri="sip:lm.nop.qrs.tu(server)",response="014a8ffc9e6cc551acc86b22f2c26c11",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 No. Time Source Destination Protocol Info 21 7.455368 ab.cde.fgh.ijk(proxy) lm.nop.qrs.tu(server) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 21 (912 bytes on wire, 912 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: Unispher_40:b5:39 (00:90:1a:40:b5:39) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK11c8.7f536395.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;received=ab.cde.fgh.ijx(xlite);branch=z9hG4bK-d8754z-316786162159173a-1---d8754z-;rport=33374 Max-Forwards: 69 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 3 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605503001203402405505305",uri="sip:lm.nop.qrs.tu(server)",response="014a8ffc9e6cc551acc86b22f2c26c11",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 P-hint: outbound No. Time Source Destination Protocol Info 22 7.457267 ab.cde.fgh.ijx(xlite) ab.cde.fgh.ijk(proxy) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 22 (801 bytes on wire, 801 bytes captured) Ethernet II, Src: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: 33374 (33374), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-316786162159173a-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 3 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605503001203402405505305",uri="sip:lm.nop.qrs.tu(server)",response="014a8ffc9e6cc551acc86b22f2c26c11",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 No. Time Source Destination Protocol Info 23 7.574533 lm.nop.qrs.tu(server) ab.cde.fgh.ijk(proxy) SIP Status: 200 OK (1 bindings) Frame 23 (539 bytes on wire, 539 bytes captured) Ethernet II, Src: Unispher_40:b5:39 (00:90:1a:40:b5:39), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 200 OK Message Header CSeq: 3 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK11c8.7f536395.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-316786162159173a-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030240100059 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d>;expires=60 Expires: 60 Content-Length: 0 No. Time Source Destination Protocol Info 24 8.355247 ab.cde.fgh.ijk(proxy) lm.nop.qrs.tu(server) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 24 (912 bytes on wire, 912 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: Unispher_40:b5:39 (00:90:1a:40:b5:39) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK11c8.7f536395.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;received=ab.cde.fgh.ijx(xlite);branch=z9hG4bK-d8754z-316786162159173a-1---d8754z-;rport=33374 Max-Forwards: 69 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d> To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 3 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605503001203402405505305",uri="sip:lm.nop.qrs.tu(server)",response="014a8ffc9e6cc551acc86b22f2c26c11",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 P-hint: outbound No. Time Source Destination Protocol Info 25 8.472891 lm.nop.qrs.tu(server) ab.cde.fgh.ijk(proxy) SIP Status: 200 OK (1 bindings) Frame 25 (539 bytes on wire, 539 bytes captured) Ethernet II, Src: Unispher_40:b5:39 (00:90:1a:40:b5:39), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 200 OK Message Header CSeq: 3 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bK11c8.7f536395.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-316786162159173a-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030241100000 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d>;expires=60 Expires: 60 Content-Length: 0 No. Time Source Destination Protocol Info 26 9.310268 ab.cde.fgh.ijk(proxy) ab.cde.fgh.ijx(xlite) SIP Status: 200 OK (1 bindings) Frame 26 (476 bytes on wire, 476 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)) User Datagram Protocol, Src Port: sip (5060), Dst Port: 33374 (33374) Session Initiation Protocol Status-Line: SIP/2.0 200 OK Message Header CSeq: 3 REGISTER Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-316786162159173a-1---d8754z-;rport=33374 From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. To: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=030240100059 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d>;expires=60 Expires: 60 Content-Length: 0 No. Time Source Destination Protocol Info 29 10.939788 ab.cde.fgh.ijx(xlite) ab.cde.fgh.ijk(proxy) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 29 (796 bytes on wire, 796 bytes captured) Ethernet II, Src: 1a:1b:1c:1d:1e:1f (1a:1b:1c:1d:1e:1f), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: ab.cde.fgh.ijx(xlite) (ab.cde.fgh.ijx(xlite)), Dst: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)) User Datagram Protocol, Src Port: 33374 (33374), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;branch=z9hG4bK-d8754z-075267174a75f03a-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d>;expires=0 To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 4 REGISTER Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605503001203402405505305",uri="sip:lm.nop.qrs.tu(server)",response="014a8ffc9e6cc551acc86b22f2c26c11",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 No. Time Source Destination Protocol Info 30 11.097051 ab.cde.fgh.ijk(proxy) lm.nop.qrs.tu(server) SIP Request: REGISTER sip:lm.nop.qrs.tu(server) Frame 30 (907 bytes on wire, 907 bytes captured) Ethernet II, Src: Supermic_bd:b9:bc (00:30:48:bd:b9:bc), Dst: Unispher_40:b5:39 (00:90:1a:40:b5:39) Internet Protocol, Src: ab.cde.fgh.ijk(proxy) (ab.cde.fgh.ijk(proxy)), Dst: lm.nop.qrs.tu(server) (lm.nop.qrs.tu(server)) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:lm.nop.qrs.tu(server) SIP/2.0 Message Header Via: SIP/2.0/UDP ab.cde.fgh.ijk(proxy);branch=z9hG4bKe0c8.73270ff2.0 Via: SIP/2.0/UDP ab.cde.fgh.ijx(xlite):50648;received=ab.cde.fgh.ijx(xlite);branch=z9hG4bK-d8754z-075267174a75f03a-1---d8754z-;rport=33374 Max-Forwards: 69 Contact: <sip:1234@ab.cde.fgh.ijx(xlite):50648;rinstance=0f34c912798e872d>;expires=0 To: "1234"<sip:1234@lm.nop.qrs.tu(server)> From: "1234"<sip:1234@lm.nop.qrs.tu(server)>;tag=cb57d146 Call-ID: Zjg5MTdhZjMyYTZlMzlmZTA2NjY4MDBhMjNhYjkyMDU. CSeq: 4 REGISTER Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Proxy-Authorization: Digest username="1234",realm="VoipSwitch",nonce="126513605503001203402405505305",uri="sip:lm.nop.qrs.tu(server)",response="014a8ffc9e6cc551acc86b22f2c26c11",algorithm=MD5 User-Agent: X-Lite release 1104o stamp 56125 Content-Length: 0 P-hint: outbound

4 5

[Kamailio-Users] protocol/port mismatch on BYE from Calle to Caller
by Arafath-uz-zaman khan 03 Feb '10

03 Feb '10

Hello All, I need a working example for sending all request to another sip server using kamailio. X-lite-->TLS(7161)-->Kamailio-->UDP(5060)-->SIP Server-->PSTN Number. i have attached my cfg file. The problem is when i dialed any pstn number everything working fine except the by msg. If the caller send BYE callee get hangup but if Calle send BYE caller never hangup the call. i got the following msg on my log file Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_msg: method: <BYE> Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_msg: uri: <sip:91131@192.168.10.2:5060> Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_msg: version: <SIP/2.0> Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: flags=2 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field: cseq <CSeq>: <1> <BYE> Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bk010213101521011481381407>; state=16 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_via: end of header reached, state=5 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: via found, flags=2 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: this is the first via Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:receive_msg: After parse_msg... Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:receive_msg: preparing to run routing scripts... Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: flags=100 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to_param: tag=b23c1531 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to: end of header reached, state=29 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to: display={"91131"}, ruri={sip:91131@192.168.10.2:5060} Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field: <To> [51]; uri=[sip:91131@192.168.10.2:5060] Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field: to body ["91131"<sip:91131@192.168.10.2:5060>] Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field: content_length=0 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field: found end of header Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:maxfwd:is_maxfwd_present: max_forwards header not found! Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:check_via_address: params 192.168.10.2, 192.168.10.2, 0 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: flags=80 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:siputils:has_totag: totag found Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: flags=200 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:rr:is_preloaded: is_preloaded: No Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: checking if host==us: 12==13 && [192.168.10.2] == [192.168.10.1] Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: checking if port 5060 matches port 5060 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: checking if host==us: 12==13 && [192.168.10.2] == [192.168.10.1] Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: checking if port 7161 matches port 5060 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: no match for: [192.168.10.2:5060] Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_aliases: no match for: [0:192.168.10.2:5060] Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:check_self: host != me Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: checking if host==us: 13==13 && [192.168.10.1] == [192.168.10.1] Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: checking if port 5060 matches port 5060 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: match found for: [192.168.10.1:5060] Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:check_self: host == me Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:rr:after_loose: Topmost route URI: 'sip:192.168.10.1;r2=on;lr=on;nat=yes' is me Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: checking if host==us: 13==13 && [192.168.10.1] == [192.168.10.1] Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: checking if port 7161 matches port 7161 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info: match found for: [192.168.10.1:7161] Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: flags=200 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field: found end of header Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:rr:find_next_route: No next Route HF found Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:rr:after_loose: no next URI found Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:rr:check_route_param: params are <;r2=on;lr=on;nat=yes> Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: flags=40 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to_param: tag=01021310150514813644546133 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to: end of header reached, state=29 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to: display={"911317434"}, ruri={sip:911317434@192.168.10.1:5060} Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:siputils:has_totag: totag found Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_newtran: transaction on entrance=0xffffffff Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: flags=ffffffffffffffff Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: flags=78 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_lookup_request: start searching: hash=850, isACK=0 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_lookup_request: proceeding to pre-RFC3261 transaction matching Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_lookup_request: no transaction found Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:run_reqin_callbacks: trans=0xb615b5f8, callback type 1, id 0 entered Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers: flags=78 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:mk_proxy: doing DNS lookup... *Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_send_socket: force_send_socket of different proto (1)! Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: WARNING:core:get_send_socket: protocol/port mismatch* Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:set_timer: relative timeout is 500000 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:insert_timer_unsafe: [4]: 0xb615b744 (46600000) Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:set_timer: relative timeout is 30 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:insert_timer_unsafe: [0]: 0xb615b760 (76) Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_relay_to: new transaction fwd'ed Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_unref: UNREF_UNSAFE: after is 0 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:destroy_avp_list: destroying list (nil) Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:receive_msg: cleaning up Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8809]: DBG:tm:utimer_routine: timer routine:4,tl=0xb615b744 next=(nil), timeout=46600000 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8809]: DBG:tm:retransmission_handler: retransmission_handler : request resending (t=0xb615b5f8, BYE sip:9 ... ) Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8809]: DBG:tm:set_timer: relative timeout is 1000000 Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8809]: DBG:tm:insert_timer_unsafe: [5]: 0xb615b744 (47600000) Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8809]: DBG:tm:retransmission_handler: retransmission_handler : done Feb 1 04:27:30 ser /usr/local/sbin/kamailio[8809]: DBG:tm:utimer_routine: timer routine:5,tl=0xb615b744 next=(nil), timeout=47600000 Feb 1 04:27:30 ser /usr/local/sbin/kamailio[8809]: DBG:tm:retransmission_handler: retransmission_handler : request resending (t=0xb615b5f8, BYE sip:9 ... ) Feb 1 04:27:30 ser /usr/local/sbin/kamailio[8809]: DBG:tm:set_timer: relative timeout is 2000000 Feb 1 04:27:30 ser /usr/local/sbin/kamailio[8809]: DBG:tm:insert_timer_unsafe: [6]: 0xb615b744 (49600000) Feb 1 04:27:30 ser /usr/local/sbin/kamailio[8809]: DBG:tm:retransmission_handler: retransmission_handler : done

2 3

[Kamailio-Users] the best editor?
by BERGANZ Francois 03 Feb '10

03 Feb '10

Hello all, what is the best edit tool to see quickly the right syntax ... ? which language to choose?

5 6

2025

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