sr-users

sr-users@lists.kamailio.org

48 participants
37555 discussions

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 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

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 conf script: ####### Modules Section ######## loadmodule "db_mysql.so" loadmodule "mi_fifo.so" loadmodule "kex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "mi_rpc.so" loadmodule "xcap_client.so" loadmodule "pua.so" loadmodule "pua_reginfo.so" loadmodule "presence.so" loadmodule "presence_reginfo.so" loadmodule "presence_xml.so" # ----------------- setting module-specific parameters --------------- #!define DBURL "mysql://kamailio:kamailiorw@localhost/kamailio" # ----- xlog params ----- modparam("xlog", "prefix", "-xlog: ") # ----- mi_fifo params ----- modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo") # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) # ----- rr params ----- # add value to ;lr param to cope with most of the UAs modparam("rr", "enable_full_lr", 1) # do not append from tag to the RR (no need for this script) modparam("rr", "append_fromtag", 0) # ----- registrar params ----- modparam("registrar", "method_filtering", 1) modparam("registrar", "max_expires", 86400) # ----- pua_reginfo params ----- modparam("pua_reginfo", "default_domain", "system.test") modparam("pua_reginfo", "server_address", "sip:reginfo@10.171.0.4") modparam("pua_reginfo", "publish_reginfo", 0) modparam("pua_reginfo", "default_domain", "system.test") # ----- presence_xml params ----- modparam("presence_xml", "integrated_xcap_server", 1) # ----- presence params ----- modparam("presence", "db_url", DBURL)

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. Running kamailio 4.2.2 and relevant sections of kamailio.cfg are: modparam("dialog_ng", "dlg_flag", FLT_DIALOG) modparam("dialog_ng", "timeout_avp", "$avp(DLG_TIMEOUT_AVP)") modparam("dialog_ng", "detect_spirals", 1) modparam("dialog_ng", "profiles_no_value", "orig ; term") request_route { # NAT detection route(NATDETECT); # Set DLG flag to track dialogs using dialog2 if (!is_method("REGISTER|SUBSCRIBE")) setflag(FLT_DIALOG); # handle requests within SIP dialogs route(WITHINDLG); ### only initial requests (no To tag) # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) t_relay(); exit; } t_check_trans(); if (is_method("INVITE")) { set_dlg_profile("orig"); Ro_CCR("CHARGING_CCR_REPLY", "orig", "SCUR", "", "30","CCR_location"); } So my question is, "should the above logic create a dialog record on the initial INVITE?" and if yes then "what possible reasons might there be for the Ro_CCR() function not be able to detect it exists?" Cheers Shane Harrison

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: --- -----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

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 can see rtpengine throwing this error - "SRTCP output wanted, but no crypto suite was negotiated" BTW, I have - [root@localhost log]# openssl version OpenSSL 1.0.1j 15 Oct 2014 I even tried building kamailio & rtpengine using this openssl but in-vain. One thing that baffles me is that, apparently kamailio has started receiving RTP packets (perhaps early media) but the mobile phone hasn't ringed :-( I am attaching all possible logs & seek some guidance from the array of experts in this list. Files attached: a) tcpdump on ext. interface b) tcpdump on loopback c) syslogs d) Chromium JS logs UAC (14.98.55.38), Kamailio (125.99.186.126), SIP Server (157.238.178.153), Media Server (199.27.244.6) -- Warm Regds. MathuRahul

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 rtpengine started failing after a >openssl update in January. Recompiling a newer version from git fixed that. > >regards > >M I updated to latest version through git but still stuck there. Now I can see that the config file (ngcp-rtpengine in etc default) has changed so I'm not sure how should this impact (not ADDRESS neither ADV ADDRESS now I see an Interfaces parameter) I also find for some reason very possible that somehow rtp traffic is not getting through. ICE candidates are being negotiated, so I feel that the route is clear, so maybe there might be some crypto issues as you point out, but update has not been enough :( Any other ideas? *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>

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

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