Sorry to hijack this thread, but I was trying to follow along (Kamailio 4.1.4) and everything seems OK except that when the offline user registers and msilo attempts to deliver his messages, I get this "no corresponding socket for af 2" error and the messages remain in the db. I have TLS enabled in kamailio.cfg (listen=tls:79.xx.xx.xx:5061 listen=tcp: 127.0.0.1:5060), and calls work fine. The only issue I can see is with msilo dumping the messages when the user signs in.
Any clue as to why it's not able to find the socket? Thanks, Peter Jul 6 18:40:06 pbx /usr/sbin/kamailio[20634]: NOTICE: <script>: -------------------------MESSAGE PROCESSING: dumping offline messages Jul 6 18:40:09 pbx /usr/sbin/kamailio[20635]: ERROR: tm [ut.h:343]: uri2dst2(): no corresponding socket for af 2 Jul 6 18:40:09 pbx /usr/sbin/kamailio[20635]: ERROR: tm [uac.c:266]: t_uac_prepare(): t_uac: no socket found Jul 6 18:40:09 pbx /usr/sbin/kamailio[20635]: ERROR: tm [ut.h:343]: uri2dst2(): no corresponding socket for af 2 Jul 6 18:40:09 pbx /usr/sbin/kamailio[20635]: ERROR: tm [uac.c:266]: t_uac_prepare(): t_uac: no socket found On Wed, Jun 18, 2014 at 11:38 AM, Marc M. <proy...@hotmail.com> wrote: > Hi Daniel! > > I applied now the source ip check and it is working! > > Thanks a lot! > > regards > > Marc > > ------------------------------ > From: proy...@hotmail.com > To: sr-users@lists.sip-router.org > Date: Tue, 3 Jun 2014 21:38:32 +0000 > Subject: [SR-Users] MSILO - dumped messages get duplicated > > Hi, > > I have a Kamailio 3.2 setup up and running. > Recently I configured msilo for offline message store. Essentialy the > setup runs fine. > > Messages to users without location info getting stored. > In case the user has location info, but cannot be reached, I made > failover_route, so the messages getting stored in this case too. > Messages getting dumped at the next REGISTER. > > However, I have a group of new mobile clients, with unstable connection. > It happens many times that they send a REGISTER, but the connection brakes > afterwards. > > It this case the message is getting dumped, but since it cannot be > delivered, it runs on the failover_route which stores the message again. > However, the previous message is not removed from the db, so the same > message is now twice in the db. > Next time the message either gets delivered in double, or in case of a new > failure, it gets stored 2x2= four times. > > I need to avoid this duplicates but still make sure the message get > delivered sooner or later. > Any help is highly appreciated. > > Here is my routing table: > > thanks > Marc > > > > _______________________________________________ SIP Express Router (SER) > and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > >
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users