1. Brekeke Product Name and version:
SIP Server 2.0
2. Java version:
1.6
3. OS type and the version:
Windows 2003
4. UA (phone), gateway or other hardware/software involved:
Asterisk PBX
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :
6. Your problem:
Is it possible to change the SIP Uri in a register signal before the register signal is routed by the brekeke server.
I want to change REGISTER onedomain.domain.com:5065 SIP/2.0 to REGISTER anotherdomain.domain.com SIP/2.0.
And I want the brekeke to route the signal based on the last sip uri. Is this possible
Thanks,
Björn
Modify SIP uri
Moderator: Brekeke Support Team
Hi,
thanks for the reply.
Yes, I have tried the upper registration function. It let me set the request uri to another domain, but it also changes the to and from fields in the sip header. I want the to and from field to be unmodified. So the upper registration function doesn't seem to work for me.
I have found a matching pattern for the request uri, $request, but it doesn't seem to work for deploy pattern. Any ideas?
My matching/deploy pattern:
$request=^REGISTER/$request=sip:host.domain.com
thanks for the reply.
Yes, I have tried the upper registration function. It let me set the request uri to another domain, but it also changes the to and from fields in the sip header. I want the to and from field to be unmodified. So the upper registration function doesn't seem to work for me.
I have found a matching pattern for the request uri, $request, but it doesn't seem to work for deploy pattern. Any ideas?
My matching/deploy pattern:
$request=^REGISTER/$request=sip:host.domain.com
Hi Björn!
I found it in the Version History.
http://www.brekeke.com/download/readme_bss.txt
> 2.1.1.3 (July 31, 2007)
> - The Deploy Pattern can set $request as the new request line
So you need to use a newer version after ver2.1.1.3.
I found it in the Version History.
http://www.brekeke.com/download/readme_bss.txt
> 2.1.1.3 (July 31, 2007)
> - The Deploy Pattern can set $request as the new request line
So you need to use a newer version after ver2.1.1.3.