New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
topos: retry initial INVITE - no Contact #1356
Comments
miconda
added a commit
that referenced
this issue
Dec 24, 2017
- recover them on retransmissions, otherwise no contact header is added on initial request routing - reported by GH #1356
This should be fixed with the commit referenced above. Reopen if still an issue. |
Thank you Daniel. It is work as expected now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When callee device not reachable kamailio tries to reach it, I have profile with 3 retries with 1second interval.
But Contact header present only in 1-st Invite. Next Invites are send without Contact header...
With topoh module - Contact normal in all INVITES.
Troubleshooting
Reproduction
Load and configure topos module
Create permanent location record which is unreachable.
Make call to it. make sure that you have profile with retries.
Log Messages
kamailio.tar.gz
SIP Traffic
retry-Invite-on-not-reach.tar.gz
Additional Information
Kamailio Version
version: kamailio 5.2.0-dev1 (x86_64/linux)
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled on 14:50:56 Dec 8 2017 with gcc 4.8.5
Operating System:
Red Hat Enterprise Linux Server 7.3
3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: