Yes 141 is opensips I am sending both 3 and 5 register messages when I get from
11 which is ims bench
Samsung Mobile tarafından gönderildi
Orjinal mesaj Kimden: Bogdan-Andrei Iancu
Tarih:09 10 2014 13:45 (GMT+02:00)
Alıcı: Kaan Dandin ,OpenSIPS users mailling
list Cc: K
I think my client never send stun message to the server.
the client find its public ip from the OK VIA header:
Via: SIP/2.0/UDP
192.168.1.3:5070;received=192.168.1.3;branch=z9hG4bK.Klryaqrls;rport=5070
Am I right?
At 2014-10-10 23:36:18, "george wu" wrote:
Hi, all:
I can't see any debug me
Hi, all:
I can't see any debug message for stun on the opensips server side.
I have enabled debug and set up stun as below
loadmodule "stun.so"
modparam("stun", "primary_ip", "192.168.1.3")
modparam("stun","alternate_ip","192.168.122.1")
From the client linphone debug message, I can see
ortp-mes
Hi,
I am working on a special load balancing setup. For specific $rU values, I
want to keep choosen gateway and use cached value for next time. So that,
for each destination, there will be a specific gateway. But I failed at
getting the chosen gw to an avp. I am trying to get it, just before rela
Hi,
You can switch the protocol for the outbound relaying in two ways:
1) force it via the RURI -> add the transport=tls param to RURI :
http://www.opensips.org/html/docs/modules/1.11.x/uri.html#id294426
2) force a TLS socket to be used with force_send_socket() or $fs
http://www.opensips.
Hi,
SIP registration has nothing to do with SIP presence. There are totally
individual mechanisms in SIP.
In presence, when a device starts publishing for the first time, it gets
an etag (a unique id) that will identify the device+publisher.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder an
