Re: [reSIProcate-users] what are the uses of DUM
Tanim wrote:
Hello,
I am trying to develop a phone based on voip and I am trying to use
the resiprocate sip stack. I am new with resiprocate. I came across
dum, and am confused about what it does.
DUM abstracts most of the SIP dialog constructs for you. Instead of
worrying about how to populate specific headers, or which messages are
legal to send when, you simply deal with things at the offer/answer level.
Will using it make my development easier?
Much easier, yes.
Is it a good help if someone want to develop with resiprocate while
integrating with a third party media engine and transport interface.
DUM is completely independent of the media layer, including its
transport. You can use whatever media library you want with DUM.
If you want to use your own sockets for the SIP messages, you'll have to
become rather familiar with the Transport class (and its derived
classes) in the stack. Doing so would be far more advanced than simply
using the DUM library and the built-in transports.
What are the uses of dum?
It's primarily for building user agents, although it does handle some
related odd tasks, such as registrar functionality.
If we dont want to use it, what difficulties will we face?
You'll have to implement SIP session semantics. This isn't impossible,
but it's a pretty big task.
/a