[OpenSIPS-Users] ASR & ACR per country/destination
Hello dear list, I am looking for a tool that will provide me call statistics (ASR and ACD) by destination/country with alerting by emails. I try to detect when a sip provider does not work well in order to route the traffic to another sip provider. Thank you. Abdoul OSSENI AfriCallShop ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] HEP mi_datagram tracing
Hi, I’m running into an issue in 2.3.3 with HEP tracing and the proto_tcp and mi_datagram modules. I am not setting the trace_destination parameter in the mi_datagram module, so I expect tracing should be disabled. I am setting the parameter in the proto_tcp module, but the trace_on parameter is disabled. However, tracing still seems to be attempting and is causing errors. This config: #// Even though we are not receiving HEP, #// this listener is required by OpenSIPS #// to use the proto_hep module. listen=hep_udp:PRIVATE_ADDRESS:9060 listen=hep_tcp:PRIVATE_ADDRESS:9060 #// DATAGRAM Management Interface loadmodule "mi_datagram.so" modparam("mi_datagram", "unix_socket_mode", 0666) modparam("mi_datagram", "socket_name", "/tmp/opensips.sock") modparam("mi_datagram", "children_count", 1) #// PROTOcol HEP module loadmodule "proto_hep.so" modparam("proto_hep", "hep_id", "[hep_tcp] 127.0.0.1:9060; transport=tcp; version=3") modparam("proto_hep", "hep_capture_id", 1) modparam("proto_hep", "homer5_on", 1) #// PROTOcol TCP module loadmodule "proto_tcp.so" modparam("proto_tcp", "trace_destination", "hep_tcp") modparam("proto_tcp", "trace_on", 0) Generates these errors: Mar 30 13:52:25 [328] ERROR:proto_hep:build_hep3_buf: unknown IP family Mar 30 13:52:25 [328] ERROR:proto_hep:send_hep_message: failed to build hep buffer! Mar 30 13:52:25 [328] ERROR:core:trace_mi_message: failed to send trace message! Mar 30 13:52:25 [328] ERROR:mi_datagram:mi_trace_request: failed to trace mi command request! Mar 30 13:52:25 [328] ERROR:proto_hep:build_hep3_buf: unknown IP family Mar 30 13:52:25 [328] ERROR:proto_hep:send_hep_message: failed to build hep buffer! Mar 30 13:52:25 [328] ERROR:core:trace_mi_message: failed to send trace message! Mar 30 13:52:25 [328] ERROR:mi_datagram:mi_trace_reply: failed to trace mi command reply! Tracing for the mi_datagram module should not be enabled, but appears to be attempting to trace anyway. If I change the HEP config to use version 2 then the errors change: #// Even though we are not receiving HEP, #// this listener is required by OpenSIPS #// to use the proto_hep module. listen=hep_udp:PRIVATE_ADDRESS:9060 #// DATAGRAM Management Interface loadmodule "mi_datagram.so" modparam("mi_datagram", "unix_socket_mode", 0666) modparam("mi_datagram", "socket_name", "/tmp/opensips.sock") modparam("mi_datagram", "children_count", 1) #// PROTOcol HEP module loadmodule "proto_hep.so" modparam("proto_hep", "hep_id", "[hep_udp] 127.0.0.1:9060; transport=udp; version=2") modparam("proto_hep", "hep_capture_id", 1) modparam("proto_hep", "homer5_on", 1) #// PROTOcol TCP module loadmodule "proto_tcp.so" modparam("proto_tcp", "trace_destination", "hep_udp") modparam("proto_tcp", "trace_on", 0) Generates these errors: Mar 30 14:33:12 [341] ERROR:proto_hep:unpack_hepv12: unsupported family [1] Mar 30 14:33:12 [340] ERROR:proto_hep:unpack_hepv12: unsupported family [1] Mar 30 14:33:12 [341] ERROR:proto_hep:update_recv_info: invalid hep version! Mar 30 14:33:12 [340] ERROR:proto_hep:update_recv_info: invalid hep version! Mar 30 14:33:12 [340] ERROR:proto_hep:hep_udp_read_req: failed to run hep callbacks Mar 30 14:33:12 [341] ERROR:proto_hep:hep_udp_read_req: failed to run hep callbacks If I remove the trace_destination parameter from the proto_tcp module all errors stop. Interestingly, if I set the HEP listener port to something different than the destination port, the errors also stop. Thanks, Ben Newlin ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] HEP Address Hostname error
Has anyone had a chance to look into this DNS issue? Thanks, Ben Newlin From: Ben NewlinDate: Monday, March 26, 2018 at 4:02 PM To: OpenSIPS users mailling list Subject: HEP Address Hostname error Hi, While upgrading from 1.11 to 2.3, we have run into an issue with the parsing of the hep_id parameter in the proto_hep module. In 1.11, we used the duplicate_uri setting in the siptrace module like so: modparam("siptrace", "duplicate_uri", "sip:homer-hep.test.com:5656") In 2.3, we converted this into the appropriate module config for proto_hep: modparam("proto_hep", "hep_id", "[hid]homer-hep.test.com:5656;transport=udp;version=2") However, this results in OpenSIPS complaining about receiving the wrong address: Mar 26 19:59:58 [332] CRITICAL:core:mk_proxy: could not resolve hostname: "homer" Mar 26 19:59:58 [332] ERROR:proto_hep:send_hep_message: bad hep host name! Mar 26 19:59:58 [332] ERROR:siptrace:send_trace_proto_duplicate: failed to forward message to destination! Mar 26 19:59:58 [332] ERROR:siptrace:save_siptrace: Failed to duplicate with hep to It appears the proto_hep module parameter parsing doesn’t allow for dashes/hyphens in the address portion, so it ends up with only a small part of the actual hostname of our Homer server. Thanks, Ben Newlin ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] How to extract SIP-I ISUP 'Redirecting number' parameter
Hi, I've pushed the fix, but bear in mind that you could still extract the redirecting number without full subfield access support. By just reading from "$isup_param(Redirecting number)" you get, as a string, the full ISUP parameter value in hex representation. From that, knowing the parameter format from the ISUP specification, you could parse the number yourself in the OpenSIPS script. Regards, Vlad Patrascu OpenSIPS Developer http://www.opensips-solutions.com On 29.03.2018 13:52, Eugene Prokopiev wrote: Btw, is it possible to extract ISUP part as is in binary form and read by some external script? Can anybody advice me any library to parse ISUP binary data? 2018-03-29 12:50 GMT+03:00 Eugene Prokopiev: Thank you! I submitted https://github.com/OpenSIPS/opensips/issues/1323 - maybe your patch can be applied? 2018-03-29 10:53 GMT+03:00 Arto Kuiri : Hello, I had same problem and made my own patch. See attached diff, it adds support for: - redirection info (reason in same format as in SIP diversion header, commented ITU Q.763 version) - original called number - redirection number Meant to make feature request/patch, but somehow forgot it. Best regards, Arto Kuiri Lähettäjä: Users käyttäjän Vlad Patrascu puolesta Lähetetty: 28. maaliskuuta 2018 20:48 Vastaanottaja: users@lists.opensips.org Aihe: Re: [OpenSIPS-Users] How to extract SIP-I ISUP 'Redirecting number' parameter Hi, Unfortunately "Redirecting Number" is not currently supported, but you could open up a feature request regarding this, as it would be not very difficult to implement. Regards, Vlad Patrascu OpenSIPS Developer http://www.opensips-solutions.com Home — OpenSIPS Solutions www.opensips-solutions.com OpenSIPS is a mature Open Source implementation of a SIP server. OpenSIPS is more than a SIP proxy/router as it includes application-level functionalities. On 28.03.2018 18:32, Eugene Prokopiev wrote: Hi, I need to extract ISUP parameter 'Redirecting number' from SIP-I INVITE request and add it as SIP header with 'X-' prefix to process in FreeSWITCH. Can't found any about 'Redirecting number' in http://www.opensips.org/html/docs/modules/2.3.x/sip_i.html, so how to extract it? 'Redirecting number' parameter value is visible in Wireshark now as ISUP parameter with t=11 and l=7 ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- WBR, Eugene Prokopiev ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users