Hello Guys,
I would like SER not to mask the FROM field when its sending a call to
another sip proxy/gateway. What Im getting on the destination gateway is the
IP of the SER. I wouldnt want SER to proxy/mask the original IP address of
the UAC. Is this possible. Here is a sample callflow:
UAC (192.168.10.10) >> SER (192.168.11.10) >> UAS (192.168.12.10)
i would like the FROM on the UAS to look like 123456(a)192.168.10.10 and not
123456(a)192.168.11.10 which is the SER's IP.
Please help. Thanks in advance.
Hi Bastien,
If you see incoming and outgoing udptl traffic on both SIP-FAX
devices, capture it and load the file on wireshark. Check the T.38
signaling and see where it is failing and why.
As an example/reference, use a capture from a working case.
Regards,
Ovidiu Sas
On 11/17/06, Bastian Schern <ml02(a)in-bln.de> wrote:
> Hi Bogdan,
>
> I think it has nothing to do with a deadlock. I see the incoming and
> outgoing UDPTL traffic on both SIP-FAX devices.
>
> Do you got a suggestion for me, what I could do to locate and resolve the
> problem.
>
> Cheers
> Bastian
>
> --On Donnerstag, 16. November 2006 14:12 +0200 Bogdan-Andrei Iancu
> <bogdan(a)voice-system.ro> wrote:
>
> > Hi Bastin,
> >
> > probably there is kind of a RTP deadlock between the RTPproxy and
> > OpenPBX - both are waiting for the other party to send the media before
> > sending on its turn.
> >
> > try something like:
> > if (nat_uac_test("8")) {
> > force_rtp_proxy();
> > } else {
> > force_rtp_proxy("r");
> > }
> >
> > refer to http://www.openser.org/docs/modules/1.2.x/nathelper.html for
> > more details.
> >
> > regards,
> > bogdan
> >
> >
> > Bastian Schern wrote:
> >
> >> Hi everybody,
> >>
> >> I've got a question: Does anybody get T.38 working between OpenPBX and
> >> OpenSER + RTPProxy?
> >>
> >> The following scenarios are working fine:
> >>
> >> 1: SIP-FAX1 (pub. IP) <-> OpenPBX <-> SIP-FAX2 (pub. IP)
> >> 2: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> SIP-FAX2 (pub. IP)
> >> 3: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> SIP-FAX2 (NAT)
> >> 4: SIP-FAX1 (pub. IP) <-> OpenSER <-> OpenPBX <-> SIP-FAX2 (pub. IP)
> >>
> >>
> >> But the following scenario is not working:
> >>
> >> SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> OpenPBX <-> SIP-FAX2 (pub. IP)
> >>
> >>
> >>
> >> It seems to be that the RTPproxy has a problem with the OpenPBX but no
> >> Problem with SIP-FAX-ATAs.
> >>
> >> Does anybody have an idea what's going wrong???
> >>
> >>
> >> Cheers
> >> Bastian
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users(a)openser.org
> >> http://openser.org/cgi-bin/mailman/listinfo/users
> >>
> >
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
Hi everybody,
I've got a question: Does anybody get T.38 working between OpenPBX and
OpenSER + RTPProxy?
The following scenarios are working fine:
1: SIP-FAX1 (pub. IP) <-> OpenPBX <-> SIP-FAX2 (pub. IP)
2: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> SIP-FAX2 (pub. IP)
3: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> SIP-FAX2 (NAT)
4: SIP-FAX1 (pub. IP) <-> OpenSER <-> OpenPBX <-> SIP-FAX2 (pub. IP)
But the following scenario is not working:
SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> OpenPBX <-> SIP-FAX2 (pub. IP)
It seems to be that the RTPproxy has a problem with the OpenPBX but no
Problem with SIP-FAX-ATAs.
Does anybody have an idea what's going wrong???
Cheers
Bastian
Hi!
Is it possible to deactivate the 100 Trying during t_relay? I want to
use sl_send_reply("100","trying"), thus the implicit 100 trying during
t_relay is not needed.
regards
klaus
--
Klaus Darilion
nic.at
I can not use "nat.uac" and "nat.uas" as registrar flags:
0(12872) str2s: ERROR: unexpected char N in NATuac
0(12872) set_mod_param_regex: 'registrar' matches module 'registrar'
0(12872) find_param_export: found <load_nat_flag> in module registrar
[/usr/local/lib/ser/modules/registrar.so]
0(12872) set_mod_param_regex: found <load_nat_flag> in module
registrar [/usr/local/lib/ser/modules/registrar.so]
0(12872) str2s: ERROR: unexpected char N in NATuas
Bogdan,
Thank you.I did it, but doesn't work. I will try to implement my own
radius extra solution.
Antal
-----Original Message-----
From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro]
Sent: Thursday, November 16, 2006 1:19 PM
To: Pletli Antal
Cc: users(a)openser.org
Subject: Re: [Users] Radius extra: integer attribute type how to
Hi Antal,
If I'm not wrong, all extra accounting information is added as string
(it's a limitation because of using several backend), so you may try
configuring the attribute in the RADIUS dictionary as string and not
integer.
regards,
bogdan
Pletli Antal wrote:
> Hello,
>
> I'm trying the radius-extra feature in openser cvs snapshot.
>
> In my openser.cfg I set up the following parameter:
>
> modparam("acc", "radius_extra",
> "Acct-Session-Time=$avp(call_length)")
>
> modparam( "avpops", "avp_aliases", "start_timestamp=i:100")
> modparam( "avpops", "avp_aliases", "end_timestamp=i:101")
> modparam( "avpops", "avp_aliases", "call_length=i:102")
>
> (...)
>
> avp_op("$avp(end_timestamp)","sub/$avp(start_timestamp)");
>
> avp_op("$avp(end_timestamp)/$avp(call_length)","sub/$avp(start_timesta
> mp)");
>
>
>
> I have experienced that when I sent an Accounting-Stop request to
> radius server, it received the integer value as an string and it
> decoded the value to the chr code of the "3"
>
> In the radius log:
>
> * Attr: 46 - Acct-Delay-Time len: 6 val: 51
>
> In the openser.log:
>
> Nov 14 16:12:09 sip2 ./openser[727]: INFO:avpops:print_avp:
> p=0x40623b88, flags=0x0000
> Nov 14 16:12:09 sip2 ./openser[727]: INFO:
id=<102>
> Nov 14 16:12:09 sip2 ./openser[727]: INFO:
> val_int=<3>
>
> How can I set the corresponding integer attribute in the request?
>
> Thanks in advance,
>
> Antal
>
>-----------------------------------------------------------------------
>-
>
>_______________________________________________
>Users mailing list
>Users(a)openser.org
>http://openser.org/cgi-bin/mailman/listinfo/users
>
>
Hello,
A new SER database migration tool is available at:
http://iptel.org/ser/migrate_db
The tool can be used to migrate the contents of the old SER database
used in releases 0.9.x into the new schema used in 0.10.x.
Please report bugs to serdev(a)iptel.org
Jan.