Re: [SR-Users] VERY IMPORTANT: deciding when to remove the MI code

+1 - I'm all for cleaning up any technical debt and moving on with more normalized concept. :) Sincerely, Brandon Armstead On Thu, Dec 1, 2016 at 6:17 AM Daniel-Constantin Mierla wrote: > Hello, > > we started discussing about removing MI (so called management interface) >

[SR-Users] VERY IMPORTANT: deciding when to remove the MI code

Hello, we started discussing about removing MI (so called management interface) for very long time, more or less since 2008. The RPC should remain the control interface, given its better structure for commands, parameters, etc ... MI is custom protocol using a line-oriented communication via fifo

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

Hi Daniel, I am trying tm.t_uac_start and its stating Content-Type Missing, I have tried to add to params but it doesnt like it, where should it be defined? Command below; jsonrpc_exec('{"jsonrpc":"2.0","method":"tm.t_uac_start","params": ["INFO",

Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code

Brandon Armstead writes: > +1 - I'm all for cleaning up any technical debt and moving on with more > normalized concept. I'm also in favor of getting rid on MI interface. I'm myself relying only on one MI command (pua_publish) for which an RPC command does not exist (or did not exist last time

Re: [SR-Users] Limiting Registration Contacts

Wouldn't it be more fruitful to delete and reach old bindings in such a scenario? Or are these bindings not only for web clients? On December 1, 2016 5:54:06 PM EST, Colin Morelli wrote: >Hey all, > >I know Kamailio's registrar module has a max_contacts parameter that

[SR-Users] Dual Stack Environments

Hey all, Sorry for two questions out at the same time! I'm using kamailio in front of FS, and I'm about to enable IPv6, but I have a question that I'm not entirely clear on. What's the proper way to forward traffic using the same interface that it came in on? Specifically, if a client connects

[SR-Users] In dialog messages cannot be routed after re-registration with outbound and gruu

Hi, I'm using outbound with gruu enabled and with edge proxy, registrar and auth proxy all running as separate entities. My problem is once a dialog is formed between two UAs, if one side re-registers and gets assigned a new flow token, all subsequent in-dialog messages cannot be routed because

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

Hello, are you still trying with MI command via kamctl? Not with the jsonrpc-s module and tm.t_uac_start? When double quotes disappear is likely due to command line interpreter, so you need to put two of them for each one you have now, then ones than need to stay should be with more

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

Hello, I am currently still using the exec module, so within the .cfg file, as when using jsonrpc-s its coming up with the async command issue again, I presume this will still be the case? Ok I will try with the combinations you mention. Many thanks Jon

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

Hello, tm.t_uac_start is another rpc command than what was tried before, this one doesn't do async operation. Cheers, Daniel On 01/12/2016 13:28, Jonathan Hunter wrote: > > Hello, > > > I am currently still using the exec module, so within the .cfg file, > as when using jsonrpc-s its coming up

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

Hello, have you set modparams for tm module related to reparsing the invite or on dns failover? The build_local() should be used only in some specific cases and want to be sure it doesn't get executed somehow when it shouldn't be. Cheers, Daniel On 30/11/2016 16:40, Helio Okuyama wrote: >

Re: [SR-Users] RTP Pyload

Dear all, We are seeing that some RTP Payload are with 14 bytes and some are with 15 bytes. 1. 14 byte is correct or 15 byte is correct? 2. Is TOC present in all payloads i.e. in all RTP messages? Following example with 14 byte payload. Regards, Amar

Re: [SR-Users] http_async_client - queries

Hi Agalya, can you please provide an example of the data format you'd like to use and the related http_async parameters and request? And possibly also an example of expected final content of the HTTP request? We'll try to better understand what you want achieve. Cheers, Giacomo On 30 November

Re: [SR-Users] RTP Pyload

The query is regarding, while using "Payload type: DynamicRTP-Type-111 (111)" Regrads. From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of amar Smart Telecom Sent: Thursday, December 1, 2016 2:46 PM To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] RTP Pyload

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

Hello, if you haven't changed the tm parameters that refer to reparsing outgoing requests for building local hop-by-hop messages, then you should not be affected by the issue reported by Helio Okuyama. The function that needs to be patched should not used with default values of tm parameters --

Re: [SR-Users] Real error?

Yes, and it is very annoying one. On 2-3 restarts is happens. Not had enough time to troubleshoot it. On 12/01/2016 06:27 AM, Olvera, Victor wrote: Is this a real error? 9(1899) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket

Re: [SR-Users] help with string modification

Hi, All. One more question related to remove_hf... I have added route: # Fix user-agent and server route[RemoveHeader] { remove_hf("server"); remove_hf("user-agent"); return; } I use it form request_route { route(RemoveHeader); . } failure_route[--- all what i

Re: [SR-Users] RTP Pyload

amar Smart Telecom wrote: > We are seeing that some RTP Payload are with 14 bytes and some are with 15 > bytes. > > > > 1. 14 byte is correct or 15 byte is correct? > > 2. Is TOC present in all payloads i.e. in all RTP messages? > > Following example with

Re: [SR-Users] TSILO question

Hi, about your questions: Q1: yes it's feasible as long as the two Registrars (Kamailio) have the location information. Please see my reply on a thread on this topic: http://lists.sip-router.org/pipermail/sr-users/2016-February/091612.html Q2: given that TSILO depends on the users' location you

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

Hello. I make test, currently on kamailio 4.4.0, but as I see in git - tm module does not changes from that time. I have normal line termination. See a dump in attach. in that dump 10.56.41.33 and 10.56.42.33 is the my mhomed kamailio. -- Best regards, Sergey Basov e-mail:

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

On 01/12/2016 02:05, Mikko Lehto wrote: > Helio Okuyama wrote: > >> Local messages are malformed in Kamailio 4.4.X. For example after receiving >> an error response (603) to an INVITE message, the ACK is generated with >> header Max-Forwards concatenated to header CSeq and

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

Daniel-Constantin Mierla : > The specs require to be \r\n. Accepting only \n is and > SER-time-propagated extension in Kamailio from the early days of the > project when a lot of tests during the development was done by building > messages inside a text file and injecting it

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

Hello, Ok cool I will look at it, will it help with syntax issues I have seen with the double quotes so far? Many thanks Jon Get Outlook for iOS On Thu, Dec 1, 2016 at 12:31 PM +, "Daniel-Constantin Mierla" > wrote: