Open Source SIP Clients
-
-
Blink looks interesting.
-
That's what I thought. Will need to check out Blink.
-
Question, is SIP subject to the same tapping requirements as traditional telephony? If so, does it really matter if we use SKYPE or Blink? it's all being recorded anyhow...
If not, how does that work? It was my understanding (perhaps incorrectly) that SIP wasn't encrypted?
-
@Dashrender nothing but actual PSTN is subject to PSTN regulations. Anything that hit SIP would hit team speak, Lync, XMPP, video conferencing and other audio applications. Every casual application with voice would be impacted.
-
SIP, like HTTP, FTP, XMPP, SMTP is not encrypted. SSL encryption is at a different layer. So SIP traffic is often quite secure. But SIP itself doesn't do the encryption.
-
I remember hearing good things about Jitsi (not specifically on Linux but in general) but have not tried it.
-
Just installed Blink. Trying it out today.
-
What exactly would you use this for? when you're traveling so you can connect directly to a SIP trunk? instead of connecting to your office PBX?
Am I mistaken in thinking that a SIP line is nothing more than an IP based POTS line? (OK it can do a ton more, but you see where I'm going with this)...
-
@Dashrender Most PBXs will do IM/Chat voice and some video.
But, SIP doesn't just mean IP Phone systems sip is a connection type http://en.wikipedia.org/wiki/Session_Initiation_Protocol -
I wish someone would make a fully featured Lync open source alternative. Lync is great but it's so dang expensive for what it is. IIRC it's more than exhcnage is with CALS and all. Openfire is close but it lacks some features and needs more native SSO support that well, actually works.
-
@Dashrender said:
What exactly would you use this for? when you're traveling so you can connect directly to a SIP trunk? instead of connecting to your office PBX?
Am I mistaken in thinking that a SIP line is nothing more than an IP based POTS line? (OK it can do a ton more, but you see where I'm going with this)...
This is my phone. SIP is what you use to connect to the PBX. A soft phone doesn't bypass the PBX. It's just what you can choose instead of a phone on your desk.
-
@thecreativeone91 said:
I wish someone would make a fully featured Lync open source alternative. Lync is great but it's so dang expensive for what it is. IIRC it's more than exhcnage is with CALS and all. Openfire is close but it lacks some features and needs more native SSO support that well, actually works.
Which Lync features do you seek?
-
@Dashrender said:
Am I mistaken in thinking that a SIP line is nothing more than an IP based POTS line? (OK it can do a ton more, but you see where I'm going with this)...
No, SIP is nothing more than a delivery method for phone service. It does not even mean you have an inbound phone number (DID).
@Dashrender said:
What exactly would you use this for? when you're traveling so you can connect directly to a SIP trunk? instead of connecting to your office PBX?
Scott stated how he is using it, but you can use a SIP compatible client to connect directly to a provider also. Technically there is not much difference between a SIP trunk and a SIP connection from a phone (desk or soft) because well, it is SIP. SIP is a standard protocol.
At home I have a Yealink T38G, a Yealink T42G, and an Obi100. The phones talk to PBX systems. The Obi talks to VoIP.ms. I could use the phones to talk directly to VoIP.ms also and just get rid of the Obi100, but it is connected to a cordless phone and I have not gotten around to it yet. The Obi100 does not have a DID. it is used ONLY for outbound calling at home. Generally only for my wife to call her family in Japan. I use it occasionally to test inbound call routing for other systems.
-
Thanks guys, I missed the fact that this was a 'soft phone'
