1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
libnet-sip-perl (0.802-1) unstable; urgency=medium
From upstream Changes for 0.800:
- important, partly incompatible API changes
- Leg::new and Simple::new now croak when unexpected arguments are given
- Internals changed for more code reability and to take care of TLS where the
hostname is needed for certificate validatin. Lots of structures are now
managed by (restricted) hashes which were previously implemented as arrays.
Anybody grabbing in the internals will probably need to adjust code.
Affects partly the more public functions of Leg and Dispatcher too.
-- gregor herrmann <gregoa@debian.org> Sat, 26 Nov 2016 18:36:12 +0100
libnet-sip-perl (0.702-1) unstable; urgency=medium
From upstream Changes for 0.700:
- major API changes !!!
- proxies, registrars etc are no longer given with udp:/tcp: prefix to signal
which protocol gets used but instead SIP URL's are used:
sip:... - SIP over UDP
sip:...;transport=TCP - SIP over TCP
sips:... - SIP over TLS
the simplified syntax without protocol specification still works and is
considered as before as SIP over UDP
- Util: result of sip_uri2parts changed
from (domain,user,proto,param,data)
to (domain,user,proto,data,param)
- Eventloop - addFD, delFD now take argument $rw to specify if the handler is
for read or for write. If omitted in delFD it will remove all handlers for
fd as before. Wrong (old) usage with addFD will result in Carp::confess.
!!! When integrating with its own eventloop this is also the interface this
loop is expected to provide !!!
- Dispatcher::deliver: arguments dst_addr now [proto,ip,port,family] instead
of string. Using string with SIP URI is also still supported but not
official API but existing code without protocol specification in string
should thus still work.
- Endpoint::register expects SIP URI, i.e. no longer adds 'sip:' prefix
- fields or meaning of fields in Leg, Packet, Dispatcher::Packet changed but
nobody should have accessed these internals anyway
- Leg::deliver: destination given as [proto,ip,port,family] instead of
ip:port string
- Leg::sendto takes packet object instead of packet string, dst as single
argument with [host,port,family] instead of separate addr and port arguments
- Leg::receive now gets (packet,from) and returns the same (might modify data
but currently doesn't). Previously reading of the packet was done inside
this function but now reading is done by SocketPool and Leg just has the
option to process packet.
-- gregor herrmann <gregoa@debian.org> Thu, 17 Nov 2016 18:36:18 +0100
|
