sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

presence_dialoginfo- first NOTIFY - force_dummy_dialog
by evoip＠ukr.net 29 Aug '15

29 Aug '15

||Hello, we use Kamailio 4.2 with Presence_DIALOGINFO module for BLF notifications (blinking lamps on phone panel). Since version 4.1 Kamailio has a new module parametr " modparam("presence_dialoginfo", "force_dummy_dialog", 1)" - this option generate first NOTIFY to Subscribed phone (without PUBLISH message) and it's lamps became GREEN ( <state>terminated</state>). Without this module parametr the first NOTIFY won't be sent to phone and lamps will stay turned off until first PUBLISH will be handled by presence server. The first NOTIFY sip message with xml body look like this: NOTIFY sip:1005@22.22.22.22:1120 SIP/2.0. To: <sip:1005@11.11.11.11>;tag=867246696. From: <sip:9095@11.11.11.11>;tag=495949c4c25d687c77ca707bd10a0818-5171. CSeq: 2 NOTIFY. Call-ID: 662126467-5060-6(a)BJC.BGI.E.CDD. Route: <sip:10.60.1.3;r2=on;lr=on>, <sip:11.11.11.11;r2=on;lr=on>. Content-Length: 272. User-Agent: kamailio (4.2.3 (x86_64/linux)). Max-Forwards: 70. Event: dialog. Subscription-State: active;expires=600. Content-Type: application/dialog-info+xml. . <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="1" ух state="full" entity="sip:9095@10.60.1.3"> <dialog direction="recipient"> <state>terminated</state> </dialog> </dialog-info> Especially pay attention on XML body. But for some SIP phones this xml body with state = terminated is not enough to turn the BLF lamp on. (for example Grandstream phones). It requires one more or two more fields: "dialog id", "call-id". <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="28" state="full" entity="sip:9093@10.60.1.3"> <dialog id="830b4fd4-c75d-1233-ca9f-0050569560f4" call-id="830b4fd4-c75d-1233-ca9f-0050569560f4" direction="recipient"> <state>terminated</state> </dialog> </dialog-info> The question is how to modify this first NOTIFY XML body message to add "dialog id" and "call-id" to </dialog>. For example latest Kamailio Kazoo fixed that already. :) Kind Regards Ewgeny

4 8

unsupported route_type 64
by Admin 29 Aug '15

29 Aug '15

Hi, I am running Kamailio (4.4.0-dev2 (x86_64/linux)) with cgrates real-time billing application. At the end of a basic call (prepaid to postpaid), I receive the following error: ERROR:tmx [t_var.c:521]:pv_get_tm_reply_code():unsupported route_type 64 8(6740) DEBUG:tmx [t_var.c:526]:pv_get_tm_reply_code():reply code is <0> What does route_type 64 mean? I checked the archive posts (FS#456) and seemed to be fixed in branch 4.1 (part of 4.1.5). Thanks.

2 1

Parser error when enabling siptrace functionality
by Asgaroth 28 Aug '15

28 Aug '15

Hi All, I have a strange issue occuring, when I enable the siptrace functionality within the routing logic, I begin to get a bunch of parser error as show below. Is this normal behaviour or, more than likely, am I doing something wrong? I enable siptrace as follows: request_route { route("InitialMessageChecks"); sip_trace(); setflag(22); ... } event_route[tm:local-request] { sip_trace(); ... } When I enable this functions in the routing logic, I begin to see alot of the following messages in the log file: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 39) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàU{#002> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 39) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàUÞž#002> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 35) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàU #011#003> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#006y|#023ÄN˜#036ÂÕ#035múLàUÅ±#012> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> Is there any way I can disable seeing these messages? What are these messages? Any thoughts are appreciated. Thanks

2 4

kamailio_fifo
by Sven Juhkam 28 Aug '15

28 Aug '15

After updating kamailio I get: ERROR: Error opening Kamailio's FIFO /var/run/kamailio/kamailio_fifo ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name", "/var/run/kamailio/kamailio_fifo")' in your config ERROR: and also have loaded the mi_fifo module. Any solution? Best regards Sven

3 2

BLF state on register
by Loic Chabert 28 Aug '15

28 Aug '15

Hello everyone, I'm trying to reproduce BLF's asterisk fonctionnality with kamailio. With asterisk, on register, NOTIFY message has been sent to all suscribed users. So LED became green. How can i reproduce this function ? I have try to execute a "pua_set_publish()" on register route, but it's not work. My led stay "black", and no notify message has been sent. I have loaded presence, presence_xml, presence_mwi, presence_dialoginfo, pua, pua_dialoginfo, pua_usrloc. Any other module needed ? Thanks, Regards.

2 10

webrtc not working in different networks
by Achintha 28 Aug '15

28 Aug '15

Hi, I have configured kamailio 4.3.1 with mysql ,rtpproxy,websocket modules , then I tried to call through the two extensions using x-lite phone and get the capture. Call is connected. In that test rtp was going through the rtpproxy server, Then I configured jssip to test webrtc in this setup, call is connected I can communicate through the extensions both video and voice only in LAN. IN different networks call is connected but, voice is not hear (rtp not working). Kindly help me to configure this web rtc with kamailio. -- Best Regards.. Achintha

1 0

dmq_usrloc
by Kelvin Chua 28 Aug '15

28 Aug '15

is there any function to trigger replication? i enabled the module and dmq is working for my htables but usrloc is not replicating. "kamctl ul show" does not show anything i used ngrep to trace the KDMQ packets, i can see the frequent exchanges but nothing related to usrloc. am i doing something wrong? Kelvin Chua

3 13

multiple proxies
by Bruce Lefko 27 Aug '15

27 Aug '15

If I want to have multiple kamailio proxies in front of multiple media servers, can I balance them using plain old DNS behind a domain name? If I wanted a specific proxy to be notified about an entire SIP dialog I could set the record route to use the public IP of the proxy that received the initial INVITE. Could I leverage something like route53 tcp healthchecks to know if I should be failing over to another proxy?

3 2

multiple proxies
by Bruce Lefko 27 Aug '15

27 Aug '15

1 0

kamailio presence server using db_mongodb as database
by José Seabra 27 Aug '15

27 Aug '15

Hello all, I would like to test my presence server using db_mongodb as database server instead of using mysql, but i don't find any documentation explaining how i can configure mongodb database(data structure) for presence or even for the other kamailio modules. Can someone guide me in this setup? Best Regards -- Cumprimentos José Seabra

2 12

Jump to page:

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