Hi All
I was able to setup carrierroute in database mode and when I make a call
with prefix 00 it works fine. For that I did setup an entry in
carrierroute, I did duplicate that same entry for prefix "+".
If I call 004353453 it works fine however if I dial +12341234 I get a
403 forbidden error. The log shows:
Jan 23 14:22:34 [25866] DBG:carrierroute:get_route_tree_by_id: tree
default, domain 0 : 0
Jan 23 14:22:34 [25866] INFO:carrierroute:rewrite_uri_recursor: URI or
route tree nodes empty, empty flag list
Jan 23 14:22:34 [25866] INFO:carrierroute:cr_do_route:
rewrite_uri_recursor doesn't complete, uri +9613041705, carrier 5,
domain 0
Any guidance please ?
With Regards
Hi
Using kamailio v1.5 (trunk), I'm testing the following simple presence
scenario where one user shutdowns his application without prior un-PUBLISH
and un-REGISTER.
1) user A subscribes to user B presence. Both use X-Lite.
2) user B shutdowns his X-Lite (without doing un-REGISTER and un-PUBLISH of
his presence information),
3) user B starts again X-Lite, registers and publishes his presence,
from that point when user B updates his presence information, user A does
not see the updates !
I've configured kamailio to use
save("location", "0x04")
instead of
save("location")
for incoming REGISTER but this does not help.
Is there a way to clean presence DB tables properly when user B register
again ?
Regards,
Pascal
Hi All
I was finally able to setup carrierroute on Solaris :). I am using
carrierroute in db mode and I did setup two entries with rewritehost in
carrierroute and two entries in route_tree with one route being default.
I am still very new to carrierroute as a sample start I do have two
astersisk servers that will act as pstn_gw and I want to split the
traffic in half between both servers.
Can anyone please provide sample instructions on what to put into the
route{} statement in this scenario and any main ideas about route_tree
and carrierroute ?
Thanks.
Hi Ramona, I have installed Siremis, but I get the following error:
Unable to write in the session save path [/home/www/siremis/siremis/session]
Fatal error: Call to a member function GetSessionContext() on a non-object
in /home/www/siremis/openbiz/bin/BizSystem.php on line 9
Do you have any suggestions about how to fix this?
Thanks in advance,
Juan.-
Hi,
I'd like to know if there is a way to retrieve the information from the
carrierroute module in AVPs.
Example:
- a prefix has matched, and I'd like to get the field "description"
associated with this route and add it in the SIP header
- a prefix has matched, and I'd like to get the field
"rewrite_host" associated with this route and use it with xlog
Thanks,
rod.
htable module README has a dictionary attack limitation example. i'm
afraid to "try it at home", because it seems to me that it in turn opens
up a dos attack possibility: exhausting proxy shared memory by
generating requests with random $au values.
in order to avoid that, the script should include check if $au exists
before adding it to dictionary. on am i missing something?
-- juha
I need some hints as to what can be going on;
Running: openser-1.2.2-tls
Mobile 1 à PSTN à Provider SER à Local SER à Asterisk (Callforward) à Provider SER à PSTN à Mobile 2
When Mobile 2 hangs up, Mobile 1 does not get disconnected but hangs with dead air.
Provider SER: Is load balanced using standards DNS round robin with one CNAME pointing to two IP's
Our BYE goes to the wrong IP even though we use;
modparam( "rr", "enable_full_lr", 1 )
...
fix_nated_contact();
force_rport();
if ( ! search( "^Content-Length:\ 0" ) ) {
fix_nated_sdp( "3" );
};
t_on_reply( "1" );
record_route();
if ( loose_route() ) {
route( 1 );
break;
};
I have tested with check_via = yes to no avail.
Do any of you have any idea what might be causing this?
I know the provided information is sparse but thought I'd try the short descriptions of the problem first, if it's a known miss config.
Many Regards
Danny Froberg
Hi,
I have a SIP phone setup behind a router. When I placed a call from this
phone, I got this error from OpenSER when the INVITE message was received.
Jan 21 13:57:44 prod-ipser-10 /usr/sbin/openser[2100]:
ERROR:nathelper:extract_body: message body has length zero
Jan 21 13:57:44 prod-ipser-10 /usr/sbin/openser[2100]:
ERROR:nathelper:fix_nated_sdp_f: cannot extract body from msg!
Jan 21 13:57:45 prod-ipser-10 /usr/sbin/openser[2097]:
ERROR:nathelper:extract_body: message body has length zero
Jan 21 13:57:45 prod-ipser-10 /usr/sbin/openser[2097]:
ERROR:nathelper:fix_nated_sdp_f: cannot extract body fr
Any ideas?
Lee
Victor Pascual Ávila wrote:
> On Wed, Jan 21, 2009 at 5:45 PM, Iñaki Baz Castillo <ibc(a)aliax.net> wrote:
>
>> 2009/1/21 Elena-Ramona Modroiu <ramona(a)asipto.com>:
>>
>>> For few days, a demo site can be accessed at:
>>> - http://siremis.asipto.com/demo/
>>> - username: admin and password: admin
>>>
>> Guau! really great!
>>
>>
>
> Great work. Thanks!
>
Thanks for your appreciations!
Regards,
Ramona
Hello,
trunk has a new transformation class: tobody
The name comes from To header Body and provides access to fields inside
strings that follow the grammar of a To header - such headers are From,
P-Asserted-Identity, ....
Real benefit of using this transformation is that it copes with strings
that can have values either simple URIs or NameAddr.
The format of transformation is {tobody.param}, where param can be:
- display - return display name
- uri - return uri
- user - return username from uri
- host - return hostname from uri
- tag - return the value of tag parameter
Documentation is available at:
http://www.kamailio.org/dokuwiki/doku.php/transformations:devel#to-body_tra…
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com