Closed #936.
--
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/936#event-977268842___
sr-dev mailing list
sr-dev@lists.sip-router.org
http:
The source port < 5060 changed between different tests. It was the same only
per each test.
Thanks for the hint, I will try that in case the issue reemerges. So far I have
been unable to reproduce it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email dire
One more clarification: is that port<5060 always the same, even at different
tests? Or was the same only per each test?
You can try to define `event_route[tm:local-request] { ... }` and force send
socket there (there is a function or can be done with assignment to $fs). I
don't think there is a
Over the lifetime of a kamailio process, I observed messages from two source
ports: the same source port < 5060 for the first or first few REGISTER, and
source port 5060 for all subsequent REGISTER.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directl
Kamailio is always forcing one of its UDP listen sockets when sending out.
The question was if it the issue you observed was using only one other port and
the same always (besides those where kamailio is listening on), or there were
different other ports and many of them from case to case.
--
Can you explain what you mean with a single different source port versus many?
The kamailio instance was not doing anything else besides sending out periodic
registrations to a single provider, so this was very low traffic indeed.
Is it possible to explicitly force the source port for outgoing
Any update on this?
--
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/936#issuecomment-281910932___
sr-dev mailing list
sr-dev@lists.sip-ro
Kamailio doesn't create any other sockests for sending over udp than the ones
set for listen. I can't say for sure if the kernel decides to change that in
case of high traffic, but I doubt that.
Is ther a single sport different than 5060, or there are many?
--
You are receiving this because yo
I apologize for the incomplete report so far. I was tracing the SIP traffic
with `sngrep` and unfortunately did not save the pcap file while I was testing
something else. The registrations with an alternate source port are in fact
hard to reproduce and appear to occur, if at all, only right afte
Can you attach a pcap file with some of suchregistrations? Kamailio should use
the sockets it listens on for sending these requests.
--
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
When registering to an upstream provider using the uac module, the source port
of REGISTER messages alternates seemingly randomly between either 5060 or the
lowest available port, e.g., 1024, 1025, 1026. All SIP providers that I tested
send subsequent INVITEs of incoming calls to the originating
11 matches
Mail list logo
