Re: [reSIProcate] RFC 5923 alias
On 11/04/12 16:32, Scott Godin wrote:
>
>> you can try out the flow token mode of repro - this allows RFC5626 like
>> behavior for endpoints that don't support it:
>
> I tried that, I'm not 100% sure about the way these settings interact:
> if I do EnableFlowTokens=true, then does the setting of DisableOutbound
> make any difference?
>
> [Scott] You must enable outbound support for any of this to work. ie:
> DisableOutbound = false
>
> How about the relationship between ClientNatDetectionMode and
> EnableFlowTokens? Does EnableFlowTokens supercede
> ClientNatDetectionMode, or do they work together in some way?
>
> [Scott] ClientNatDetectionMode is just more selective than the
> EnableFlowTokens. If you have EnableFlowTokens on, then it doesn't
> matter what the ClientNatDetectionMode is set to.
>
> [Scott] Also make sure you are specifying an appropriate record-routing
> URI - for TLS it should contain domain names in it and not IP addresses.
I've definitely tried all of that, but I still get the same error. I've
taken the most relevant stuff from config and copied it below - is there
anything obviously wrong?
IPAddress = < my fixed IP >
UDPPort = 0
UDPPort = 0
TLSPort = 5061
DTLSPort = 0
TLSDomainName = < CN from cert >
CertificatePath = /etc/repro/ssl
DatabasePath = /var/lib/repro
NumAuthGrabberWorkerThreads = 2
EnableCertServer = false
ThreadedStack = true
Domains = < same as TLSDomainName >
RecordRouteUri = sip:< same as TLSDomainName >;transport=tls
ForceRecordRouting = true
AssumePath = false
DisableRegistrar = false
DisableOutbound = false
OutboundVersion = 5626
EnableFlowTokens = true
ClientNatDetectionMode = DISABLED
FlowTimer = 3600
DisableAuth = false