Hi,
i have mwi running on a server and everything works as expected but
notifications over TLS are not sent.
i tried this with several ip phones (hard and soft)
i can register over tls, make calls, etc
the initial SUBSCRIBE sent by client works as expected and answer is sent
and received.
when the NOTIFY is initiated by the server here is what i get. i setup some
extra debug settings
any thoughts ?
thank you
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:1681]:
notify(): updating subscription to database
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:117]:
printf_subs(): pres_uri: sip:995582130@teste.sip.90e9.com
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:121]:
printf_subs(): callid/from_tag/to_tag:
73da11de-3566eef2(a)192.168.16.15/b302146219721c3/804318313668236640636a8c49438852-3fce
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:122]:
printf_subs(): local_cseq/remote_cseq: 7/1005
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:123]:
printf_subs(): local_contact/contact: sip:192.168.16.145:5061
;transport=tls/sip:995582130@192.168.16.15:5074;transport=tls
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:124]:
printf_subs(): record_route:
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:125]:
printf_subs(): sockinfo_str: tls:192.168.16.145:5061
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:127]:
printf_subs(): event: message-summary
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:1591]:
send_notify_request(): expires 172 status 1
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:1603]:
send_notify_request(): STEP 1
Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence [notify.c:1606]:
send_notify_request(): STEP 2
*Aug 31 23:46:42 sipproxy-01 kamailio[3041]: : <core> [pass_fd.c:157]:
send_all(): ERROR: send_all: send on 17 failed: Bad file descriptor*
*Aug 31 23:46:42 sipproxy-01 kamailio[3041]: ERROR: <core>
[tcp_main.c:2353]: tcpconn_send_put(): BUG: tcp_send: failed to get
fd(write):Bad file descriptor (9)*
*Aug 31 23:46:42 sipproxy-01 kamailio[3041]: ERROR: tm
[../../forward.h:237]: msg_send(): msg_send: ERROR: tcp_send failed*
*Aug 31 23:46:42 sipproxy-01 kamailio[3041]: ERROR: tm [uac.c:506]:
send_prepared_request_impl(): t_uac: Attempt to send to precreated request
failed*
*Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence
[notify.c:1608]: send_notify_request(): STEP 3*
*Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence
[notify.c:1621]: send_notify_request(): NOTIFY
sip:995582130@teste.sip.90e9.com via
sip:995582130@192.168.16.15:5074;transport=tls
on behalf of sip:995582130@teste.sip.90e9.com for event message-summary*
*Aug 31 23:46:42 sipproxy-01 kamailio[3041]: INFO: presence
[notify.c:3107]: pres_notify_watchers(): step 13*
--
Luis Azedo
Hi,
The Flowroute development team is pleased to announce a complete
overhaul of the json and jsonrpc-c modules, originally authored two
years ago.
Credit should first and foremost go to Joe Hillenbrand who did most of
the new development. Jordan Levy (our CTO) and I were also involved in
the updates and QA to a lesser extent.
The updated modules are available in the mgw/json branch.
In addition to the Kamailio modules, we have developed a Twisted
Python library to complement the jsonrpc-c module:
https://github.com/flowroute/txjason
We would be interested in any critiques of the API, documentation, and
code. Please let us know if you use these modules and especially if
you find any bugs.
We hope to merge this into master once we have had it in production
for awhile and (ideally) have received some feedback from other users.
Feel free to contact either Joe (joe(a)flowroute.com) or me directly
with any questions or comments.
--
Matthew Williams
Flowroute LLC
http://www.flowroute.com/
Hello,
not that summer holidays (pretty much) ended, I'm making a call to catch
up with what was left unattended and somehow got lost on the lists,
trackers or repositories. Therefore:
- if someone asked questions without answer on mailing list, send now a
reminder
- if you sent emails to private address (direct message only to personal
emails, not as a request from a mailing list conversation), again, they
are very very unlikely to be answered there, resend the message to
mailing list
- if you opened a tracker issue and have more details, add them as soon
as possible
As for development, I have seen a bunch of commits on personal branches,
if they are not requiring special review, merge them to the master
branch so the code can be easier tested. Soon we will have to freeze for
next major release and it is better to have the code as early as
possible in the main branch.
Have a great autumn,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Oct 21-24; Miami, Nov 11-13, 2013
- more details about Kamailio trainings at http://www.asipto.com -