Gracias por vuestra ayuda chicos.. me estoy volviendo loco aquí...
 
 
sí que lo hace.. mirad:
 

No.     Time        Source                Destination           Protocol Info
    744 513.272574  192.168.1.33          66.151.45.116         SIP      Request: REGISTER sip: sip99.yip.com
Frame 744 (404 bytes on wire, 404 bytes captured)
Ethernet II, Src: Agere_ba:91:a2 (00:02:2d:ba:91:a2), Dst: ZygateCo_4d:cc:84 (00:02:cf:4d:cc:84)
Internet Protocol, Src: 192.168.1.33 (192.168.1.33), Dst: 66.151.45.116 (66.151.45.116)
User Datagram Protocol, Src Port: 3060 (3060), Dst Port: 5060 (5060)
Session Initiation Protocol
    Request-Line: REGISTER sip:sip99.yip.com SIP/2.0
    Message Header
        Via: SIP/2.0/UDP 192.168.1.33:3060 ;rport;branch=z9hG4bK8836
            Transport: UDP
            Sent-by Address: 192.168.1.33
            Sent-by port: 3060
            RPort: rport
            Branch: z9hG4bK8836
        From: <sip:8889990@sip99.yip.com>;tag=10315
            SIP from address: sip:8889990@sip99.yip.com
            SIP tag: 10315
        To: <sip:8889990@sip99.yip.com>
            SIP to address: sip:8889990@sip99.yip.com
        Call-ID: 10315@192.168.1.33
        CSeq: 1 REGISTER
            Sequence Number: 1
            Method: REGISTER
        Contact: <sip:8889990@192.168.1.33:3060>
            Contact Binding: < sip:8889990@192.168.1.33:3060>
                URI: <sip:8889990@192.168.1.33:3060>
                    SIP contact address: sip:8889990@192.168.1.33:3060
        Max-Forwards: 70
        User-Agent: Koncept KU2000 3.1.5.1221 Beta
        Expires: 3600
        Content-Length: 0
No.     Time        Source                Destination           Protocol Info
    745 513.619712  66.151.45.116         192.168.1.33          SIP      Status: 401 Unauthorized    (0 bindings)
Frame 745 (476 bytes on wire, 476 bytes captured)
Ethernet II, Src: ZygateCo_4d:cc:84 (00:02:cf:4d:cc:84), Dst: Agere_ba:91:a2 (00:02:2d:ba:91:a2)
Internet Protocol, Src: 66.151.45.116 (66.151.45.116), Dst: 192.168.1.33 (192.168.1.33)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 3060 (3060)
Session Initiation Protocol
    Status-Line: SIP/2.0 401 Unauthorized
    Message Header
        Via: SIP/2.0/UDP 192.168.1.33:3060;rport=3060;branch=z9hG4bK8836
            Transport: UDP
            Sent-by Address: 192.168.1.33
            Sent-by port: 3060
            RPort: 3060
            Branch: z9hG4bK8836
        From: < sip:8889990@sip99.yip.com>;tag=10315
            SIP from address: sip:8889990@sip99.yip.com
            SIP tag: 10315
        To: < sip:8889990@sip99.yip.com>;tag=31e4d59e2970d9bd16e13e238562223e.e948
            SIP to address: sip:8889990@sip99.yip.com
            SIP tag: 31e4d59e2970d9bd16e13e238562223e.e948
        Call-ID: 10315@192.168.1.33
        CSeq: 1 REGISTER
            Sequence Number: 1
            Method: REGISTER
        WWW-Authenticate: Digest realm=" sip99.yip.com", nonce="478d52abccc5d8fe59400728682be83fd7211108", qop="auth"
            Authentication Scheme: Digest
            Realm: " sip99.yip.com"
            Nonce Value: "478d52abccc5d8fe59400728682be83fd7211108"
            QOP: "auth"
        Server: OpenSER (1.2.2-notls (i386/linux))
        Content-Length: 0
No.     Time        Source                Destination           Protocol Info
    746 513.638591  192.168.1.33          66.151.45.116         SIP      Request: REGISTER sip: sip99.yip.com
Frame 746 (602 bytes on wire, 602 bytes captured)
Ethernet II, Src: Agere_ba:91:a2 (00:02:2d:ba:91:a2), Dst: ZygateCo_4d:cc:84 (00:02:cf:4d:cc:84)
Internet Protocol, Src: 192.168.1.33 (192.168.1.33), Dst: 66.151.45.116 (66.151.45.116)
User Datagram Protocol, Src Port: 3060 (3060), Dst Port: 5060 (5060)
Session Initiation Protocol
    Request-Line: REGISTER sip:sip99.yip.com SIP/2.0
    Message Header
        Via: SIP/2.0/UDP 192.168.1.33:3060 ;rport;branch=z9hG4bK41
            Transport: UDP
            Sent-by Address: 192.168.1.33
            Sent-by port: 3060
            RPort: rport
            Branch: z9hG4bK41
        From: <sip:8889990@sip99.yip.com>;tag=10315
            SIP from address: sip:8889990@sip99.yip.com
            SIP tag: 10315
        To: <sip:8889990@sip99.yip.com>
            SIP to address: sip:8889990@sip99.yip.com
        Call-ID: 10315@192.168.1.33
        CSeq: 2 REGISTER
            Sequence Number: 2
            Method: REGISTER
        Contact: <sip:8889990@192.168.1.33:3060>
            Contact Binding: < sip:8889990@192.168.1.33:3060>
                URI: <sip:8889990@192.168.1.33:3060>
                    SIP contact address: sip:8889990@192.168.1.33:3060
        Authorization: Digest username="8889990", realm=" sip99.yip.com", nonce="478d52abccc5d8fe59400728682be83fd7211108", uri="sip:sip99.yip.com", response="7e809df26b9443c5836186e7b99aefe6", algorithm=MD5
            Authentication Scheme: Digest
            Username: "8889990"
            Realm: "sip99.yip.com"
            Nonce Value: "478d52abccc5d8fe59400728682be83fd7211108"
            Authentication URI: "sip:sip99.yip.com"
            Digest Authentication Response: "7e809df26b9443c5836186e7b99aefe6"
            Algorithm: MD5
        Max-Forwards: 70
        User-Agent: Koncept KU2000 3.1.5.1221 Beta
        Expires: 3600
        Content-Length: 0
 
 
pero sigue sin registrarse...
 
he notado que en todos mis traces de otros softphones, el "Digest" es "Digest realm" pero en este es "Digest username"
 
 
Un saludo

2008/1/15 Jesus Rodriguez <jesusr@voztele.com>:
Hola David,


>
> El sip phone no es configurable...
>
> ;-)
>
>
> #
> U 2008/01/14 17:08:34.939709 9.8.7.6:50099 -> 1.2.3.4:5060
> REGISTER sip:my.domain.com SIP/2.0
> Via: SIP/2.0/UDP 192.168.1.94:3060;rport;branch=z9hG4bK17848
> From: <sip:123456@my.domain.com>;tag=2183
> To: < sip:123456@my.domain.com >
> Call-ID: 24493@192.168.1.94
> CSeq: 1 REGISTER
> Contact: <sip:123456@192.168.1.94:3060>
> Max-Forwards: 70
> User-Agent: Koncept KU2000 3.1.4.781
> Expires: 3600
> Content-Length: 0
>
> #
> U 2008/01/14 17:08:34.940324 1.2.3.4:5060 -> 9.8.7.6:50099
> SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP
> 192.168.1.94:3060;rport=50099;branch=z9hG4bK17848;received= 9.8.7.6
> From: <sip:123456@my.domain.com>;tag=2183
> To: < sip:123456@sip99.yip.com>;tag=31e4d59e2970d9bd16e13e238562223e.
> 7071
> Call-ID: 24493@192.168.1.94
> CSeq: 1 REGISTER
> WWW-Authenticate: Digest realm=" my.domain.com ",
> nonce="478bde8ead929899e34e514585c09ad86fb39e8b", qop="auth"
> Server: OpenSER (1.2.2-notls (i386/linux))
> Content-Length: 0
>

Aquí falta señalización. Cuando te intentas registrar en un proxy, el
primer REGISTER se envía sin credenciales y el proxy devuelve un 401
para que el UA envíe el REGISTER con credenciales.

En tu caso, o falta el segundo REGISTER con las credenciales o el 401
no le está llegando al UA y éste no envía el segundo REGISTER.

Saludos
JesusR.





> 2008/1/14 Iñaki Baz Castillo <ibc@aliax.net>:
> El Lunes, 14 de Enero de 2008, David Villasmil escribió:
> > A ver si alguien me puede ayudar con ésto, no encuentro solución.
> Tel UA
> > está cerrado y no lo puedo configurar. El user/pass/realm está
> bien en el
> > openser, aquí un trace
>
> ¿Puedes enviar una captura con ngrep?:
>  ngrep -d any -P ' ' -W byline -T -t "" port 5060
>
> PD: ¿Qué quieres decir con "Tel UA está cerrado y no lo puedo
> configurar"?
>
>
> --
> Iñaki Baz Castillo
>
> _______________________________________________
> Users-es mailing list
> Users-es@lists.openser.org
> http://lists.openser.org/cgi-bin/mailman/listinfo/users-es
>
> _______________________________________________
> Users-es mailing list
> Users-es@lists.openser.org
> http://lists.openser.org/cgi-bin/mailman/listinfo/users-es





Saludos
JesusR.

------------------------------------
Jesus Rodriguez
VozTelecom Sistemas, S.L .
jesusr@voztele.com
http://www.voztele.com
Tel. 902360305
-------------------------------------





_______________________________________________
Users-es mailing list
Users-es@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users-es