9 Jan
2008
9 Jan
'08
6:24 p.m.
On Wednesday 09 January 2008, TCB wrote:
Thanks Henning , i have just realised i had not set
the prob,
now the routing works but i'm afraid i have created another
problem. For some reason the ip address is being prefixed to the
called number.
See below.
Jan 9 14:56:02 ss-za /usr/sbin/openser[20127]:
INFO:carrierroute:get_route_tree_by_id: searching in carrier default
Jan 9 14:56:02 ss-za /usr/sbin/openser[20127]:
DBG:carrierroute:get_route_tree_by_id: tree default, domain 0 : 0
Jan 9 14:56:02 ss-za /usr/sbin/openser[20127]: DBG:core:hash_func: hash:
2298 % 1000 = 298
Jan 9 14:56:02 ss-za /usr/sbin/openser[20127]:
INFO:carrierroute:carrier_rewrite_msg: uri 0727785841 was rewritten to sip:
196.15.164.13727785841(a)196.15.164.13
My carrierroute table looks like this:
id | carrier | scan_prefix | domain | prob | strip | rewrite_host | rewrite_prefix |
rewrite_suffix
----+---------+-------------+--------+------+-------+---------------+----------------+----------------
2 | 0 | 072 | 0 | 1 | 1 | 19.1.164.13 | 27 |
1 | 0 | 011 | 0 | 1 | 1 | 19.1.164.13 | 27 |
Hi,
your table is correct. I've seens this before, there was some user who copied
the content of rewrite_host into rewrite_prefix, i think. Could you check if the
RAM-cache on the module has also the correct data? (with 'openserctl fifo
cr_dump_routes')
Do you do other RURI rewriting before the route[22] where the cr method is called?
Cheers,
Henning