[serusers]: trusted table(permissions module)

[Kamal.Mann at t-systems.com]

Hi 
Please find ser.cfg enclosed.

Trusted table entry:
+---------------+-------+--------------+
| src_ip        | proto | from_pattern |
+---------------+-------+--------------+
| 10.25.119.156 | any   | ^sip:.*$     |
+---------------+-------+--------------+
1 row in set (0.00 sec)

Thanks in anticipation
Kamal Mann
-----Original Message-----
From: serusers-bounces at lists.iptel.org [mailto:serusers-bounces at lists.iptel.org] On Behalf Of Andrey Kuprianov
Sent: Wednesday, November 01, 2006 7:03 PM
To: serusers at iptel.org
Subject: Re: [serusers]: trusted table(permissions module)

  Hi Kamal,

I understand your setup. Nevertheless, it will be difficult to figure
out your problem, w/o your ser.cfg file at hand. Also, send a trusted
table query result (i.e. that row which contains entry for your
SIP-AS).

   Regards,

     Andrey.

On 11/1/06, Kamal.Mann at t-systems.com <Kamal.Mann at t-systems.com> wrote:
> Hi All
> In my scenario I need ser to communicate with my SIP-AS. This SIP-AS is having an application xyz running on it. This XYZ sends an invite to URI "A at xcv.de" which is a subscriber in SER and this is in TO header of Invite msg & FROM header contains another URI test at xcv.de but this URI (test at xcv.de) isn't registered / subscribed to SER. I need SER trust all packets from SIP-AS ip. BUT SER is sending 407 reply of INVITE to XYZ application! IP in trusted table is of SIP-AS on top of which XYZ application is running.
>
> Thanks in anticipation
> Kamal Mann
>
> -----Original Message-----
> From: Maciej Żwirski [mailto:mzwirek at poczta.fm]
> Sent: Wednesday, November 01, 2006 3:20 PM
> To: serusers at lists.iptel.org
> Subject: Re: [serusers]: trusted table(permissions module)
>
> Kamal.Mann at t-systems.com wrote:
>
> > Hi All
> >
> > I made an entry /"10.25.119.156, any, ^sip:.*$"/ into trusted table so
> > that any packet sent from 10.25.119.156 would be trusted by SER and
> > don't ask for its credentials. But SER is replying *407- proxy* auth
> > needed!!  After this I tried with permissions.allow file:
> >
> Hi,
> I had the same issue while interconnecting SER and Asterisk. It turned
> out to be an issue on Asterisk side (I had the same user added for SER
> and Asterisk, so the poor thing couldn't authorize either :)) So you
> could check if the 407 you're getting is from SER or from the remote host.
>
> Regards,
> Maciej Zwirski
>
> ----------------------------------------------------------------------
> Jestes kierowca? To poczytaj! >>> http://link.interia.pl/f199e
>
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ser.cfg
Type: application/octet-stream
Size: 12219 bytes
Desc: ser.cfg
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20061102/9cd0917d/attachment.obj>