Re: [SR-Users] How to append a body to send_reply() ?

2019-04-16 Thread David Dean
Some custom XML. On Tuesday, 16 April 2019, 23:30:49 BST, Alex Balashov wrote: What are you trying to add? —Sent from mobile, with due apologies for brevity and errors. On Apr 16, 2019, at 6:28 PM, David Dean wrote: Hello Kamailio gurus, I'm successfully using send_reply() with 

Re: [SR-Users] Send 200 OK response with body to INVITE requests

2019-04-16 Thread Alex Balashov
Again, the SIP standards forbid this, because proxies just don’t do that! — Sent from mobile, with due apologies for brevity and errors. > On Apr 16, 2019, at 3:57 AM, David Dean wrote: > > As you say, the rtpengine SDP mangling is turn-key with rtpengine_answer(). > It's working perfectly. >

[SR-Users] Getting a new RTP Port on reINVITE during answered call

2019-04-16 Thread Sergio Charrua
Hi all, I've the following infrastructure (fake IPs) 62.128.128.68 (Telco SBC Inbound) | | 10.19.139.66 (Kamailio + RTPEngine) | | 10.19.139.69 (Asterisk 13) | | 62.128.128.68 (Telco SBC Outbound) Test scenario is: - a mobile calls a destination; the call

Re: [SR-Users] Send 200 OK response with body to INVITE requests

2019-04-16 Thread David Dean
As you say, the rtpengine SDP mangling is turn-key with rtpengine_answer(). It's working perfectly. But I'm surprised to find I cannot generate a 200 OK and attach the SDP inside Kamailio. sl_send_reply() would be perfect but it doesn't allow a body to be attached (unless I missed something in

[SR-Users] new RTP Port after INVITE during call

2019-04-16 Thread Sergio Charrua
Hi all, I've the following infrastructure 62.128.128.68 (Telco SBC Inbound) | | 10.19.139.66 (Kamailio + RTPEngine) | | 10.19.139.69 (Asterisk 13) | | 62.128.128.68 (Telco SBC Outbound) Test scenario is: - a mobile calls a destination; the call comes in from

[SR-Users] dlg_onroute(): failed to update dialog lifetime

2019-04-16 Thread Olli Attila
Hello, I just activated snmpstats module on Kamailio 5.0.7 and added the following line to route(INITIAL) at the bottom of the route like this (For noc group to monitor Kamailio dialogs): # Per SIP request initial checks route[INITIAL] { ... dlg_manage(); } Now I started to gets this error few