SipCloak service still up

[Matt Clarin]

I came across the sipcloak.org website and hoping to take advantage of it. Is the service still running? Does not appear there has been much activity on this feed.

[Richard Warburton]

Yes, the service still runs :-)  It is however, not being developed at the moment.  Long term I intend to develop a sip library and attempt a true 'Cloak' as opposed to redirect.

Cheers.

[Matt Clarin]

Thank you, any suggestions on why it does not seem to be working for us? Our goal is to simply have a shorter/easier SIP address..  Current config:

Text Host: sip-matt

Txt Value: matt.clarinipco...@ipconsulting.webex.com

SRV Service: _sip

SRV Protocal: _udp

Name: @

Priority: 10

Weight: 10

Port: 5060

Target: server.sipcloak.org

[Richard Warburton]

What is the domain you want to use with the shortened sip address?  I'd like to check your dns settings.

[Richard Warburton]

Hi Matt,

Looks like you've done everything right.  However, doing some testing I have found 2 limitations with sipcloak.org.

1) Not all sip clients use SRV records.  Instead they just use A records.  I'm a bit disappointed about this.  This means that either you point @ at sipcloak's ip (which may change) or you use a CNAME such as sip.yourdomain.com to point to sipcloak.  This means that your sip address becomes user...@sip.yourdomain.com.

2) This is really disappointing.  Some sip clients do not support address redirection.  This essentially means that sipcloak addresses won't work if the caller is using one of these clients.  

http://pbxinaflash.com/community/index.php?threads/free-sip-uri-dialing-service-for-your-own-domain.13302/

I have an idea to solve this, but I'm busy on other projects, so it's months away.  If it's mission critical, SipCloak isn't ready for you.

Sorry.

[Guillaume Roy]

Hello Richard,

First, thank you for this brilliant SIP address redirection idea.

Ideally, SIP providers would offer SIP address mapping to clients who own domain names and DNS servers would offer redirection of SIP calls analogous to email redirection which many DNS servers already offer. Unfortunately, that's far from reality.

Do you mean that SIP clients not supporting SRV records and not supporting redirection are two different issues from a technical perspective? For example, a SIP client may not support SRV records but still support redirection instruction from SipCloak server (achieved using CNAME or A record)? Alternatively, a SIP client could support SRV records but not support automatic redirection instruction from SipCloak server or may require the caller to manually accept redirection?

Wouldn't pointing @ to SipCloak's IP also cause web traffic to one's naked domain to point to SipCloak's server, thereby conflicting with naked domain's website?

Are there any developments since your last post? Would there be a way to redirect calls that would be invisible to the caller's SIP client without SipCloak becoming a proxy and creating latency? Maybe using a call transfer method rather than redirect?

Gratitude,

Guillaume

Victoria, Canada