DM == Daniel-Constantin Mierla mico...@gmail.com writes:
DM Also, I changed the default value of Content-Encoding header value
DM from gzip (which I saw in rfc 3261) to deflate, which is used by
DM FaceTime, but more important works with Firefox out of the box. Thus I
DM assumed is the right
On 18.09.2013 12:17, Daniel-Constantin Mierla wrote:
On 9/18/13 12:04 PM, Øyvind Kolbu wrote:
Correct, no NAPTR. Only SRV, but until yesterday, no _sip._udp and then
it immediately tried an A lookup instead of attempting _sip._tcp.
I have also tried to set those prefs, but it did not help.
I
Hi Vitaliy,
On 09/24/2013 12:45 AM, Vitaliy Aleksandrov wrote:
The patch only handles the case where a tcp connection is directly
made to the registrar, as no event route is fired, right?
You are right. Current version works only when registrar accepts tcp
connections.
Anyway it's a good idea
Andreas Granig writes:
The reason I'd love to see an event-route is to handle cases for scaled
architectures, where you have load-balancers/edge-servers accepting
tcp/tls connections from clients and forward them to a back-end farm of
registrars/proxies e.g. via udp.
another application
Hi,
you could use for example RFC3680 (A Session Initiation Protocol
(SIP) Event Package for Registrations) to synchronize the information
about the connection status between the edge- and the core-proxy. This
is the way it is done in IMS for information about the signalling
status (Diameter/Rx).
Hi websocketeers, examples/websocket.cfg starts with this check:
---
request_route {
if ((($Rp == MY_WS_PORT || $Rp == MY_WSS_PORT)
!(proto == WS || proto == WSS)) || $Rp == MY_MSRP_PORT) {
xlog(L_WARN, SIP request received on $Rp\n);
The above sanity check is intended to make sure that:
- SIP over TCP/TLS arriving on the ports intended for SIP over WebSocket
is correctly rejected
- SIP over TCP/TLS arriving on the port intended for MSRP is correctly
rejected
In examples/websocket.cfg with default settings:
-
Hello,
I'm having trouble understanding how Kamailio keeps track of contacts
when used as an outbound proxy. When using Kamailio as the registrar,
contact information for each endpoint is generally stored in the
locations table.
However, when Kamailio is used as an outbound proxy, the
