[Kamailio-Users-ES] no logro jalar el modulo msilo con kamailio

troxlinux xserverlinux at gmail.com
Tue Feb 3 00:14:03 CET 2009


señores después de leer la doc del modulo de msilo no logro hacerlo
jalar con mi servidor ..

añadi el modulo dentro del openser.cfg

loadmodule "msilo.so"

modparam("msilo", "db_url", "mysql://openser:mipasswd@localhost/openser")

y dentro de la seccion donde manejo el register añadi

log("REGISTER received -> dumping messages with MSILO\n");

            # MSILO - dumping user's offline messages
            if (m_dump())
            {
                log("MSILO: offline messages dumped - if they were\n");
            }else{
                log("MSILO: no offline messages dumped\n");
            };
            exit;
        };


lo raro de todo esto es que cuando le envió un mensaje a un usuario
que no esta online , el servidor me responde un 405 Method Not Allowed
, y en el log de kamailio veo que el asterisk envía el mensaje , en
ves de kamailio

U +2.896971 192.168.10.35:5060 -> 192.168.10.1:5060
MESSAGE sip:118 at 192.168.10.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.35;rport;branch=z9hG4bKkyvowsnp
Max-Forwards: 70
To: <sip:118 at 192.168.10.1>
From: "rickylaptop" <sip:119 at 192.168.10.1>;tag=xrlqk
Call-ID: cqcjcnjqyojohir at 192.168.10.35
CSeq: 671 MESSAGE
Content-Type: text/plain;charset=utf-8
User-Agent: Twinkle/1.1
Content-Length: 16

test de mensaje
#
U +0.014030 192.168.10.1:5060 -> 192.168.10.35:5060
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.10.35;rport=5060;branch=z9hG4bKkyvowsnp
To: <sip:118 at 192.168.10.1>;tag=329cfeaa6ded039da25ff8cbb8668bd2.0f23
From: "rickylaptop" <sip:119 at 192.168.10.1>;tag=xrlqk
Call-ID: cqcjcnjqyojohir at 192.168.10.35
CSeq: 671 MESSAGE
Proxy-Authenticate: Digest realm="192.168.10.1",
nonce="49877ce734b5f405f7eecb39c411fcaa6d611c80"
Server: OpenSER (1.3.4-notls (i386/linux))
Content-Length: 0


#
U +0.003414 192.168.10.35:5060 -> 192.168.10.1:5060
MESSAGE sip:118 at 192.168.10.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.35;rport;branch=z9hG4bKlqhdbltf
Max-Forwards: 70
Proxy-Authorization: Digest
username="119",realm="192.168.10.1",nonce="49877ce734b5f405f7eecb39c411fcaa6d611c80",uri="sip:118 at 192.168.10.1",response="c9a5781d5ece2fe81f38e1643b0fb706",algorithm=MD5
To: <sip:118 at 192.168.10.1>
From: "rickylaptop" <sip:119 at 192.168.10.1>;tag=xrlqk
Call-ID: cqcjcnjqyojohir at 192.168.10.35
CSeq: 672 MESSAGE
Content-Type: text/plain;charset=utf-8
User-Agent: Twinkle/1.1
Content-Length: 16

test de mensaje
#
U +0.032034 192.168.10.1:5060 -> 192.168.10.1:5070
MESSAGE sip:u118 at 192.168.10.1:5070 SIP/2.0
Record-Route: <sip:192.168.10.1;lr=on;ftag=xrlqk>
Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK1cde.684efe93.0
Via: SIP/2.0/UDP 192.168.10.35;rport=5060;branch=z9hG4bKlqhdbltf
Max-Forwards: 69
To: <sip:118 at 192.168.10.1>
From: "rickylaptop" <sip:119 at 192.168.10.1>;tag=xrlqk
Call-ID: cqcjcnjqyojohir at 192.168.10.35
CSeq: 672 MESSAGE
Content-Type: text/plain;charset=utf-8
User-Agent: Twinkle/1.1
Content-Length: 16
P-hint: inbound->inbound

test de mensaje
#
U +0.000415 192.168.10.1:5070 -> 192.168.10.1:5060
SIP/2.0 405 Method Not Allowed
Via: SIP/2.0/UDP
192.168.10.1;branch=z9hG4bK1cde.684efe93.0;received=192.168.10.1
Via: SIP/2.0/UDP 192.168.10.35;rport=5060;branch=z9hG4bKlqhdbltf
From: "rickylaptop" <sip:119 at 192.168.10.1>;tag=xrlqk
To: <sip:118 at 192.168.10.1>;tag=as19a0f0de
Call-ID: cqcjcnjqyojohir at 192.168.10.35
CSeq: 672 MESSAGE
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0

alguna idea?

saludoss

-- 
rickygm

http://gnuforever.homelinux.com




More information about the Users-es mailing list