- sr-users - kamailio.org

Amazon VPS, long UDP packets are seen by sniffer, but don't reach application
by Andrey Utkin 16 Feb '15

16 Feb '15

We experience strange networking issue, not exactly specific to kamailio, but still related to it. Rtpengine's "ng" interface uses UDP. Protocol messages contains SDP, and for encrypted video call those messages exceed 1500 bytes. Everything works fine within localhost, but when rtpengine and Kamailio are on different hosts, and when hosts are Amazon-hosted, we have trouble. This is experienced with l3.large, t2.micro with Ubuntu 14. I believe we don't have any special settings over system … [View More]defaults. We send a large datagram from remote host, e.g. with such trivial app in python: import socket UDP_IP = "123.123.123.123" # remote host IP UDP_PORT = 33333 MESSAGE = """ .....0010......0020......0030......0040......0050......0060......0070......0080......0090......0100 .....0110......0120......0130......0140......0150......0160......0170......0180......0190......0200 .....0210......0220......0230......0240......0250......0260......0270......0280......0290......0300 .....0310......0320......0330......0340......0350......0360......0370......0380......0390......0400 .....0410......0420......0430......0440......0450......0460......0470......0480......0490......0500 .....0510......0520......0530......0540......0550......0560......0570......0580......0590......0600 .....0610......0620......0630......0640......0650......0660......0670......0680......0690......0700 .....0710......0720......0730......0740......0750......0760......0770......0780......0790......0800 .....0810......0820......0830......0840......0850......0860......0870......0880......0890......0900 .....0910......0920......0930......0940......0950......0960......0970......0980......0990......1000 .....1010......1020......1030......1040......1050......1060......1070......1080......1090......1100 .....1110......1120......1130......1140......1150......1160......1170......1180......1190......1200 .....1210......1220......1230......1240......1250......1260......1270......1280......1290......1300 .....1310......1320......1330......1340......1350......1360......1370......1380......1390......1400 .....1410......1420......1430......1440......1450......1460......1470......1480......1490......1500 .....1510......1520......1530......1540......1550......1560......1570......1580......1590......1600 .....1610......1620......1630......1640......1650......1660......1670......1680......1690......1700 .....1710......1720......1730......1740......1750......1760......1770......1780......1790......1800 .....1810......1820......1830......1840......1850......1860......1870......1880......1890......1900 .....1910......1920......1930......1940......1950......1960......1970......1980......1990......2000""" print "UDP target IP:", UDP_IP print "UDP target port:", UDP_PORT print "message:", MESSAGE sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) sock.sendto(MESSAGE, (UDP_IP, UDP_PORT)) Then we listen on that port with such trivial python app: import socket UDP_IP = "172.31.4.102" # local ip UDP_PORT = 33333 sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) sock.bind((UDP_IP, UDP_PORT)) while True: data, addr = sock.recvfrom(0x10000) print "received message:", data Meanwhile, we monitor the traffic with e.g. ngrep: ngrep -t -e -d any -W byline -O large_udp.pcap port 33333 or '(ip[6:2]' '&' '0x1fff)' '!=' '0' (the part after "or" catches segments of segmented packets) About the host: # uname -a Linux hostname 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Also linux-image-3.13.0-36-generic and linux-image-3.13.0-45-generic behave in same way. What we see: - ngrep shows the packets with correct contents. All segments are delivered. - application doesn't get any data at all Rarely dmesg shows such messages: [ 102.161679] UDP: bad checksum. From 123.123.123.124:56439 to 172.31.4.102:33333 ulen 2008 but it is logged really rarely, so this is surely not what happens on every packet transmission. This test works fine on e.g. cheapest DigitalOcean VPS. I am concerned with this issue because rtpengine software has UDP interface. So on Amazon hosts this interface works only within localhost, and I cannot distribute software to different nodes. Any thoughts? What's wrong, how to fix? -- Andrey Utkin [View Less]

2 4

Log Media IP
by Ryan Brindley 16 Feb '15

16 Feb '15

Hey community, What's the best way to pull out the media ip from the SIP INVITE body (for logging)? Ryan Brindley

2 1

Event reg - questions
by Stefan Ljung 16 Feb '15

16 Feb '15

I made a test configuration for trying the pua_regEvent module. There were two things I want to ask about. First - when the SUBSCRIBE to event 'reg' following a UEs registration to the Kamailio is responded with a NOTIFY - there was no body in the NOTIFY. I expected a XML body with registration status. Second - When the UE re-registers to Kamailio - I expected a NOTIFY to be send on the existing 'reg' subscription, but nothing happened. Or am I missing some configuration ? Here's some of the … [View More]

2 1

dialog module 4.2 REFER
by Uri Shacked 16 Feb '15

16 Feb '15

Hi, I am trying to use dlg_refer. I set the side to refer and the final destination. But, the contact header of the refer stays "controler(a)kamailio.org". So, the refer fails. Is it a bug or should i change the contact header by myself before doing the dlg_refer? same with the dlg_bridge..... Cheers, Uri

3 2

Using dialog_ng
by Shane Harrison 15 Feb '15

15 Feb '15

Hi all, I think the lack of response to my previous thread is probably because it was too complicated. I have now narrowed my problem down after further archive readings . I am trying to use the dialog_ng module along with the ims_charging_module. Upon reception of an INVITE, a call to the Ro_CCR() from the request_route script is made. That function does a check that the dialog record exists (binds to dialog module and does a "get_dlg(msg)" call) - this fails i.e. dialog is not found. … [View More]

3 7

rtpengine - Error when sending message. Error: Invalid argument
by Amit Patkar 14 Feb '15

14 Feb '15

Hi I am getting error with rtpengine. Running Kamailio 4.2.3 I am trying to call from conventional SIP client to WebRTC client Google Chrome v38.0.2125.104 Firefox v33.0 Using sipML5 as WebRTC client root@rtcpbx:/home/avhan# /usr/sbin/rtpengine --interface=127.0.0.1\!192.168.2.161 --listen-ng=7722 --pidfile=/var/run/ngcp-rtpengine-daemon.pid --tos=184 --table=42 --foreground --log-level=7 --log-stderr INFO: Generating new DTLS certificate DEBUG: Dump of DTLS certificate: DEBUG: --- -----… [View More]BEGIN CERTIFICATE----- DEBUG: --- MIIBpDCCAQ2gAwIBAAIJAIH/X+7BeV8gMA0GCSqGSIb3DQEBBQUAMBQxEjAQBgNV DEBUG: --- BAMTCXJ0cGVuZ2luZTAeFw0xNTAyMTMxMjM5MjJaFw0xNTAzMTYxMjM5MjJaMBQx DEBUG: --- EjAQBgNVBAMTCXJ0cGVuZ2luZTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA DEBUG: --- tfOduffYlJeuTeA6GRRKpeuUougYgu33QKjPZ9RuQNl6AIsmJQrqPJ9bTv93BlNd DEBUG: --- I/COq89SRxxjhAHEw6v3F283/lZAitySVa+TazbpZrwKsWbfPTXtLMC5oJvEPUr/ DEBUG: --- 8xcX+rnImLHZPrECMZj4pjSI6htclKok+YFf3incSmECAwEAATANBgkqhkiG9w0B DEBUG: --- AQUFAAOBgQBA2zHxUAv4J/dRLMboF9y3h6hQNnoEQNDwlmE+M4bBbOAxNYNxpmy3 DEBUG: --- mmZ54GBZFbvIWO4MVYrGiEMXBsQ3LSHo+MeExtY7Jq1RbXHU+DT/hHg5DGHHeFyr DEBUG: --- d46TUaHIFG/XhKSAaaCX1EbqtezMaUWrJw+mtOfzfZMEVzMP72CmiA== DEBUG: --- -----END CERTIFICATE----- DEBUG: Dump of DTLS private key: DEBUG: --- -----BEGIN PRIVATE KEY----- DEBUG: --- MIICdgIBADANBgkqhkiG9w0BAQEFAASCAmAwggJcAgEAAoGBALXznbn32JSXrk3g DEBUG: --- OhkUSqXrlKLoGILt90Coz2fUbkDZegCLJiUK6jyfW07/dwZTXSPwjqvPUkccY4QB DEBUG: --- xMOr9xdvN/5WQIrcklWvk2s26Wa8CrFm3z017SzAuaCbxD1K//MXF/q5yJix2T6x DEBUG: --- AjGY+KY0iOobXJSqJPmBX94p3EphAgMBAAECgYBJG9sLZz/Z7Nx3pBoUC6g25OKz DEBUG: --- VmjK6w0HKQ01XhDy869m2oJ4LduSgkFxC4rqusJY94aMGGCp/AkseH10VfuQ/Dn4 DEBUG: --- 6Zv9l8xGlprRmW0do6w0AR7F5JpcuoMT7ae8Jf7hAJpa//LbAg2s0lJBMofIUtd/ DEBUG: --- 0xs0y9uX/stV9hRAAQJBAOUocKdTbN1J9W6EB+r64/QBPxB7jhbs8J76RRfCjhE2 DEBUG: --- CS8JRBajMJJ3XgjOWQuh44xmydGCJeSSisDKsONVpgECQQDLQ6QCHYJxeXJ0R4w9 DEBUG: --- 5XqUEQhb03GlwoTIas3YQfJJyk/zKnQAkBKwjwatrNEldCGBOCOgeQhTERPwSxcx DEBUG: --- kGRhAkBxjmSkxjaAQhIZPdwemU00sRlrNY7n1Wo3nZV3fLWh2cEbSeAvx5ZePkCe DEBUG: --- 5IJDvWlhPd5sr63PYr7XYpndTagBAkEAj27Nvwhf0f8nOtJ6LftPAkj6owGUAqo+ DEBUG: --- 1MY5N09hz5xJyoe8j+EaryheSBPZChrmwa6BxW1i6Gr2rOvwE/OWQQJACxjVriL8 DEBUG: --- mKFqDLN1rQuDqyA6f0jSaxuPsA3TGCcEbgw4e8hQD9pFJ6NK7/X/UeqqWsW0sAZS DEBUG: --- mNrnLY9VvZPSpw== DEBUG: --- -----END PRIVATE KEY----- INFO: Startup complete, version 3.3.0.0+0~mr3.8.0.0 DEBUG: Adding a proxy for control ng stats:127.0.0.1 INFO: Got valid command from 127.0.0.1:60075: offer - { "sdp": "v=0 o=- 28314700 28314700 IN IP4 192.168.2.18 s=http://www.portsip.com c=IN IP4 192.168.2.18 t=0 0 m=audio 20670 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv ", "ICE": "force", "flags": [ "trust-address" ], "replace": [ "origin", "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "FjDYirMD4b8ldLCQFrUMaw..", "received-from": [ "IP4", "192.168.2.18" ], "from-tag": "7a3b9012", "command": "offer" } NOTICE: [FjDYirMD4b8ldLCQFrUMaw..] Creating new call DEBUG: [FjDYirMD4b8ldLCQFrUMaw..] Opened ports 30000..30001 for media relay DEBUG: [FjDYirMD4b8ldLCQFrUMaw..] Opened ports 30010..30011 for media relay INFO: [FjDYirMD4b8ldLCQFrUMaw..] Returning to SIP proxy: d3:sdp669:v=0 o=- 28314700 28314700 IN IP4 192.168.2.161 s=http://www.portsip.com c=IN IP4 192.168.2.161 t=0 0 a=ice-lite m=audio 30000 RTP/SAVPF 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=rtcp:30001 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:JBeKZmgOzhC3A5Ays2nm4Jx3GqSbsoVStGSjSFL/ a=setup:actpass a=fingerprint:sha-1 CE:47:48:60:04:D0:A5:D7:FD:00:89:6E:8F:D9:25:48:9D:2F:B9:89 a=ice-ufrag:bMtYwXGC a=ice-pwd:q053zJtRE8bxgCEu3eebdaqoWSmr a=candidate:EqkUFjVat8drCK70 1 UDP 2130706431 192.168.2.161 30000 typ host a=candidate:EqkUFjVat8drCK70 2 UDP 2130706430 192.168.2.161 30001 typ host 6:result2:oke INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: Got valid command from 127.0.0.1:42832: ping - { "command": "ping" } INFO: Returning to SIP proxy: d6:result4:ponge INFO: Got valid command from 127.0.0.1:35595: offer - { "sdp": "v=0 o=- 28373892 28373892 IN IP4 192.168.2.18 s=http://www.portsip.com c=IN IP4 192.168.2.18 t=0 0 m=audio 20674 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv ", "ICE": "force", "flags": [ "trust-address" ], "replace": [ "origin", "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "fJTfptxXKrVoGdalt_2MMA..", "received-from": [ "IP4", "192.168.2.18" ], "from-tag": "bd78da3f", "command": "offer" } NOTICE: [fJTfptxXKrVoGdalt_2MMA..] Creating new call DEBUG: [fJTfptxXKrVoGdalt_2MMA..] Opened ports 30022..30023 for media relay DEBUG: [fJTfptxXKrVoGdalt_2MMA..] Opened ports 30044..30045 for media relay INFO: [fJTfptxXKrVoGdalt_2MMA..] Returning to SIP proxy: d3:sdp669:v=0 o=- 28373892 28373892 IN IP4 192.168.2.161 s=http://www.portsip.com c=IN IP4 192.168.2.161 t=0 0 a=ice-lite m=audio 30022 RTP/SAVPF 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=rtcp:30023 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:YUVDWqqE+RNOPLu4d1J81/gee3OY8tnfGSjc2zjB a=setup:actpass a=fingerprint:sha-1 CE:47:48:60:04:D0:A5:D7:FD:00:89:6E:8F:D9:25:48:9D:2F:B9:89 a=ice-ufrag:1d16gzNH a=ice-pwd:qpNBX4eBwfNKq0TPpNHLeuMdHOjX a=candidate:EqkUFjVat8drCK70 1 UDP 2130706431 192.168.2.161 30022 typ host a=candidate:EqkUFjVat8drCK70 2 UDP 2130706430 192.168.2.161 30023 typ host 6:result2:oke INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw..] Closing call due to timeout INFO: [FjDYirMD4b8ldLCQFrUMaw..] Final packet stats: INFO: [FjDYirMD4b8ldLCQFrUMaw..] --- Tag '', created 1:06 ago, in dialogue with '(none)' INFO: [FjDYirMD4b8ldLCQFrUMaw..] ------ Media #1, port 30000 <> [::]:0 , 6 p, 600 b, 0 e, 1423917572 last_packet INFO: [FjDYirMD4b8ldLCQFrUMaw..] ------ Media #1, port 30001 <> [::]:0 (RTCP), 6 p, 600 b, 0 e, 1423917572 last_packet INFO: [FjDYirMD4b8ldLCQFrUMaw..] --- Tag '7a3b9012', created 1:06 ago, in dialogue with '' INFO: [FjDYirMD4b8ldLCQFrUMaw..] ------ Media #1, port 30010 <> 192.168.2.18:20670, 0 p, 0 b, 0 e, 1423917566 last_packet INFO: [FjDYirMD4b8ldLCQFrUMaw..] ------ Media #1, port 30011 <> 192.168.2.18:20671 (RTCP), 0 p, 0 b, 0 e, 1423917566 last_packet INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: Got valid command from 127.0.0.1:36029: answer - { "sdp": "v=0 o=Mozilla-SIPUA-33.0 15128 1 IN IP4 0.0.0.0 s=Doubango Telecom - firefox t=0 0 a=ice-ufrag:524a14d8 a=ice-pwd:f23ceb82b6f9a86a2c1f180a013a9ff3 a=fingerprint:sha-256 6A:5D:49:F6:7B:FE:5B:5E:23:43:EE:31:43:20:46:C0:E8:12:B7:AD:AB:A2:09:66:94:55:42:E2:6B:D3:D9:63 m=audio 7449 UDP/TLS/RTP/SAVPF 0 101 c=IN IP4 192.168.2.18 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=setup:active a=candidate:0 1 UDP 2128609535 192.168.2.18 7449 typ host a=candidate:0 2 UDP 2128609534 192.168.2.18 7450 typ host ", "ICE": "remove", "flags": [ "trust-address" ], "replace": [ "origin", "session-connection" ], "transport-protocol": "RTP/AVP", "call-id": "fJTfptxXKrVoGdalt_2MMA..", "received-from": [ "IP4", "192.168.2.18" ], "from-tag": "bd78da3f", "to-tag": "mUTC7w3qs5ka6fJWKCiM", "command": "answer" } INFO: [fJTfptxXKrVoGdalt_2MMA..] Returning to SIP proxy: d3:sdp240:v=0 o=Mozilla-SIPUA-33.0 15128 1 IN IP4 0.0.0.0 s=Doubango Telecom - firefox t=0 0 m=audio 30044 RTP/AVP 0 101 c=IN IP4 192.168.2.161 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=rtcp:30045 6:result2:oke *DEBUG: [fJTfptxXKrVoGdalt_2MMA.. port 30044] Error when sending message. Error: Invalid argument WARNING: [fJTfptxXKrVoGdalt_2MMA.. port 30044] Write error on RTP socket: Invalid argument* INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] Final packet stats: INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] --- Tag 'mUTC7w3qs5ka6fJWKCiM', created 0:13 ago, in dialogue with 'bd78da3f' INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] ------ Media #1, port 30022 <> 192.168.2.18:7449 , 7 p, 700 b, 0 e, 1423917638 last_packet INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] ------ Media #1, port 30023 <> 192.168.2.18:7450 (RTCP), 7 p, 700 b, 0 e, 1423917638 last_packet INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] --- Tag 'bd78da3f', created 0:13 ago, in dialogue with 'mUTC7w3qs5ka6fJWKCiM' INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] ------ Media #1, port 30044 <> 192.168.2.18:20674, 0 p, 0 b, 1 e, 1423917626 last_packet INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] ------ Media #1, port 30045 <> 192.168.2.18:20675 (RTCP), 0 p, 0 b, 0 e, 1423917626 last_packet Regards Amit [View Less]

2 2

Kamailio and rtpengine
by Marc Soda 14 Feb '15

14 Feb '15

How does Kamailio load balance traffic to rtpengine? Is it load based, round robin, etc? The module makes mention of this but I don't see how it works. Also, it talks about weighting the proxies. How is that accomplished? Thanks, Marc

3 2

WebRTC to PSTN call, proxied through Kamailio
by Rahul MathuR 14 Feb '15

14 Feb '15

Hello gents, I was trying my hands on getting a successful RTCweb call (JSsip, since Peter Dunkley mentioned that he's been using JSsip for most of the testing scenarios..) to PSTN, making my kamailio as proxy + protocol converter (sip over web-sockets to sip over udp). And yes, I've referred Carlos' config; the main problem is I get 'Bad Media Description' error in Google Chromium (Version 40.0.2214.111 m) & my SIP server even sends 200 OK, but my phone doesn't ring. To make it worse, I … [View More]

3 6

Issues after Ubuntu Server Update and WebRTC
by Manuel Camargo Lominchar 13 Feb '15

13 Feb '15

>* Is the SIP signaling still going fine via websocket? Do you get callee *>* ringing? *>>* Cheers, *>* Daniel* Hello Daniel Actually SIP signalling goes perfect, and i can see in RTP asterisk log that RTP packets are being sent, so I suppose there is something stuck somewhere in RTP maybe related with RTP Engine >Hi, > >If you are using rtpengine for the rtp you might have to upgrade to a >newer version. > >On my system crypto negotiation in … [View More]

1 1

change_reply_status() 415 -> 200 change
by Juha Heinanen 13 Feb '15

13 Feb '15

i tried to use change_reply_status() to change 415 to 200, but got: ERROR: textopsx [textopsx.c:283]: change_reply_status_f(): ERROR: textops: the class of provisional or positive final replies cannot be changed textopsx/README does not mention anything about what can or cannot be changed. why is it that the above change cannot be made? -- juha

2 1

Issues after Ubuntu Server Update and WebRTC
by Manuel Camargo Lominchar 13 Feb '15

13 Feb '15

This might be a weird question I've been operating for some months with my kam + asterisk + webrtc sipml5 based system inside an Ubuntu Server Today I had the idea to apt-get upgrade my system and... now the whole system webrtc communication service is dead Here is the VAST list of packages updated... But I cannot figure out who is the "destroyer" package. No prompts appeared during the update so I believe no config files have been updated I'm trying to debug but I cant find a solution The … [View More]handshake is done, and in Wireshark the only thing I find is that no UDP (RTP) packages are being processed, but in the SIP log I can see ICE candidates and all process is done I tried to do a direct SIP connection without WebRTC, and it worked pretty fine, so this have something to do with maybe crypt libs, or something to do with kamailio and imcompatibilities with one of this packages. Kamailio Version: # kamailio -v version: kamailio 4.1.5 (x86_64/linux) 2b3d4b flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_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, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 2b3d4b compiled on 14:39:42 Aug 28 2014 with gcc 4.8.2 Any ideas of where to start digging? Start-Date: 2015-02-12 14:40:19 Install: linux-image-extra-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), linux-image-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), linux-headers-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), linux-headers-3.13.0-45:amd64 (3.13.0-45.74, automatic) Upgrade: bind9-host:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), python3-problem-report:amd64 (2.14.1-0ubuntu3.5, 2.14.1-0ubuntu3.6), mime-support:amd64 (3.54ubuntu1, 3.54ubuntu1.1), liblwres90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), apt:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), libevent-2.0-5:amd64 (2.0.21-stable-1ubuntu1, 2.0.21-stable-1ubuntu1.14.04.1), libsystemd-login0:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), linux-headers-generic:amd64 (3.13.0.37.44, 3.13.0.45.52), mysql-server-core-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), ppp:amd64 (2.4.5-5.1ubuntu2, 2.4.5-5.1ubuntu2.1), mysql-server-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), multiarch-support:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libdns100:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), krb5-multidev:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), mysql-client-core-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), libisccfg90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), systemd-services:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), apt-transport-https:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), procps:amd64 (3.3.9-1ubuntu2, 3.3.9-1ubuntu2.2), libbind9-90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), tcpdump:amd64 (4.5.1-2ubuntu1, 4.5.1-2ubuntu1.1), dbus:amd64 (1.6.18-0ubuntu4.2, 1.6.18-0ubuntu4.3), libgssapi-krb5-2:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libapache2-mod-php5:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), php5-mysql:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), python-urllib3:amd64 (1.7.1-1build1, 1.7.1-1ubuntu0.1), dkms:amd64 (2.2.0.3-1.1ubuntu5, 2.2.0.3-1.1ubuntu5.14.04), php5-common:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), coreutils:amd64 (8.21-1ubuntu5, 8.21-1ubuntu5.1), libkrb5-3:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), apt-utils:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), cpio:amd64 (2.11+dfsg-1ubuntu1, 2.11+dfsg-1ubuntu1.1), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu17, 0.8.8-0ubuntu17.1), python3-software-properties:amd64 (0.92.37.1, 0.92.37.3), libkadm5clnt-mit9:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), mount:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), libsystemd-daemon0:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), python-apt:amd64 (0.9.3.5, 0.9.3.5ubuntu1), libc-dev-bin:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libcgmanager0:amd64 (0.24-0ubuntu7, 0.24-0ubuntu7.2), file:amd64 (5.14-2ubuntu3.2, 5.14-2ubuntu3.3), libapparmor1:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), libkrb5-dev:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libmagic1:amd64 (5.14-2ubuntu3.2, 5.14-2ubuntu3.3), libpam-systemd:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), libc-bin:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libc6:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libglib2.0-0:amd64 (2.40.0-2, 2.40.2-0ubuntu1), php5-readline:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), libprocps3:amd64 (3.3.9-1ubuntu2, 3.3.9-1ubuntu2.2), libsepol1:amd64 (2.2-1, 2.2-1ubuntu0.1), libglib2.0-dev:amd64 (2.40.0-2, 2.40.2-0ubuntu1), libapt-inst1.5:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), libuuid1:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), libmount1:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), dnsutils:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), libdbus-1-3:amd64 (1.6.18-0ubuntu4.2, 1.6.18-0ubuntu4.3), udev:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), curl:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), update-notifier-common:amd64 (0.154.1, 0.154.1ubuntu1), plymouth:amd64 (0.8.8-0ubuntu17, 0.8.8-0ubuntu17.1), libglib2.0-data:amd64 (2.40.0-2, 2.40.2-0ubuntu1), mysql-client-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), krb5-locales:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libxml2:amd64 (2.9.1+dfsg1-3ubuntu4.3, 2.9.1+dfsg1-3ubuntu4.4), ntp:amd64 (4.2.6.p5+dfsg-3ubuntu2, 4.2.6.p5+dfsg-3ubuntu2.14.04.2), libudev1:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), binutils:amd64 (2.24-5ubuntu3, 2.24-5ubuntu3.1), bsdutils:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), libxml2-dev:amd64 (2.9.1+dfsg1-3ubuntu4.3, 2.9.1+dfsg1-3ubuntu4.4), libapparmor-perl:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), lshw:amd64 (02.16-2ubuntu1, 02.16-2ubuntu1.2), libssl-dev:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), wget:amd64 (1.15-1ubuntu1, 1.15-1ubuntu1.14.04.1), libapt-pkg4.12:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), uuid-runtime:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), python3-apt:amd64 (0.9.3.5, 0.9.3.5ubuntu1), mysql-common:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), php5-cli:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), libmysqlclient18:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), git-man:amd64 (1.9.1-1, 1.9.1-1ubuntu0.1), libplymouth2:amd64 (0.8.8-0ubuntu17, 0.8.8-0ubuntu17.1), libmysqlclient-dev:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), git:amd64 (1.9.1-1, 1.9.1-1ubuntu0.1), python3-distupgrade:amd64 (0.220.5, 0.220.7), libcurl3:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), apport:amd64 (2.14.1-0ubuntu3.5, 2.14.1-0ubuntu3.6), linux-firmware:amd64 (1.127.7, 1.127.11), libssl-doc:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), libcurl4-gnutls-dev:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), landscape-common:amd64 (14.01-0ubuntu3, 14.12-0ubuntu0.14.04), libblkid1:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), python3-apport:amd64 (2.14.1-0ubuntu3.5, 2.14.1-0ubuntu3.6), apparmor:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), tzdata:amd64 (2014e-0ubuntu0.14.04, 2015a-0ubuntu0.14.04), mysql-server:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), software-properties-common:amd64 (0.92.37.1, 0.92.37.3), openssl:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), libelf1:amd64 (0.158-0ubuntu5.1, 0.158-0ubuntu5.2), libglib2.0-bin:amd64 (2.40.0-2, 2.40.2-0ubuntu1), libkdb5-7:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), ubuntu-release-upgrader-core:amd64 (0.220.5, 0.220.7), linux-libc-dev:amd64 (3.13.0-37.64, 3.13.0-45.74), util-linux:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), python-apt-common:amd64 (0.9.3.5, 0.9.3.5ubuntu1), php5-gd:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), libgssrpc4:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libdrm2:amd64 (2.4.52-1, 2.4.56-1~ubuntu1), language-pack-en:amd64 (14.04+20140707, 14.04+20141110), libmysqld-dev:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), linux-image-generic:amd64 (3.13.0.37.44, 3.13.0.45.52), libkadm5srv-mit9:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libkrb5support0:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libk5crypto3:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libisccc90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), dh-apparmor:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), libc6-dev:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libisc95:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), libcurl3-gnutls:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), rsyslog:amd64 (7.4.4-1ubuntu2.3, 7.4.4-1ubuntu2.5), ntpdate:amd64 (4.2.6.p5+dfsg-3ubuntu2, 4.2.6.p5+dfsg-3ubuntu2.14.04.2), linux-generic:amd64 (3.13.0.37.44, 3.13.0.45.52) End-Date: 2015-02-12 14:43:37 Kind regards, *Manuel Camargo* Teléfono: 638000836 eMail: sir.louen(a)gmail.com <https://twitter.com/SirLouen> [image: Ver el perfil de Manuel Camargo Lominchar en LinkedIn] <http://es.linkedin.com/in/louen> [View Less]

4 3

Unable to route outbound with multiple VRRP IP's
by mark＠brightvoip.co.uk 13 Feb '15

13 Feb '15

Hi, I am trying to install a Kamailio server in a HA configuration, with IP's for 3 attached networks. I am using Keepalived/VRRP to manage the VIP's. I have tested v 4.1.6 and latest 4.2.2 I have 3 x listen entries, one for each network and mhomed=1. Also, for info, we have net.ipv4.ip_nonlocal_bind = 1 in sysctl.conf listen=udp:my.public.net.46:5060 listen=udp:192.168.106.46:5060 listen=udp:192.168.116.46:5060 mhomed=1 I have dispatcher set up to load balance over two seperate groups … [View More]

2 2

Possible memory leak dealing with presence in kamailio
by Nuno Reis 12 Feb '15

12 Feb '15

Hello all. I'm consistently watching a memory increase in kamailio when dealing with PRESENCE events, namely SIP PUBLISH events. The system eventually hangs running out of memory. This behavior is seen at least in kamailio 4.1 and 4.2. I'm currently using the latest stable 4.2.2. If I disable the SIP PUBLISH handling in kamailio i don't observe the issue anymore but as a side effect I don't have presence (name BLFs) also. What do you think can be the right approach here? Should I open an issue … [View More]

4 13

Roadmap to next major release 4.3.0
by Daniel-Constantin Mierla 12 Feb '15

12 Feb '15

Hello, being discussed yesterday during the IRC devel meeting, the proposed planning for next major release (v4.3.0) is: - freeze the development sometime in April - after mid of March decide the exact date when the development is going to be frozen - testing during last part of April and May - based on testing results, release in the time frame: end of May till mid of June >From git activity, there are already several new modules and plenty of new features -- don't forget to add … [View More]

1 0

Using MariaDB with sqlops sql_query_async
by davy van de moere 12 Feb '15

12 Feb '15

Does anyone know if the async queries of kamailio work with mariadb? I'm on kamailio 4.2.3, and I can't get the async way of querying to work. I don't get any errors, but I don't see the queries to be executed. the relevant part of my config is: loadmodule "db_mysql.so" loadmodule "sqlops.so" modparam("sqlops","sqlcon","ca=>mysql://kamailio:kamailiorw@localhost /kamailio") sql_query_async("ca", "insert into cdr_events (callid) values ('$ci') "); When just replace sql_query_async with … [View More]

2 3

long l_uuid in uac_reg
by kovarik＠odorik.cz 11 Feb '15

11 Feb '15

Hello, rpc funcions: reg_info,reg_enable,reg_disable not work if l_uuid is number and size > than 10, for 1234567890 is O.K. and for 12345678901 try to find 18446744073170328629. kamcmd uac.reg_enable l_uuid 1234567890 -- found kamcmd uac.reg_enable l_uuid 12345678901 -- not found and if number start with zero then zero is cut. kamcmd uac.reg_enable l_uuid 0034567890 -- 34567890 I add debug to uac_reg.c 1615 LM_ERR("START %.*s,%.*s\n", attr.len,attr.s,val.len, val.s); Thaks

2 1

Trouble with DB APIs
by Davidson, Erik 11 Feb '15

11 Feb '15

Hey Everyone! I'm currently working on a database module and I've come across some issues/confusion that I was hoping someone could clear up for me. I've been looking at the existing modules and the docs online for help but I can't find a definitive answer for them. 1. I see there are 2 DB APIs (srdb1 and srdb2) and I gather that srdb2 is the newer version? Should I aim to use srdb2 exclusively or should I also use srdb1? 2. It looks like srdb2 provides a db_uri command that can be … [View More]

2 1

Next IRC development meeting
by Daniel-Constantin Mierla 11 Feb '15

11 Feb '15

Hello, I thought to propose organizing the next IRC meeting to discuss and sync each other about Kamailio development and surrounding ecosystem. First date proposal is next week, Wednesday, 15:00GMT, Feb 11, 2015, on the usual #kamailio channel at freenode.net. The date can be changed, based on feedback from the people that want to attends. I made a wiki page for the event at: - http://www.kamailio.org/wiki/devel/irc-meetings/2015a Feel free to propose topics to the agenda and/or new … [View More]

3 4

[Kamailio 4.0.6] sometimes route specified by RTIMER module doesn't be executed just after finishing starting Kamailio server
by jack wang 11 Feb '15

11 Feb '15

Hello everyone, I got a little trouble on using the RTIMER module. Sometimes the route block I set using the "exec" parameter in RTIMER module doesn't be executed, this will happen from Kamailio server being started, and only work (not always) after restarting server. I have no idea why this happen, does anyone ever met this? Which part should I notice? Thx :)

1 0

Presence module for BLF issue
by SamyGo 11 Feb '15

11 Feb '15

Hi community, I'm dealing with a problem here related to presence module handling BLF. My BLF phones are Yealink T28p with latest firmware and work perfectly with Asterisk and FreeSwitch but not with Kamailio as expected. What I'm observing here is a malfunctioning statuses due to accumulation of multiple entries of just one status in "presentitiy" table. These entries neither get expired not cleared from DB hence I see atleast 21 XML tags combined in the NOTIFY sent to Phones. Here is what … [View More]

2 10

Issues while using Kamailio as proxy with Asterisk
by Juned Khan 10 Feb '15

10 Feb '15

Hi All, I am using Kamailio as proxy server with Asterisk but having some issues with Inbound and outbound calls. Asterisk is a registrar, Kamailio is a just for proxy. Using softphone call are working fine but using hardphone, its creating issues. Here are the test cases. No Test case *98 Inbound 1 ATA registered with Proxy Domain No No 2 ATA registered with Proxy IP Yes Yes … [View More]

2 1

Kamailio v4.2.3 Released
by Daniel-Constantin Mierla 10 Feb '15

10 Feb '15

Hello, Kamailio SIP Server v4.2.3 stable release is out. This is a maintenance release of the latest stable branch, 4.2, that includes fixes since release of v4.2.2. There is no change to database schema or configuration language structure that you have to do on installations of v4.2.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.2.3. For more details about version 4.2.3 (including links and guidelines to download the tarball or from GIT … [View More]

1 0

Re: [SR-Users] Wrong location entries when using usrloc with Mongo
by Mickael Marrache 10 Feb '15

10 Feb '15

I forgot to precise that I allow only one contact per AOR. modparam("registrar", "max_contacts", 1) save("location", "0x04") From: Mickael Marrache [mailto:mickaelmarrache@gmail.com] Sent: Friday, January 30, 2015 10:51 AM To: sr-users(a)lists.sip-router.org Subject: Wrong location entries when using usrloc with Mongo Hi, I start with no location nor in Mongo, nor in memory. My UA registers successfully and I can see the location entry in Mongo. Then, I close my UA which … [View More]unregisters (by setting Expires header to 0). Then, I open the app again and a new registration is made. The entry after first registration. Looks okay. { "_id" : ObjectId("54cb38f684e58133783f2b42"), "username" : "A", "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp", "expires" : ISODate("2015-01-30T08:55:34Z"), "q" : -1, "callid" : "297EC55073A07BF78F0C05822A6CCDFB47E48705", "cseq" : 8809, "flags" : 0, "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" : "sip:XXXXXXXXXXX:54217;transport=tcp", "path" : "<sip:XXXXXXXXXX;lr;received=sip:XXXXXXXXXXX:54217%3Btransport%3Dtcp>", "socket" : "udp:XXXXXXXXX:5060", "methods" : 4751, "last_modified" : ISODate("2015-01-30T07:55:34Z"), "ruid" : "uloc-54cb38df-3378-2", "instance" : null, "reg_id" : 0 } The same entry after un register (Expires 0). Note that the username field is missing. In any case, I expected the entry to be deleted. { "_id" : ObjectId("54cb38f684e58133783f2b42"), "expires" : ISODate("2015-01-30T08:56:51Z"), "q" : -1, "cseq" : 8811, "flags" : 0, "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" : "sip: XXXXXXXXX:54217;transport=tcp", "path" : "<sip: XXXXXXXXX;lr;received=sip: XXXXXXXXX:54217%3Btransport%3Dtcp>", "socket" : "udp: XXXXXXXXX:5060", "methods" : 4751, "last_modified" : ISODate("2015-01-30T07:56:51Z"), "callid" : "297EC55073A07BF78F0C05822A6CCDFB47E48705", "instance" : null, "reg_id" : 0, "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp" } The entries after second registration. The new entry looks okay. But, the old entry is still here. { "_id" : ObjectId("54cb38f684e58133783f2b42"), "expires" : ISODate("2015-01-30T08:56:51Z"), "q" : -1, "cseq" : 8811, "flags" : 0, "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" : "sip: XXXXXXXXX:54217;transport=tcp", "path" : "<sip: XXXXXXXXX;lr;received=sip: XXXXXXXXX:54217%3Btransport%3Dtcp>", "socket" : "udp: XXXXXXXXX:5060", "methods" : 4751, "last_modified" : ISODate("2015-01-30T07:56:51Z"), "callid" : "297EC55073A07BF78F0C05822A6CCDFB47E48705", "instance" : null, "reg_id" : 0, "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp" } { "_id" : ObjectId("54cb3a7884e581337a25b895"), "username" : "A", "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp", "expires" : ISODate("2015-01-30T09:02:00Z"), "q" : -1, "callid" : "297EC55073A07BF78F0C05822A6CCDFB47E48705", "cseq" : 8813, "flags" : 0, "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" : "sip: XXXXXXXXX:54217;transport=tcp", "path" : "<sip: XXXXXXXXX;lr;received=sip: XXXXXXXXX:54217%3Btransport%3Dtcp>", "socket" : "udp: XXXXXXXXX:5060", "methods" : 4751, "last_modified" : ISODate("2015-01-30T08:02:00Z"), "ruid" : "uloc-54cb38df-337a-1", "instance" : null, "reg_id" : 0 } The issue is the entry is not deleted after un registering. I precise that registrations are dispatched over multiple registrars with all accesses the same Mongo cluster. Thanks, Mickael [View Less]

2 7

Kamailio appends firs inserted branch twice
by Yuriy Gorlichenko 10 Feb '15

10 Feb '15

Hello I use this version of kamailio kamailio -v version: kamailio 4.3.0-dev3 (x86_64/linux) 8cdbe7 flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_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, DEFAULT PKG_SIZE 8MB … [View More]poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 8cdbe7 compiled on 17:54:50 Jan 20 2015 with gcc 4.8.2 I hav an issue with append branches to branch route when I need fork call to one endpoint woth different destionations. I use my own algorithm for call to this devices because with lookup("location") I can not use RTPENGINE for different types of endpoints (web endoints and standart UDP endpoints) My alg is here: { sql_query("ca", "select contact from location where username='$tU'", "ra"); xlog("L_INFO","rows: $dbr(ra=>rows) cols: $dbr(ra=>cols)\n"); if($dbr(ra=>rows)>0){ $var(i)=0; while($var(i)<$dbr(ra=>rows)){ xlog("L_INFO","SQL query return contact {$dbr(ra=>[$var(i),0])} for {$tU} at step {$var(i)}\n"); if ($dbr(ra=>[$var(i),0])=~"transport=ws"){ xlog("L_INFO", "This is a Websocket call to endpoint"); sql_pvquery("ca", "select received from location where contact='$dbr(ra=>[$var(i),0])'","$var(recieved)"); $du=$var(recieved); xlog("L_INFO","SQL query return recieved {$var(recieved)} for {$tU}. Destination is {$du}\n"); append_branch("sip:$tU@$(du{s.select,1,:})"); } else { xlog("L_INFO", "This is a classic UDP call to endpoint"); $var(recieved)=''; sql_pvquery("ca", "select received from location where contact='$dbr(ra=>[$var(i),0])'","$var(recieved)"); xlog("L_INFO", "SQL query return RECIEVED {$var(recieved)}"); if ($var(recieved)==0){ xlog("L_INFO", "Recieved string is EMPTY"); $du="sip:"+$(dbr(ra=>[$var(i),0]){s.select,1,@}); } else { xlog("L_INFO", "Recieved string is {$var(recieved)}"); $du=$var(recieved); } $var(UDP_contact)="sip:"+$(dbr(ra=>[$var(i),0]){s.select,1,@}); append_branch("sip:$tU@$(du{s.select,1,:})"); xlog("L_INFO","Classic Destination URI is {$dbr(ra=>[$var(i),0])} for {$tU}}. Destination is {$du}\n"); } $var(i) = $var(i) + 1; } } else{ exit; } t_on_branch("1"); return; } } } branch_route[1]{ if($du=~"transport=ws"){ xlog("L_INFO","Websocket Branch is {$du} for {$tU}\n"); rtpengine_manage("internal extenal force trust-address replace-origin replace-session-connection ICE=force RTP/SAVPF"); t_on_reply("REPLY_FROM_WS"); } else{ xlog("L_INFO","UDP Branch is {$du)} for {$tU}\n"); rtpengine_manage("replace-origin replace-session-connection ICE=remove RTP/AVP"); t_on_reply("MANAGE_CLASSIC_REPLY"); } } So as you see I choose array of devices and then set its to branches. At the kamailio console I see output This is output of alg that above. I have 3 devices: 2 websocket devices and 1 udp But when you look at dump where rtpengine make changes with packets you can see that it runs for 4 devices and 1 and 4 devices is the same. You can see start of every branch from words of log "Websocket Branch is" or "UDP Branch is" So this bug gives a mistake because some of hardphones can not handlie double INVITE and kamilio response for this devices cancel with 200 cause because hardphone set 482 reply to kamialio. (you can see it reply at the log) Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: rows: 3 cols: 1 Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: SQL query return contact {sip:5ue13vsh@2t4iielj109h.invalid;transport=ws} for {123455678} at step {0} Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: This is a Websocket call to endpoint Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: SQL query return recieved {sip:85.6.14.8:4328;transport=WS} for {123455678}. Destination is {sip:85.6.14.8:4328;transport=WS} Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: SQL query return contact {sip:a7uo9vsq@7c0oo5kvc71e.invalid;transport=ws} for {123455678} at step {1} Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: This is a Websocket call to endpoint Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: SQL query return recieved {sip:85.2.10.3:58509;transport=WS} for {123455678}. Destination is {sip:85.2.10.3:58509;transport=WS} Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: SQL query return contact {sip:upsjchv2@5c88tisd29d4.invalid;transport=ws} for {123455678} at step {2} Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: This is a Websocket call to endpoint Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: SQL query return recieved {sip:18.9.18.10:56917;transport=WS} for {123455678}. Destination is {sip:18.9.18.10:56917;transport=WS} Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: Websocket Branch is {sip:18.9.18.10:56917;transport=WS} for {123455678} Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Got valid command from 127.0.0.1:52689: offer - { "sdp": "v=0#015#012o=root 1141861088 1141861088 IN IP4 12.34.56.78#015#012s=Asterisk PBX 13.1.0#015#012c=IN IP4 12.34.56.78#015#012t=0 0#015#012m=audio 12230 RTP/AVP 9 8 107 0 101#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:107 opus/48000/2#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=maxptime:60#015#012a=sendrecv#015#012", "ICE": "force", "direction": [ "internal" ], "flags": [ "extenal", "force", "trust-address" ], "replace": [ "origin", ... Feb 8 23:04:43 Kamailio2 rtpengine[55410]: ... "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "220725c425526bc941dff8e972bd9458@12.34.56.78:50600", "received-from": [ "IP4", "12.34.56.78" ], "from-tag": "as4f0c032f", "command": "offer" } Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Unknown flag encountered: 'extenal' Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Unknown flag encountered: 'force' Feb 8 23:04:43 Kamailio2 rtpengine[55410]: [220725c425526bc941dff8e972bd9458@12.34.56.78:50600] Creating new call Feb 8 23:04:43 Kamailio2 rtpengine[55410]: [220725c425526bc941dff8e972bd9458@12.34.56.78:50600] Returning to SIP proxy: d3:sdp747:v=0#015#012o=root 1141861088 1141861088 IN IP4 23.101.139.216#015#012s=Asterisk PBX 13.1.0#015#012c=IN IP4 23.101.139.216#015#012t=0 0#015#012a=ice-lite#015#012m=audio 38518 RTP/SAVPF 9 8 107 0 101#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:107 opus/48000/2#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=maxptime:60#015#012a=sendrecv#015#012a=rtcp:38519#015#012a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:f31jYQjjKBdYoqWYijx0V/ZtTfP17pTVW8NJGVQ4#015#012a=setup:actpass#015#012a=fingerprint:sh ... Feb 8 23:04:43 Kamailio2 rtpengine[55410]: [220725c425526bc941dff8e972bd9458@12.34.56.78:50600] ... a-1 00:E3:0F:B6:C0:9F:D4:16:52:D2:41:A8:01:24:51:CD:3F:FB:B2:55#015#012a=ice-ufrag:VfqUSGBP#015#012a=ice-pwd:t5bLzDaNcqWUwzh7iEtyAZfweGo6#015#012a=candidate:04GQy5683m4TP1Da 1 UDP 2130706431 23.101.139.216 38518 typ host#015#012a=candidate:04GQy5683m4TP1Da 2 UDP 2130706430 23.101.139.216 38519 typ host#015#0126:result2:oke Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: Websocket Branch is {sip:85.6.14.8:4328;transport=WS} for {123455678} Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Got valid command from 127.0.0.1:52689: offer - { "sdp": "v=0#015#012o=root 1141861088 1141861088 IN IP4 12.34.56.78#015#012s=Asterisk PBX 13.1.0#015#012c=IN IP4 12.34.56.78#015#012t=0 0#015#012m=audio 12230 RTP/AVP 9 8 107 0 101#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:107 opus/48000/2#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=maxptime:60#015#012a=sendrecv#015#012", "ICE": "force", "direction": [ "internal" ], "flags": [ "extenal", "force", "trust-address" ], "replace": [ "origin", ... Feb 8 23:04:43 Kamailio2 rtpengine[55410]: ... "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "220725c425526bc941dff8e972bd9458@12.34.56.78:50600", "received-from": [ "IP4", "12.34.56.78" ], "from-tag": "as4f0c032f", "command": "offer" } Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Unknown flag encountered: 'extenal' Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Unknown flag encountered: 'force' Feb 8 23:04:43 Kamailio2 rtpengine[55410]: [220725c425526bc941dff8e972bd9458@12.34.56.78:50600] Returning to SIP proxy: d3:sdp747:v=0#015#012o=root 1141861088 1141861088 IN IP4 23.101.139.216#015#012s=Asterisk PBX 13.1.0#015#012c=IN IP4 23.101.139.216#015#012t=0 0#015#012a=ice-lite#015#012m=audio 38518 RTP/SAVPF 9 8 107 0 101#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:107 opus/48000/2#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=maxptime:60#015#012a=sendrecv#015#012a=rtcp:38519#015#012a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:f31jYQjjKBdYoqWYijx0V/ZtTfP17pTVW8NJGVQ4#015#012a=setup:actpass#015#012a=fingerprint:sh ... Feb 8 23:04:43 Kamailio2 rtpengine[55410]: [220725c425526bc941dff8e972bd9458@12.34.56.78:50600] ... a-1 00:E3:0F:B6:C0:9F:D4:16:52:D2:41:A8:01:24:51:CD:3F:FB:B2:55#015#012a=ice-ufrag:VfqUSGBP#015#012a=ice-pwd:t5bLzDaNcqWUwzh7iEtyAZfweGo6#015#012a=candidate:04GQy5683m4TP1Da 1 UDP 2130706431 23.101.139.216 38518 typ host#015#012a=candidate:04GQy5683m4TP1Da 2 UDP 2130706430 23.101.139.216 38519 typ host#015#0126:result2:oke Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: Websocket Branch is {sip:85.2.10.3:58509;transport=WS} for {123455678} Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Got valid command from 127.0.0.1:52689: offer - { "sdp": "v=0#015#012o=root 1141861088 1141861088 IN IP4 12.34.56.78#015#012s=Asterisk PBX 13.1.0#015#012c=IN IP4 12.34.56.78#015#012t=0 0#015#012m=audio 12230 RTP/AVP 9 8 107 0 101#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:107 opus/48000/2#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=maxptime:60#015#012a=sendrecv#015#012", "ICE": "force", "direction": [ "internal" ], "flags": [ "extenal", "force", "trust-address" ], "replace": [ "origin", ... Feb 8 23:04:43 Kamailio2 rtpengine[55410]: ... "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "220725c425526bc941dff8e972bd9458@12.34.56.78:50600", "received-from": [ "IP4", "12.34.56.78" ], "from-tag": "as4f0c032f", "command": "offer" } Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Unknown flag encountered: 'extenal' Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Unknown flag encountered: 'force' Feb 8 23:04:43 Kamailio2 rtpengine[55410]: [220725c425526bc941dff8e972bd9458@12.34.56.78:50600] Returning to SIP proxy: d3:sdp747:v=0#015#012o=root 1141861088 1141861088 IN IP4 23.101.139.216#015#012s=Asterisk PBX 13.1.0#015#012c=IN IP4 23.101.139.216#015#012t=0 0#015#012a=ice-lite#015#012m=audio 38518 RTP/SAVPF 9 8 107 0 101#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:107 opus/48000/2#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=maxptime:60#015#012a=sendrecv#015#012a=rtcp:38519#015#012a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:f31jYQjjKBdYoqWYijx0V/ZtTfP17pTVW8NJGVQ4#015#012a=setup:actpass#015#012a=fingerprint:sh ... Feb 8 23:04:43 Kamailio2 rtpengine[55410]: [220725c425526bc941dff8e972bd9458@12.34.56.78:50600] ... a-1 00:E3:0F:B6:C0:9F:D4:16:52:D2:41:A8:01:24:51:CD:3F:FB:B2:55#015#012a=ice-ufrag:VfqUSGBP#015#012a=ice-pwd:t5bLzDaNcqWUwzh7iEtyAZfweGo6#015#012a=candidate:04GQy5683m4TP1Da 1 UDP 2130706431 23.101.139.216 38518 typ host#015#012a=candidate:04GQy5683m4TP1Da 2 UDP 2130706430 23.101.139.216 38519 typ host#015#0126:result2:oke Feb 8 23:04:43 Kamailio2 kamailio[59406]: INFO: <script>: Websocket Branch is {sip:18.9.18.10:56917;transport=WS} for {123455678} Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Got valid command from 127.0.0.1:52689: offer - { "sdp": "v=0#015#012o=root 1141861088 1141861088 IN IP4 12.34.56.78#015#012s=Asterisk PBX 13.1.0#015#012c=IN IP4 12.34.56.78#015#012t=0 0#015#012m=audio 12230 RTP/AVP 9 8 107 0 101#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:107 opus/48000/2#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=maxptime:60#015#012a=sendrecv#015#012", "ICE": "force", "direction": [ "internal" ], "flags": [ "extenal", "force", "trust-address" ], "replace": [ "origin", ... Feb 8 23:04:43 Kamailio2 rtpengine[55410]: ... "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "220725c425526bc941dff8e972bd9458@12.34.56.78:50600", "received-from": [ "IP4", "12.34.56.78" ], "from-tag": "as4f0c032f", "command": "offer" } Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Unknown flag encountered: 'extenal' Feb 8 23:04:43 Kamailio2 rtpengine[55410]: Unknown flag encountered: 'force' Feb 8 23:04:43 Kamailio2 rtpengine[55410]: [220725c425526bc941dff8e972bd9458@12.34.56.78:50600] Returning to SIP proxy: d3:sdp747:v=0#015#012o=root 1141861088 1141861088 IN IP4 23.101.139.216#015#012s=Asterisk PBX 13.1.0#015#012c=IN IP4 23.101.139.216#015#012t=0 0#015#012a=ice-lite#015#012m=audio 38518 RTP/SAVPF 9 8 107 0 101#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:107 opus/48000/2#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=maxptime:60#015#012a=sendrecv#015#012a=rtcp:38519#015#012a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:f31jYQjjKBdYoqWYijx0V/ZtTfP17pTVW8NJGVQ4#015#012a=setup:actpass#015#012a=fingerprint:sh ... Feb 8 23:04:43 Kamailio2 rtpengine[55410]: [220725c425526bc941dff8e972bd9458@12.34.56.78:50600] ... a-1 00:E3:0F:B6:C0:9F:D4:16:52:D2:41:A8:01:24:51:CD:3F:FB:B2:55#015#012a=ice-ufrag:VfqUSGBP#015#012a=ice-pwd:t5bLzDaNcqWUwzh7iEtyAZfweGo6#015#012a=candidate:04GQy5683m4TP1Da 1 UDP 2130706431 23.101.139.216 38518 typ host#015#012a=candidate:04GQy5683m4TP1Da 2 UDP 2130706430 23.101.139.216 38519 typ host#015#0126:result2:oke Feb 8 23:04:43 Kamailio2 kamailio[59438]: INFO: <script>: Reply from webrtc client {18.9.18.10:56917} for method {INVITE}: 100 Feb 8 23:04:43 Kamailio2 kamailio[59438]: INFO: <script>: Manage_Reply from webrtc client {18.9.18.10:56917} for method {INVITE}: 100 Feb 8 23:04:43 Kamailio2 kamailio[59438]: INFO: <script>: Reply from webrtc client {18.9.18.10:56917} for method {INVITE}: 180 Feb 8 23:04:43 Kamailio2 kamailio[59438]: INFO: <script>: Manage_Reply from webrtc client {18.9.18.10:56917} for method {INVITE}: 180 Feb 8 23:04:43 Kamailio2 kamailio[59438]: INFO: <script>: Reply from webrtc client {18.9.18.10:56917} for method {INVITE}: 482 Feb 8 23:04:43 Kamailio2 kamailio[59442]: INFO: <script>: Reply from webrtc client {85.2.10.3:58509} for method {INVITE}: 100 Feb 8 23:04:43 Kamailio2 kamailio[59442]: INFO: <script>: Manage_Reply from webrtc client {85.2.10.3:58509} for method {INVITE}: 100 [View Less]

2 3

Setting dialog variable when BYE is received before accounting
by Mickael Marrache 10 Feb '15

10 Feb '15

Hi, Is there a way to set a dialog variable when a BYE is received so that it can be written in a CDR? I tried as follows but it didn't work: if (loose_route()) { .. if(is_method("BYE")) { if(is_direction("downstream")) { #Call disconnected by caller $dlg_var(dr) = 700; } else { #Call disconnected by callee … [View More]

2 1

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