Send Users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://openser.org/cgi-bin/mailman/listinfo/users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Users digest..."
Today's Topics:
1. Re: How to extract sip-id when using alias-id?
(Bogdan-Andrei Iancu)
2. Route Algorithm. (raviprakash sunkara)
3. Re: Forward SUBSCRIBER (Bogdan-Andrei Iancu)
4. RE: 2 Openser Instances (Sam Lee)
----------------------------------------------------------------------
Message: 1
Date: Fri, 26 May 2006 12:35:21 +0300
From: Bogdan-Andrei Iancu <[EMAIL PROTECTED]>
Subject: Re: [Users] How to extract sip-id when using alias-id?
To: Frogger <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Hi,
what you can do is to save into an AVP the alias before doing
lookup(aliases). In failure route, before sending to voicemail, push the
AVP into RURI to have the alias and not the sip id.
regards,
bogdan
Frogger wrote:
Good point.
I need to clarify...
The alias is working to route to the user however if
the timer expires, the route fails or if there is a
reject, the failure routes are applying their logic to
the alias-id not the sip-id.
What I need to do is apply the failure route logic to
the sip-id so we can send the attempt to voicemail.
Let say I have an alias of [EMAIL PROTECTED] for sip-id
[EMAIL PROTECTED]
When [EMAIL PROTECTED] is dialed by another user in the
domain (I am using "use_domain") the call is properly
routed to: [EMAIL PROTECTED]
However, if [EMAIL PROTECTED] does not answer, timer
expires, or a reject, then the failure logic is be
applied to the alias.
Failure route says:
prefix("66");
append_branch();
append_urihf("CC-Diversion: ", "\r\n");
t_relay();
Result of the failure logic:
[EMAIL PROTECTED]
Needs to be:
[EMAIL PROTECTED]
Thoughts?
F
--- Bogdan-Andrei Iancu <[EMAIL PROTECTED]>
wrote:
Hi,
not sure I understand - you dial an alias and via
db_aliases you replace
the alias with the sip-id. So you have the sip-id ..
where is the problem?
regards,
bogdan
Frogger wrote:
I am using alias_db to store alias's for users.
However when an alias is dialed I need to also be
able
to restore the alias owners original sip-id.
This is necessary to forward the call to voicemail
using sip-id.
Any guidance on getting the sip-id out of the
alias_db
and replacing the alias-id prior to forwarding to
vmail?
Thanks in advance!
F
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
------------------------------
Message: 2
Date: Fri, 26 May 2006 05:38:23 -0400
From: "raviprakash sunkara" <[EMAIL PROTECTED]>
Subject: [Users] Route Algorithm.
To: [email protected], "Klaus Darilion"
<[EMAIL PROTECTED]>, [EMAIL PROTECTED],
[EMAIL PROTECTED]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Hi listers and Users.
Please help me in " how to make a call from one place to other place in
route algorithm "
I got Call not approved ? what is this and also $04 and $08 messages as
not
found and request timeout........
It connect ( REgister) to server .
server respond as 1 st " 200 ok " and then " 408 request time out....
plesse help me
Bye..
--
Thanks and Regards with cheers
Sunkara Ravi Prakash (Voip Developer)
Hyperion Technology
www.hyperion-tech.com
<b>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://openser.org/pipermail/users/attachments/20060526/afad0b31/attachment.html
------------------------------
Message: 3
Date: Fri, 26 May 2006 12:42:55 +0300
From: Bogdan-Andrei Iancu <[EMAIL PROTECTED]>
Subject: Re: [Users] Forward SUBSCRIBER
To: Javier Ramirez <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
as I see you are trying to use the PA for presence - that's a different
story. So, what do you want:
1) presence end-2-end directly between end-users
2) presence via PA - the users will talk only with the PA and not
directly.
regards,
bogdan
Javier Ramirez wrote:
I read all documentation from internet, and nothing.
please
if (method=="SUBSCRIBE") {
if (!t_newtran()) {
sl_reply_error();
};
handle_subscription("registrar");
# break;
};
when I coment the "break;" the SUBSCRIBER message is forward to B user.
if I don´t coment the break, the SUBSCRIBER end in OpenSER.
why ?
best Regards
Javier
------------------------------
Message: 4
Date: Fri, 26 May 2006 17:45:44 +0800
From: "Sam Lee" <[EMAIL PROTECTED]>
Subject: RE: [Users] 2 Openser Instances
To: "Klaus Darilion" <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
I tried the cacheless mode, it didn't work for me.
I'm just wondering , how did those people out there do their OUTBOUND
proxy ?
Can anyone give me some hint ?
Regards,
Sam
-----Original Message-----
From: Klaus Darilion [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 4:57 PM
To: Sam Lee
Cc: [email protected]
Subject: Re: [Users] 2 Openser Instances
Sam Lee wrote:
Hi Klaus,
Thanks for the quick reply. My purpose is one of the instance being a
normal Openser, the other with a FORCE RTPproxy. This is so that if
they have a symmetric NAT going on in their network, they can make use
of this rtpproxy as an outbound proxy but still able to call those
register with the normal openser.
Care to explain what is cacheless userloc mode ? How do I set it ?
http://openser.org/docs/modules/devel/usrloc.html#AEN252
it's mode 3 (only available in CVS head)
Because of the normal and force RTPproxy , these 2 instances has
different routing patterns, and they are handled differently.
I still would use only one proxy and apply NAT traversal only for
clients which use the "NAT traversal" port on your openser.
The idea is:
...
if ( dst_port = 6060) { # needs NAT traversal
if (is_method("REGISTER")) {
setflag(9);
# this is the natflag specified in userloc module #
http://openser.org/docs/modules/1.0.x/registrar.html#AEN103
fix_nated_register();
} else {
# do all the NAT traversal, activate RTP proxy
}
}
# now do the normal call and REGISTER handling
...
...
lookup("location");
if(isflagset(9)) {
...#force rtp proxy
}
....
regards
klaus
Any ideas ?
Regards,
Sam
-----Original Message-----
From: Klaus Darilion [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 4:28 PM
To: Sam Lee
Cc: [email protected]
Subject: Re: [Users] 2 Openser Instances
1. You can run several instances of openser on the same PC, but what
is your purpose?
2. If 2 openser proxies share the same userloc database, you have to
use the cacheless userloc mode
3. If you just want to listen on several ports, use a single proxy
with multiple listen directives
listen=udp:1.2.3.4:5060
listen=udp:1.2.3.4:6060
listen=udp:1.2.3.4:7060
regards
klaus
Sam Lee wrote:
Have anyone tried running 2 separate instances on OpenSER (running on
different ports) ?
Both these instances are doing almost exactly the same thing, they
take in REGISTER and save them into the locations database. They all
do all the other processing like INVITE.
Will this causes a problem in MYSQL ? I'm asking this because i got a
very strange problem. I register 1 UA to each instances. When i did a
ul show , it always only have either the UA from instance A or UA
from
instance B . Note, these 2 UA have different numbers. Why can't it
just save both into the MYSQL DB ?
I would be glad to clarify any doubts. Please assist as far as you
can.
Thanks!
Regards,
Sam
---------------------------------------------------------------------
-
--
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
------------------------------
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
End of Users Digest, Vol 12, Issue 71
*************************************
