Hi all,
I have a module to process SIP message (INVITE, INFO, 200 OK, BYE). I have use
t_relay function to capture 200 OK message in block onreply_route. But, After I
use t_relay function, INFO, BYE, some ACKs messages cannot route to
destination. If I insert some t_relay function in config fil
Hello Brett,
The SIPp scenarios are configured to handle the correct flow. If I run the SIPp
UAC directly with the SIPp UAS I don't get the errors, it just happend when I
use the OpenSIPs as a proxy. And that error doesn't occur on every call, is
just in some. After I disabled the logging, I'm
Luis,
Your scenario isn't setup to properly handle the call flow. The error
message clearly shows that 200 was expected but 180 was received.
-Brett
On Monday, September 12, 2011, Luis Morales
wrote:
>
>
>
>
>
> The script is simply forwarding requests and responses in a stateless manner.
> I've
The script is simply forwarding requests and responses in a stateless manner.
I've tried the simple stateful configuration in the opensips site, but I've
like to try it with the stateless configuration. Here's the script I'm using:
### Global Parameters #
debug=0log_stderror=no
for
Can't really tell without seeing what the errors are and what your script is
doing. Are you doing any database lookups??
-Brett
On Sep 12, 2011, at 9:18 PM, Luis Morales
wrote:
Hello Brett,
You're right, I forgot to check the logging. I disabled it and it's working
better. I'm still getting so
Hello Brett,
You're right, I forgot to check the logging. I disabled it and it's working
better. I'm still getting some unexpected messages error, but a lot less than I
was getting before. Thanks for your help. Do you know if there's something else
I could do so I could stop getting the errors.
On Mon, Sep 12, 2011 at 10:57 AM, Akib Sayyed wrote:
> yah but even if radius gives error mediaproxy should work
>
If you have included an erroneous configuration for radius it will prevent
anything from working properly. Debuging is irrelevant if you have other
parts of your configuration that
Have you checked if relay and dispatcher are actually running?
Have you run them in the foreground with debug turned on to see why
use_media_proxy returned an error?
I'm betting Brett is right that radius is at least primarily the problem.
I would disable it's use in opensips.cfg and mediaproxy/con
please i want instruction to install mediaproxy
On Mon, Sep 12, 2011 at 9:58 PM, Adrian Georgescu wrote:
> That web site instructions are completely bogus
>
> Adrian
>
> On Sep 12, 2011, at 5:39 PM, Akib Sayyed wrote:
>
> Guys i want step by step guide for installing and running mediaproxy.
> i f
That web site instructions are completely bogus
Adrian
On Sep 12, 2011, at 5:39 PM, Akib Sayyed wrote:
> Guys i want step by step guide for installing and running mediaproxy.
> i followed
> http://voiprookie.blogspot.com/2009/04/blog-post.html instructions but i
> received following error
>
>
yah but even if radius gives error mediaproxy should work
On Mon, Sep 12, 2011 at 9:23 PM, Brett Nemeroff wrote:
>
>
> On Mon, Sep 12, 2011 at 10:39 AM, Akib Sayyed wrote:
>
>> Guys i want step by step guide for installing and running mediaproxy.
>> i followed
>> http://voiprookie.blogspot.com/2
On Mon, Sep 12, 2011 at 9:15 AM, Luis Alfredo Morales Lora <
luisalfredo_m...@hotmail.com> wrote:
> I'm using version 3.1 and I've also tried version 3.2 and I have the same
> problem in both. I used the -trace_err to see what the errors where, and the
> problem is that while Sipp is expecting a p
On Mon, Sep 12, 2011 at 10:39 AM, Akib Sayyed wrote:
> Guys i want step by step guide for installing and running mediaproxy.
> i followed
> http://voiprookie.blogspot.com/2009/04/blog-post.html instructions but i
> received following error
>
>
>
These are RADIUS errors. Check your radius configur
Guys i want step by step guide for installing and running mediaproxy.
i followed
http://voiprookie.blogspot.com/2009/04/blog-post.html instructions but i
received following error
Sep 12 21:06:03 localhost /usr/local/sbin/opensips[15062]: rc_ip_hostname:
couldn't look up host by addr: 73FCBDE7
Sep
Hello,
Thanks for your responses Flavio and Brett,
I'm using version 3.1 and I've also tried version 3.2 and I have the same
problem in both. I used the -trace_err to see what the errors where, and the
problem is that while Sipp is expecting a particular response, it receives
another, for exam
Check if Avaya has support for SIP Path extension:
http://www.opensips.org/html/docs/modules/1.7.x/path.html
This would be the clean solution.
Alternative solution: replace the IP in Contact header of REGISTER and
mirror the registration on opensips.
This should trick Avaya to think that opensips
Basically what I ask is what methods can i use to force PhoneA to go to
opensips because it is a h.323 phone and there is no way to specify sip
proxy in it or it's only one solution here - b2bua?
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/opensips-rtppr
Append a header in OpenSIPS with the source IP and check it in Asterisk.
Adrian
On Sep 11, 2011, at 4:30 AM, Robert Thomas wrote:
> Hello List,
>
> This question I think it's more related to SIP in general, or OpenSIPS -
> Asterisk implementation that just opensips. However I highly value the
On Sep 11, 2011, at 11:10 PM, Anto wrote:
> Hello
>
> I have a problem with callControl and before I started researching the
> code (rather try to do it :-P), I wanted to ask if you can do easily
> by routing by OpenSIPS or cdrtool settings.
>
> I explain my scenario, I have several department
19 matches
Mail list logo