Re: [SR-Users] How to distinguish 200 OK that have byed

I want to distinguish the Retransmission 200 OK(INVITE), not the first 200 OK(INVITE) or every 200 OK(INVITE) Every 200 OK will request port from rtpproxy, but The call is byed. I don't want to request port any more, so to drop it. 2016-04-20 12:06 GMT+08:00 Alex Balashov : > 1. Why would you w

[SR-Users] Kamailio IMS+FHoSS: Error "Visited Network Identity not found, responding with 400"

Good afternoon! I use Kamailio from BOX from Article https://www.kamailio.org/w/2016/02/kamailio-ims-getting-started-box/ The client can not register (use Boghe IMS Client as IMS client) i-cscf log 10(1991) INFO:

Re: [SR-Users] I have kamailio with drouting modulo and I want to pass only the RTP trafic to a FREESWITCH server

Hi Humberto Take a look to RTPENGINE and rtpengine module in Kamailio. Thats for RTP handling. WITH_FREESWITCH allows in code to enable some parts to handle SIP correctly agains Freeswitch. You should configure some values as FreeSwitch IP and port BR 2016-04-19 21:46 GMT+02:00 Humberto H : >

Re: [SR-Users] How to distinguish 200 OK that have byed

1. Why would you want to drop it? ‎2. Any reply has a CSeq value matching the request to which it corresponds. So, $rm, method, and is_method() in an onreply_route can all be used to test for a BYE. -- Alex Balashov | Principal | Evariste Systems LLC 1447 Peachtree Street NE, Suite 700 Atlanta,

[SR-Users] How to distinguish 200 OK that have byed

A KA B INVITE -> 200 OK(INVITE)<- ACK is lost BYE <- 200 OK(BYE) -> 200 OK(INVITE)<- 200 OK(INVITE)<- 200 OK(INVITE)<- ACK is lost A

Re: [SR-Users] another bug with JSONRPC-S?

Alright, it was the "params" part that wasn't clear since none of the rest of the MI interfaces I've used with jsonrpc required that. I'll give it a try, thanks! Brooks Bridges | Sr. Voice Services Engineer O1 Communications 5190 Golden Foothill Pkwy El Dorado Hills, CA 95762 office: 916.235.2

Re: [SR-Users] another bug with JSONRPC-S?

Actually my apologies, just tested here on this end the correct parameter name is "htable" not "name" as well, so you will want to adjust it as follows to: curl -s -H 'Content-Type: application/json' --data-binary '{"jsonrpc": "2.0", "method": "htable.dump", "params" : {"htable": "callstats"}}' ht

Re: [SR-Users] another bug with JSONRPC-S?

I believe what you want is something more along the lines of: curl -s -H 'Content-Type: application/json' --data-binary '{"jsonrpc": "2.0", "method": "htable.dump", "params" : {"name": "callstats"}}' http://1.2.3.4:5060/jsonrpc Sincerely, Brandon Armstead On Tue, Apr 19, 2016 at 3:33 PM, Brandon

Re: [SR-Users] another bug with JSONRPC-S?

Brooks, Here is an example call: Ijsonrpc_exec('{"jsonrpc": "2.0", "method": "dlg.end_dlg", "params" : {"h_entry": "$var(h_entry)", "h_id": "$var(h_id)"}, "reply_name": "kamailio_ jsonrpc_reply_fifo", "id": 1}') It looks like you are not specifying params correctly perhaps? Just a quick gue

[SR-Users] I have kamailio with drouting modulo and I want to pass only the RTP trafic to a FREESWITCH server

Hello: I have kamailio with drouting and I want to pass only the RTP trafic to a FREESWITCH o what ever you think is better to manage de RTP traffic. What opcions do I have? I am a little bit confused using WITH_FREESWITCH. I will appreciate your help, Thanks ___

[SR-Users] another bug with JSONRPC-S?

I may have stumbled across another bug with this module. I believe the htable.dump method isn't correctly recognizing that a table name is being provided: [root@server ~]# curl -s --header 'Content-Type: application/json' --data-binary '{"jsonrpc": "2.0", "method": "htable.dump", "name": "cal

Re: [SR-Users] $shtval(htable=>key)

Ah, ok. That makes sense. Thanks! In that same line of thought, is there a clean way to iterate over an unknown list of keys and grab their values? I did see the iteration functions (sht_iterator_*), however it was very clear that the slot should not be updated while it's locked. In this ca

Re: [SR-Users] Kamailio Blind Call Forwarding

Thanks a lot Daniel! topoh-module does what I need. Best Regards Dimitry Nagorny Trainee /*-Ursprüngliche Nachricht- /*Von: sr-users [mailto:sr-users-boun...@lists.sip-router.org] Im Auftrag von /*Daniel Tryba /*Gesendet: Dienstag, 19. April 2016 13:15 /*An: Kamailio (SER) - Users Mailin

Re: [SR-Users] Kamailio Blind Call Forwarding

On Mon, Apr 18, 2016 at 07:26:40PM +0300, Juha Heinanen wrote: > > No, Kamailio cannot build new, independent call legs. This is a > > function of a B2BUA. > > Yes, real easy with SEMS, for example. In the past I have used the topoh module with success to counter such antiloop detection: Avaya IP

Re: [SR-Users] $shtval(htable=>key)

Hello, I corrected the docs in master (devel) branch and will backport soon. It was supposed to be $shtitval(...), a variable that can be used with htable iterators. Also, the wiki page for devel pv cookbook was updated. Cheers, Daniel On 18/04/16 23:02, Brooks Bridges wrote: > > What is this?

[SR-Users] BYE packet looping and loose routing

Hello;     i have trouble with BYE routing and loose routing and kamailio sometimes looping itselft Bye packets.i checked loose routing and bye packet routing here "https://voipmagazine.wordpress.com/2014/12/05/strict-and-loose-routing-of-sip-sequential-requests/"