Jan ONDREJ (SAL) schrieb:
> On Thu, Jan 31, 2008 at 04:09:54PM +0100, Iñaki Baz Castillo wrote:
>
>> El Jueves, 31 de Enero de 2008, Andreas Heise escribió:
>>
>>> I search for a simple way to match src_ip from 192.168.1.6 - 192.168.1.11.
>>>
>>> Any ideas, the following aren't working :-(
[EMAIL PROTECTED] wrote:
> Hi,
>
> I'm trying to implement LDAP authentication with anonymous LDAP bind. I set
> the
> ldap configuration file without ldap_bind_dn, ldap_bind_password attributes.
> This step works fine. Unfortunately, I can't figure out how to set the
> openser.cfg file. I need t
Hi,
I'm trying to implement LDAP authentication with anonymous LDAP bind. I set the
ldap configuration file without ldap_bind_dn, ldap_bind_password attributes.
This step works fine. Unfortunately, I can't figure out how to set the
openser.cfg file. I need to pass the bind DN and the user password
All,
I have a situation where I have a OpenSER server frontending a set of
Asterisk boxes (call them box A1 and A2). Calls come in and are routed to
one of the boxes (after doing some custom HTTP lookups using a custom perl
module, rewriting the RURI, etc).
This works fine, however at some point,
Thank you for your reply.
Of course you were right. I have setup everything as you stated. And calls are
reaching the PSTN gateway.. but they are dropped there. I have another post in
the mailing list concerning this new problem
Thanks again for your comments.
-Original Message-
From: He
Thanks for your reply I have used the subst function and as you said it did not
work and that is not what is wrong..could it be different interpretation of the
SIP stack..the GW software is supposed to follow RFC standards.
-Original Message-
From: Bogdan-Andrei Iancu [mailto:[EMAIL PRO
On Wednesday 30 January 2008, Ali Jawad wrote:
> I have successfully setup OpenSer with a mysql backend. I am able to
> make calls using sip phones between registered users. What I need to do
> know is routing calls that start with 00 to my PSTN gateway. But first I
> need to setup OpenSer to route
I cannot pin point the problem, but as you originally said that the GW
is looking for number in TO I just pointed you that this is not correct.
Of course, as an ultimate solution you can abuse the subst() function
from textops module and to brutally change the TO header, but it is not
something
The error message I am getting is Call Failed: Not Found. The thing is
that the GW is working with Asterisk, Linksys phones and other 3rd Party
SIP proxies. Is there something I can do using OpenSer ? I have even
contacted the GW company and they said that they do have clients using
OpenSer.
Thank
Hi Ali,
SIP routing (RFC3261) is done based on RURI and not To URI - TO does not
change in the message. I would say your GW is outdated.
Regards,
Bogdan
Ali Jawad wrote:
>
> Hi All
>
> I am using OpenSER as a proxy to make outbound calls my config is very
> simple if the number dialled is not
Hi All
I am using OpenSER as a proxy to make outbound calls my config is very
simple if the number dialled is not an openser account route it to the
PSTN gw.
if(does_uri_exist()){
# local uri does exist, is probably a user.
# lookup location
if(lookup("location")){
route(1);
return;
}
}
Hi Folks,
My openser is running on SCTP. I'm using SEAS module. I am using a simple
client socket (TCP Socket) program as Application Server(AS) to connect to
SEAS module.
As is written to connect to port 5080 of server. But it does not connect as
is evident from the line (openser' console log):
On Friday 01 February 2008, Ramona Modroiu wrote:
> Hi,
>
> diameter support was developed for DISC (DIameter Server Client project
> at http://developer.berlios.de/projects/disc/). This project seems to be
> no longer maintained and DIAMETER specifications were updated in the
> meantime. Thus I
Hi,
diameter support was developed for DISC (DIameter Server Client project
at http://developer.berlios.de/projects/disc/). This project seems to be
no longer maintained and DIAMETER specifications were updated in the
meantime. Thus I believe the implementation in OpenSER is obsolete and
nee
On Friday 01 February 2008, Ovidiu Sas wrote:
> The diameter implementation in openser is old and outdated.
> You will need to add new functionality to the diameter module to make
> it work with opendiameter.
Hi Ovidiu,
does this means that the openser diameter stuff in ACC is not usable at all?
15 matches
Mail list logo
