I still have the problem of routing the 200 OK message for the REINVITE.
192.168.70.106:5061 is the Kamailio with topos module enabled.
**Here is the REINVITE message arriving from our provider:**
INVITE sip:btpsh-5acddf40-d74-5@192.168.70.106:5061 SIP/2.0
Call-ID: 79acbb714c21354c
Contact:
Con
Well, I've just read the #1421. Let me update the code and test again first.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1350#issuecomment-380412551_
The same problem still exist with the lastest code. That's logic because I had
reported this error before the commit 97532ca
Any help is highly appreciated.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com
### Description
I have an instance of Kamailio running with topos module enabled as described
bellow:
(Core network)<---> (**Kamailio** running on 192.168.70.106:5061) <-->
(Provider network)
Here is the scenario:
1. An INVITE comming from Core network through Kamailio to the Provider
Table topos_d and topos_t before the REINVITE:
**topos_d:**
(id;rectime;s_method;s_cseq;a_callid;a_uuid;b_uuid;a_contact;b_contact;as_contact;bs_contact;a_tag;b_tag;a_rr;b_rr;s_rr;iflags;a_uri;b_uri;r_uri;a_srcaddr;b_srcaddr;a_socket;b_socket)
470690;2018-04-11
18:09:23;INVITE;55;4569feb56b789d
By searching in the code, I found that the error message I had *no valid dlg
uuid (0: - 0:)* is found only in the function tps_storage_update_dialog.
>From my log file, I can say that this error message was showing during the
>handling of the 200 OK (of the RE-INVITE). Hence I suppose that the e
It works @miconda. Thank you very much!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1496#issuecomment-380825960___
Kamailio (SER) - D
Well, it only worked once...
Now I am having the problem of infinite loop when routing the first INVITE of a
new dialog. As if the dialog of an already hung up call is reused for new
calls...
I am investigating and will update this ticket with any new finding.
--
You are receiving this because
These methods allow setting/getting pseudo variable values from Python module.
Pre-Submission Checklist
- [X] Commit message has the format required by CONTRIBUTING guide
- [X] Commits are split per component (core, individual modules, libs, utils,
...)
- [X] Each component has a sing
### Description
The sqlops module run into an infinite loop and print continously this line to
the stderr (or stdout):
22(17903) ERROR: [core/io_wait.h:1040]: io_wait_loop_epoll():
epoll_wait(10, 0x2ab72bb7b690, 0, 5000): Invalid argument [22]
### Troubleshooting
Reproduction
Set log_s
You are right. It stopped printing (and stop running too) after ~70 seconds
after being started.
I guess it tried to connect to the database and the socket get closed
immediately by the OS and the handle to the socket became invalide. However,
the handle was still used in some epoll_wait call
How should we handle RE-INVITE in this case? From what @Joonake said, I deduce
that RE-INVITE from provider to masked contact uri will not find its final
destination.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://
After a closer look, I think the event_route[topos:msg-sending] is called after
the topos module has proceeded the message (restore original headers for masked
messages) so the message would be routed correctly even we call "drop" in the
event route.
--
You are receiving this because you are s
I also have the problem of missing VIA in 200 OK reply but it was for REINVITE
message.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1350#issuecomment-351683326_
Pre-Submission Checklist
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils,
...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] No commits to README files
The version I was using was 5.0.3. I will test with 5.1.0 to see if the problem
still exist.
For the version 5.0.3, the problem goes away when I disable the topos module.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
http
In my case, the reINVITE come in in the same direction as the first INVITE.
I have no special treatment for in dialog request. Juste doing loose_route &
relay.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.
Just tested with 5.1.0 and had the same problem. Bellow is what I got in my log
file. Any idea @miconda?
Dec 14 17:51:43: INFO: loose_route : INVITE sip:+@x:5080
Dec 14 17:51:43: INFO: Relaying a loose route request: INVITE
sip:+@x:5080 (sip:192.168.50.xxx;lr;ftag=205258336;did=b
FYI, the REINVITE has this first line:
INVITE sip:**atpsh-5a32a6fe-162e-1**@192.168.50.xxx:5061 SIP/2.0
In the database, I see the value **atpsh-5a32a6fe-162e-1** in the column a_uuid
of the corresponding call
--
You are receiving this because you are subscribed to this thread.
Reply to this
### Description
Kamailio segfaults when KEMI functions are invoked from app_python script
### Troubleshooting
The same code was running ok with the 5.6 branch.
It seems that the function sr_apy_kemi_exec_func_ex has been re-written in 5.7
with the following main changes :
- The long IF/ELSE
20 matches
Mail list logo
