Does this mean that there is TLS support in SipXproxy in the testing-release of SipX now? I've seen the configuration parameter for the SIP TLS port (5061) but still didn't think it was doing anything for real...
Can I register endpoints using TLS to SipXproxy? Can I send outbound SIP sessions from SipXproxy (without the use of SipXBridge) using TLS? Can I receive inbound SIP sesions (without going via SipXbridge) using TLS? If this i s so, it's great news! =) /Staffan On 18 okt 2010, at 23.23, Tony Graziano wrote: > Please fix the DNS portion before processding. > > When you installed sipx, did you specify the DNS server? Was DNS to be hosted > on sipx? > > Did you specify your sipdomain? > > You should state the version of sipx you are using. You should also check to > see if the correct SRV records are present (wherever you host DNS that sipx > resolves to)... > > It does not sound like there is a: > > _sip._tls SRV records showing port 5061 for your tls domain. > > Editing the xml files directly will wipe your changes after a profile is > resent. > > What version od sipx are you using? > > On Mon, Oct 18, 2010 at 5:02 PM, Arman Güngör <[email protected]> wrote: > Hi all, > > I am experiencing problems when I try to register or make a call through TLS. > > Firstly I had problems with domain alias, sipx was not accepting > mydomain:5061 as its domain. As a workaround for this problem I added > mydomain:5061 into the SIP_DOMAIN_ALIASES etc/sipxpbx/domain-config. > > Secondly I realized that register requests are not forwarded to registrar, as > a workaround I added mydomain:5061 to etc/sipxpbx/forwardingrules. > xml and etc/sipxpbx/sipxproxy-config. > > Thirdly, when TLS client is connected, local IP parameter of its socket is > set to NULL( it was causing problems in the search part for existing clients > ). In order to set that correctly I changed OsSSLConnectionSocket to pass > local ip info to OsConnectionSocket. > > After these changes now phones are able to Register and make a call > successfully. But Polycom IP335 sends its To-Uri with port info ( To: > <sip:2...@mydomain:5061> ) while registering, this again caused domain name > problems in the registrar because mydomain:5061 does not match with any > records in credentials.xml. As a workaround I trimmed port info from the > toUri in source code and this resolved the register problem. But still it > causes problems in making call, because there is "mydomain:5061" in the from > header, sipX can not find the caller in its records. Again trimming the port > part resolves the problem. > > Any suggestion is welcomed. Is there a easier way to configure TLS domain or > am I missing some configuration? > > Thanks, > > Arman > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.326.5325 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > Helpdesk Contract Customers: > http://support.myitdepartment.net > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ -- Staffan Kerker mail/sip/xmpp: [email protected] "There is absolutely no money above the 5th fret..." /Donald "Duck" Dunn
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
