Iñaki Baz Castillo
Iñaki Baz Castillo
You provider MUST delete the **useless** and **wrong** SRV record for "int.sipserver.alltele.se" and instead create a SRV record for "_sip._udp.int.sipserver.alltele.se".
@jmillan said: > Does that mean they also need two more NAPTR records? Forget it. If the provider does not support SIP TCP/TLS it should not announce it in NAPTR....
Does the 183 response has a Contact header?
The 183 in an above comment doesn't have any Contact header so indeed there is no early dialog established yet and hence JsSIP cannot send in-dialog requests to the remote...
Please, don't pollute existing issues with unrelated questions.
Sorry for the delay. Do you use "use_tls_tunnel" options for both SIP and WS? That means that OverSIP uses separated "stud" processes as TLSTCP gateway. I assume you use them....
> I have a strange issue. When I connect with sipML5 from a web browers to the oversip websocket server via www on port 10443 all is fine if the...
Definitely the second one is wrong since the `Target` class (defined in rfc3263.rb) is: ``` class Target def to_s if self[2] == :ipv4 "#{self[0]}:#{self[1]}:#{self[3]}" else "#{self[0]}:[#{self[1]}]:#{self[3]}" end end end ```...
So, must your OverSIP resolve such a domain (with two different A records) in order to route the received SIP request? Anyhow this is a bug. Theoretically OverSIP does support...