Re: [repro-users] Authenticated identity check problem
Repro does not currently validate identity headers in inbound requests.
If you write a UA with DUM, then you can enable identity header
validation checking. It will not automatically reject the message -
however it will tag is as not-verified, and your application can decide
to reject the request or not.
Since repro only uses DUM for registrations - it shouldn't be that hard
to get repro to check the identity headers of registrations - but that
will only work for registrations and not Invites, etc.
Scott
> -----Original Message-----
> From: repro-users-bounces@xxxxxxxxxxxxxxx [mailto:repro-users-
> bounces@xxxxxxxxxxxxxxx] On Behalf Of Gergely Kovacs
> Sent: Thursday, October 11, 2007 12:31 PM
> Cc: repro-users@xxxxxxxxxxxxxxx
> Subject: [repro-users] Authenticated identity check problem
>
> Hi,
>
> I'd like to have repro check identity headers. I run two repro on the
> same machine:
>
> Machine A (port 5060)
> domain: a.com
> user: root@xxxxx
> route uri: ^sip:([^@]+)@a.com.*$
> route sip:$1@xxxxx:5062
>
> Machine B (port 5062)
> domain: b.com:5062
> user: root@xxxxx:5062
>
>
> root@xxxxx calls root@xxxxx; root@xxxxx authenticates himself, a.com's
> repro inserts identity headers, message is forwarded to b.com:5062,
but
> b.com does not check identity!
>
> What could be the problem? (repro is the latest version in SVN)
>
> Cheers,
> Gergely
>
> _______________________________________________
> repro-users mailing list
> repro-users@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/repro-users