On 09/19/06 23:21, Ramin Dousti wrote:
> Thanks, Daniel.
>
> So according to the document forward_<proto>(host:port) becomes
> foward(proto:host:port).
>
> But how should I then create a string which replaces the argument of
> forward_tcp(uri:host):
uri:host, uri:port have been eliminated, because when you give no
parameter to forward(), same behavior happen. You can play with
rewriteuri() or setdsturi() to make combinations of how to forward the
request (or you can use avp_pushto() to achive similar results but with
more flexible parameters).
Cheers,
Daniel
>
> forward("tcp:" . uri:host . ":5060");
>
> with . being the concatenation function.
>
> Ramin
>
> On 9/19/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
>> Hello,
>>
>> there was a change in the format of forwarding functions (core and tm),
>> please see:
>>
>> http://openser.org/dokuwiki/doku.php?id=migrating_openser_v1.0.x_to_v1.1.x
>>
>>
>> Cheers,
>> Daniel
>
I belive I'll make it...
And my goal for that evening will be to see if SER-beer tastes as good
as OpenSER-beer :-)....and off cource how many instances you can
run...... before U're out of memory ;-)
br hw
--
Helge Waastad
Senior Engineer
Systemavdelingen
Smartnet
Hi,
Im facing some weird problem, when users register from behind NAT. Let
me try to break it down.
First of all, Im using ser 0.9.6 and my configuration file is almost
identical to that of mediaproxy+nat config file from getting started
bundle. I have asked my friends and colleagues to test my SIP-based
application behind NAT with their ADSL modems and strange thing
happens:
1. While one guy (say user1) has ADSL modem, which gives him address
of 192.168.0.3, he can register w/o problem. Contact header
<sip:user1@192.168.0.3:5060;transport=udp>;q=1.0
is sent in REGISTER request, and received back with 200 OK as
<sip:user1@192.168.0.3:5060;transport=udp>;q=1.0;expires=3600;received="sip:61.47.x.x:5060"
(i have put "x" by myself)
2. Another guy (user2) has ADSL modem connected to a wireless access
point. The application sends in Contact:
<sip:surat@10.0.0.12:5060;transport=udp>;q=1.0
but gets back in 200 OK (attention !!!):
<sip:surat@124.120.x.x:41854;transport=udp>;q=1;expires=3600;received="sip:124.120.x.x:43041"
It gets Contact with a public IP back, which is not the case with
user1. How come?
I *wonder* why this is happening... Some kind of weird NAT?
I'd really appreciate if anyone can shed some light on this issue.
Bests,
Andrey.
Hi all,
I have this message during SER runtime.
10(17177) WARNING: set_timer called on a "detached" timer -- ignoring:
0xf73f01b8
7(17171) WARNING: set_timer called on a "detached" timer -- ignoring:
0xf6186090
10(17177) WARNING: set_timer called on a "detached" timer -- ignoring:
0xf694a60c
3(17163) WARNING: set_timer called on a "detached" timer -- ignoring:
0xf6fe9ecc
2(17161) WARNING: set_timer called on a "detached" timer -- ignoring:
0xf79f50c0
8(17173) WARNING: set_timer called on a "detached" timer -- ignoring:
0xf767ed08
8(17173) WARNING: set_timer called on a "detached" timer -- ignoring:
0xf7482294
3(17163) WARNING: set_timer called on a "detached" timer -- ignoring:
0xf75b56c8
7(17171) WARNING: set_timer called on a "detached" timer -- ignoring:
0xf704f65c
4(17165) WARNING: set_timer called on a "detached" timer -- ignoring:
0xf6862054
Somebody knows what means?
--
Gildo Caceres
Does anybody have samples of using LCR strip and prefix? I've tried
configuring it for an ITSP that wants US numbers to be 10-digits and
international calls to be prefixed with 011. I keep these numbers in
E.164 format, so, for example:
+12128543754 should have the ruri rewritten to: 2128543754
and +44123456789 should become 01144123456789
Here are relevant portions of my lcr tables:
lcr routes
+--------------+----------+--------+----------+
| prefix | from_uri | grp_id | priority |
+--------------+----------+--------+----------+
| +1__________ | % | 5 | 10 |
| +1__________ | % | 7 | 20 |
| +__ | % | 8 | 20 |
| +__ | % | 6 | 10 |
lcr gateways (edited to fit and hide details:-)
+-----------+---------+------+-----+-----+--------+-------+--------+
| gw_name | ip | port | uri_| tran| grp_id | strip | prefix |
+-----------+---------+------------+-----+--------+-------+--------+
| prov1-us | x.x.x.x | 5060 | 1 | 1 | 5 | 2 | |
| prov1-int | x.x.x.x | 5060 | 1 | 1 | 6 | 1 | 011 |
| voip1-int | y.y.y.y | 5060 | 1 | 1 | 7 | 1 | 011 |
| voip1-us | y.y.y.y | 5060 | 1 | 1 | 8 | 2 | |
openser.cfg snippet (our internal dialplan has 93 for outside line):
xlog("L_INFO","route[4]: SIP-to-PSTN call from <$fu> to <$tu>
routed\n");
if (uri=~"^sip:931") {
subst_user('/^931/+1/'); # rewrite to E.164
subst('/^(To:[^0-9]*)931(.*)$/\1+1\2/'); # rewrite to E.164
}
if (uri=~"^sip:93011") {
subst_user('/^93011/+/'); # rewrite to E.164
subst('/^(To:[^0-9]*)93011(.*)$/\1+\2/'); # rewrite to E.164
}
xlog("L_INFO","route[4]: SIP-to-PSTN r-uri is now <$ru>\n");
# rewrite callee's 5-digit extensions to +121285.....
if !((isflagset(6) && !isflagset(4)) || isflagset(5)) {
subst('/^(From:.*<sip:)([134][0-9]{4}@)/\1+121285\2/');
subst('/^(Remote-Party-ID:.*<sip:)([134][0-9]{4}@)/\1+121285\2/');
}
t_on_failure("4"); # if gateway unavail go to 4
if (!next_gw()) {
sl_send_reply("503", "Service not available - No gateways");
return;
};
xlog("L_INFO","route[4]: SIP-to-PSTN after next_gw() r-uri is now
<$ru>\n");
# Cookbook does a forward. I think we do a stateful t_relay which
will handle
# e.g. TCP/UDP or v6->v4 conversion as needed.
if (isflagset(18))
{ #call fwd enabled
append_branch();
}
if (!t_relay()) {
sl_reply_error();
};
xlog("L_INFO","Fell through route[4]: $si: $rm From <$fu> To <$tu>\n");
} # end of route[4]
The observed behavior is that the host part gets rewritten correctly (to
x.x.x.x) but the user part does not get stripped and/or prefixed.
Any help would be appreciated.
/a
Hello all,
SER is started fine, but it looks like it doesn't react to any message arrived to it.
When the SER started the debug information has following message :
0(0) DEBUG: FIFO created @ /tmp/ser_fifo
0(0) DEBUG: fifo /tmp/ser_fifo opened, mode=432
0(0) init_unixsock_socket: No unix domain socket will be opened
Please advice what can be the reason for such behaviour?
Thanks Boris,
Best regards,
Boris Bouslov.
---------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.
Hi,
I just upgraded from v1.0.0 to v1.1.0 and my old config file seem to
have problems,
namely, the line:
...
forward_tc(uri:host);
...
gives a syntax error. I tried to read the release notes but couldn't
find anything
indicading any change.
Thanks in advance,
--
Ramin
Hi all!
Noob question that needs advanced help.
One of my providers will reject calls if valid US callerid is not
presented to them.
I need to find a way to have openSER rewrite bad callerid info. ( If the
user sends valid callerID I would like to preserver that)
To keep it simple.. I would want to rewrite any callerid that is less
than 10 digits.
Could someone point me in the right directions?
TIA!
Cheers,
--
Zac Amsler, Network Operations
NetIQ Systems, LLC www.netiqsys.net <http://www.netiqsys.net>
Halo, guys...
thanx for the time to read this mail
I really need help to solve msilo problems...
I have setup SER server in order to use msilo to deliver offline voice message, it works.
But I really don't know how to add msilo parameter and the logics in my ser.cfg.
Last, how to test whether the msilo module is working or not?
Please give me solutions from this problem.
I will very thank you because my last project in university is about to meet deadline...
Regards,
Meidiana Ten
---------------------------------
Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business.
looks like avpops module documentation does not allow pseudo variables
as avp names although, for example, avp_pushto function does support
them.
1.5.7. avp_pushto(destination,name)
...
name - which AVP(s) should be pushed into the SIP message. Parameter syntax is:
* name = ( avp_name | avp_alias )['/'flags]
* flags = 'g'
and
1.3. AVP naming format
The format of the parameters specifying an AVP in functions exported by
this module is: $avp(avp_flags:avp_name) or $avp(avp_alias).
according to above, for example.
avp_pushto("$ru/domain", "$fd");
should not work, but it does (at least in 1.1.0).
-- juha
