[Serusers] rtp-asymmetric-clients problem.

[samuel]

The asymetric file pattern is compared against the User-Agent header
and there's no such header in your 200 OK.
I'm afraid you can not use these files to check the Server header but
I haven't used these functionality so maybe out there can expand my
limited knowledege..

Hope it helps,
Samuel.

2006/10/17, Ricardo Martinez <rmartinez at redvoiss.net>:
>
>
>
> Hello User.
>         I using a rtp-asymmetric client in my platform, i want to add this
> client as a asymmetric client so i using this configuration.
>
> [ser.cfg]
> modparam("mediaproxy", "rtp_asymmetrics",
> "/usr/local/etc/ser/rtp-asymmetrics-clients")
>
> [rtp-asymmetric-clients file in /usr/local/etc/ser/]
> #
> # Lines starting with a '#' character or empty lines are ignored.
> # Put a User-Agent name or regular expression per line.
> # Check is case insensitive.
> #
> # This file should only list SIP clients that are asymmetric regarding
> # the RTP media streams. For clients that are asymmetric regarding the SIP
> # signaling, use the equivalent SIP version of this file.
> # Clients that are asymmetric for both SIP signaling as well as RTP media
> # streams should go in both files.
> #
>
> SIPquest-SIPH323-Gateway/R2-23
>
>
> When the 200 - OK from the asymmetric client arrive :
>
> SIP/2.0 200 OK.
> Via: SIP/2.0/UDP 100.100.148.246;branch=z9hG4bK9eda.3d49eaf1.0.
> Via: SIP/2.0/UDP
> 192.168.1.100;received=100.100.148.248;rport=46107;branch=z9hG4bKc0a801640000004b453532800000783900000087.
>
> Record-Route: <sip:100.100.154.36;ftag=10302336931863;lr=on>.
> Record-Route:
> <sip:7072408196 at 100.100.148.246:5060;nat=yes;ftag=10302336931863;lr=on>.
> From:
> "unknown"<sip:5502408196 at sip.desa.mydomain.net>;tag=10302336931863.
> To: <sip:7072408196 at sip.desa.mydomain.net>;tag=3235014976.
> Call-ID:
> E2BBA13E-A3CA-4E54-91C0-C30AF6466324 at 192.168.1.100.
> Cseq: 2 INVITE.
> Date: Tue, 17 Oct 2006 19:44:02 GMT.
> Server: SIPquest-SIPH323-Gateway/R2-23.
> Content-Type: application/sdp.
> Content-Length: 162.
> Contact: sip:7072408196 at 100.100.154.119.
> .
> v=0.
> o=100.100.154.119 1 627067186 IN IP4 100.100.154.119.
> s=SIP Library call.
> c=IN IP4 100.100.148.230.
> t=3370103042 0.
> m=audio 17322 RTP/AVP 0.
> a=rtpmap:0 PCMU/8000.
>
> Oct 17 16:45:18 sip mediaproxy[1783]: command lookup
> E2BBA13E-A3CA-4E54-91C0-C30AF6466324 at 192.168.1.100
> 100.100.148.230:17322:audio 100.100.154.36 sip.desa.mydomain.net local
> sip.desa.mydomain.net unknown SIPquest-SIPH323-Gateway/R2-23
> info=from:5502408196 at sip.desa.mydomain.net,to:7072408196 at sip.desa.mydomain.net,fromtag:10302336931863,totag:3235014976
>
> Oct 17 16:45:18 sip mediaproxy[1783]: command execution time:  0.55 ms
> Oct 17 16:45:18 sip mediaproxy[1783]: session
> E2BBA13E-A3CA-4E54-91C0-C30AF6466324 at 192.168.1.100: caller
> signed in from 100.100.148.248:49172 (RTP) (will return to
> 100.100.148.248:49172)
>
> Oct 17 16:45:18 sip mediaproxy[1783]: session
> E2BBA13E-A3CA-4E54-91C0-C30AF6466324 at 192.168.1.100: called
> signed in from 100.100.148.230:17090 (RTP) (will return to
> 100.100.148.230:17090)
>
> There is no match with the rtp-asymmetric-clients file ?
>
> What i'm doing wrong?
> I hope that someone can help me here.
>
> Thanks
> Ricardo.-
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
>
>