This is a follow up to the previous problem. I was able to fix the certificates and stop the codec error, however it's still getting INCOMPATIBLE DESTINATION and hanging up as a result. the debug log looks like this: 2017-05-10 14:40:55.164862 [DEBUG] sofia.c:7257 Remote SDP: v=0 o=- 7420685792921982190 2 IN IP4 127.0.0.1 s=- t=0 0 a=group:BUNDLE data a=msid-semantic: WMS m=application 55446 DTLS/SCTP 5000 c=IN IP4 111.69.178.179 a=candidate:1520298561 1 udp 2113937151 192.168.178.32 55446 typ host generation 0 network-cost 50 a=candidate:2664932878 1 udp 2113939711 2406:e007:2f57:1:1d0a:7773:e5e:f3d4 55447 typ host generation 0 network-cost 50 a=candidate:842163049 1 udp 1677729535 111.69.178.179 55446 typ srflx raddr 192.168.178.32 rport 55446 generation 0 network-cost 50 a=ice-ufrag:cCqv a=ice-pwd:m1PW5eEuaLQiFndNoj8Fm9q5 a=fingerprint:sha-256 AB:05:44:B9:4E:AE:4E:FA:E1:74:DE:0B:8C:41:B4:68:42:96:48:B4:C8:46:5A:20:F9:3B:7A:A8:AC:84:64:8E a=setup:actpass a=mid:data a=sctpmap:5000 webrtc-datachannel 1024 2017-05-10 14:40:55.164862 [NOTICE] sofia.c:7728 Hangup sofia/internal/ 1001@chat.fleetchat.co.nz [CS_NEW] [INCOMPATIBLE_DESTINATION] The sip trace looks like this: SIP/2.0 488 Not Acceptable Here Via: SIP/2.0/WSS 21d9a8odj6h4.invalid;branch=z9hG4bK3506982;received=111.69.178.179;rport=57055 Max-Forwards: 70 From: <sip:1001@chat.fleetchat.co.nz>;tag=400sjnc8e6 To: <sip:1002@chat.fleetchat.co.nz>;tag=Bta6SDNmvt28j Call-ID: 6c5ktogfdljrhk3odh8c CSeq: 7347 INVITE User-Agent: FreeSWITCH-mod_sofia/1.9.0-380-c66a012~64bit Accept: application/sdp Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Reason: Q.850;cause=88;text="INCOMPATIBLE_DESTINATION" Content-Length: 0 Remote-Party-ID: "1002" <sip:1002@chat.fleetchat.co.nz
;party=calling;privacy=off;screen=no
paste bin of extended sip trace: https://pastebin.freeswitch.org/view/304d4f82 I think it's something to do with SCTP, but knowing nothing of this standard, I am not sure if this is the problem i'm facing. I'm guessing it may be not getting the required information between, since if it is trying to send through sctp ports, my server is not currently set up for that. So how do you set up sctp on freeswitch? i have an article im looking at: https://wiki.freeswitch.org/wiki/SIP_TLS which mentions NAPTR and SRV records. Do you need to set up a DNS server to make NAPTR records? Nathan -- *Virtual Guard Ltd* *info@virtualguard.co.nz <info@virtualguard.co.nz>*