Hi
I'm still struggling with this problem. My setup is:
mobile sipproviderA kamailio1 - kamailio2 - SIP
user 2001
The SIP user calls the mobile and every thing works fine until the mobile
hangup and the sipproviderA sends a BYE to kamailio1. That bye message has
to "R
Arhhh, I see the problem now in the BYE message send to 188.166.3.25.
188.166.3.25 will the send it back to 188.226.200.111
Route: .
Route: .
Actually 188.226.200.111 is an upstream kamailio test server but it dosen't
remove "Route: " (route to itself).
How can I tell it remove exactly that route
I did try rtpengine_manage() but rtpengine still saves 10.0.0.100 in redis.
I did also try without asymmetric with no luck.
I changed flags in my rtpengine_answer() and rtpengine_offer() to
"replace-session-connection
replace-origin" that saved the public ip correctly and forwarded SDP
correctly.
On Thursday 23 April 2015 01:40:17 Martin Schiøtz wrote:
> I thought that "fix_nated_sdp("2")" would do the job before
> "rtpengine_offer("asymmetric")" but it dosen't have any effect?
My understanding of the docs is that the asymmetric flag introduces the
problem you are experiencing:
asymmetric
On 12 March 2015 at 11:30, symack wrote:
> SIPP is capable of playing media?
>
Yes it is. Take a look at SippyCup to make it easier:
http://mojolingo.github.io/sippy_cup/
>
> N.
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users ma
SIPP is capable of playing media?
N.
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 13 Feb 2015, at 20:07, Richard Fuchs wrote:
> Load balancing is achieved by running a hash over the call-id and using
> the hash value to determine which RTP proxy from the selected set to
> use. The hash ensures that everything related to the same call ends up
> on the same RTP proxy, which
On 13/02/15 01:32 PM, Marc Soda wrote:
> How does Kamailio load balance traffic to rtpengine? Is it load based,
> round robin, etc? The module makes mention of this but I don't see how
> it works. Also, it talks about weighting the proxies. How is that
> accomplished?
This part of the module i
