Author |
Message |
Björn Brekeke Newbie
Joined: 14 Feb 2008 Posts: 3
|
Posted: Thu Feb 14, 2008 7:19 am Post subject: Modify SIP uri |
|
|
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/networkpatterns.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 |
|
Back to top |
|
james Brekeke Master Guru
Joined: 10 Dec 2007 Posts: 494
|
Posted: Thu Feb 14, 2008 12:13 pm Post subject: |
|
|
Hi
Did you try "Upper Registration "? |
|
Back to top |
|
Björn Brekeke Newbie
Joined: 14 Feb 2008 Posts: 3
|
Posted: Thu Feb 14, 2008 11:03 pm Post subject: |
|
|
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 |
|
Back to top |
|
james Brekeke Master Guru
Joined: 10 Dec 2007 Posts: 494
|
Posted: Tue Feb 19, 2008 11:27 am Post subject: |
|
|
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. |
|
Back to top |
|
Björn Brekeke Newbie
Joined: 14 Feb 2008 Posts: 3
|
Posted: Thu Mar 06, 2008 12:51 am Post subject: |
|
|
Ok, thanks!
I actually solved my issue with your first suggestion, upper registration. By using it in the deploy pattern and catching the url from the matching pattern (the from paramter which was actually correct).
&net.registrar.upper.allow=true
&net.registrar.upper.url=%2 |
|
Back to top |
|
james Brekeke Master Guru
Joined: 10 Dec 2007 Posts: 494
|
Posted: Tue Mar 11, 2008 10:34 am Post subject: |
|
|
Wow, Nice. |
|
Back to top |
|
|