Women in Technology

Article:		OpenZoep: An Open Source VoIP Engine
Subject:		Dependant on the protocol
Date:		2006-02-08 03:15:46
From:		tanguy_k
This is a nice and simple approach But there is a problem: how can you be compatible with SIP, IAX and other voip protocols? there is no abstraction layer like int makeCall(string phoneNumber) rejectCall(int callId) that will be implemented using whatever voip protocol you like. For the moment nobody knows if XMPP will be the voip protocol that everybody will use and for now I prefer to bet on SIP.

Showing messages 1 through 1 of 1.

• Dependant on the protocol
  2006-02-08 07:03:26  mllarster [View]
  
  
  Zoep uses a SIP protocol for voice signaling, and XMPP used only as a transport for signaling. So you can call it “SIP over XMPP”. For payload transmission RTP is used, in this sense Zoep API is equivalent to any other SIP based phone. From my point it is one of the advantages of the solution as it is uses all benefits of XMPP protocols while it is trivial to connect/integrate it with any existing SIP based system.
  IAX protocol uses one channel for both signaling and payload and not very well fits existing conception by several reasons. So far I did not met any requirement or request on integrating AIX protocol. We can discus it when real necessity appears.
  Good candidate for “other voip protocol” implementation is a Jingle. And it implementation I believe is just matter of a time.
  Currently multiple protocols are not yet supported, but in future it can be done as following: protocol to be used for calling particular user will be selected base on party’s capabilities (using JEP-0030) and user preferences. For example “juliet@capulet.com” can be done using either “SIP over XMPP” or Jingle base on preferences and capabilities of the clients. If there is a wish to make a call using specific protocol then “sip:juliet@capulet.com” will force to use “SIP over XMPP” and “jingle:juliet@capulet.com” will force to use jingle protocol for signaling.