Trying to figure out the config needed for the following setup:
I've Asterisk server A, being decommissioned in the US, and replaced by Asterisk server B, in the UK.
Whilst the decom takes place over a few weeks/months, I need to redirect any inbound SIP Registrations it receives over to server B.
Both servers have 1 public IP addresses on their NIC. One NIC each.
So far, I've got config that looks like:
if_inbound = eth0
if_outbound = eth0 (single nic)
sip_listen_port = 5061 (5061 just for testing, will be 5060 when it replaces Asterisk)
rtp_proxy_enable = 1 (not sure if I actually need to do this or not yet)
proxy_auth_realm = Authentication_Realm
proxy_auth_passwd = ****** (all our clients will use the same password)
First thing to mention - you try to use siproxd for some purpose that it was not designed to do. Siproxd does provide a way to overcome the "NAT issue" with SIP devices.
Maybe in your case a simple port redirection from serverA:5060 -> serverB:5060 might be sufficient?
Second - the mentioned error "sip_message_parse() failed... this is not good" originates in libosip2 which fails trying to parse the SIP message. This usually happens if the SIP message contains broken headers or maybe a bug in libosip2 - but I don't think so).
Regards,
/Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually I'm not trying to do any NATing at all. Both Servers are on the public internet. It is actually the clients that are likely to be on a private LAN. I am seeing in the logs, that siproxy is referencing the internal LAN IPs of the clients (which in turn I find odd as I believed our corporate firewall, a Speedtouch 608WL, performs SIP header alterations for NATing). I might try tomorrow with a public internet IP directly on a client to see what happens then.
The port redirection idea was our first call (iptables), but for some reason we just cant get IPtables to work outside of a local LAN lab environment doing this. We havent given up on this method yet, but were hoping that having a simple software proxy act as a go-between would work.
Yes I was wondering about that message. I've tried several SIP devices, all which "speak" to asterisk 1.4.15 fine.
I'm also looking at servers like OpenSIPs, but they seem much over-powered for my needs (and complicated to set up)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi All,
Trying to figure out the config needed for the following setup:
I've Asterisk server A, being decommissioned in the US, and replaced by Asterisk server B, in the UK.
Whilst the decom takes place over a few weeks/months, I need to redirect any inbound SIP Registrations it receives over to server B.
Both servers have 1 public IP addresses on their NIC. One NIC each.
So far, I've got config that looks like:
if_inbound = eth0
if_outbound = eth0 (single nic)
sip_listen_port = 5061 (5061 just for testing, will be 5060 when it replaces Asterisk)
rtp_proxy_enable = 1 (not sure if I actually need to do this or not yet)
proxy_auth_realm = Authentication_Realm
proxy_auth_passwd = ****** (all our clients will use the same password)
outbound_proxy_host = serverB.mycompany.com
outbound_proxy_port = 5060
Everything else is default. Does this config look right for what I need to do ??
I'm looking at the debug, as no registration appears on server B.
Sorry forgot to add: I changed Authentication_Realm to my serverA domainname
I keep getting a basic error:
:07:26 ERROR:siproxd.c:420 sip_message_parse() failed... this is not good
Hi,
First thing to mention - you try to use siproxd for some purpose that it was not designed to do. Siproxd does provide a way to overcome the "NAT issue" with SIP devices.
Maybe in your case a simple port redirection from serverA:5060 -> serverB:5060 might be sufficient?
Second - the mentioned error "sip_message_parse() failed... this is not good" originates in libosip2 which fails trying to parse the SIP message. This usually happens if the SIP message contains broken headers or maybe a bug in libosip2 - but I don't think so).
Regards,
/Thomas
Hi Thomas,
First, thanks for the reply.
Actually I'm not trying to do any NATing at all. Both Servers are on the public internet. It is actually the clients that are likely to be on a private LAN. I am seeing in the logs, that siproxy is referencing the internal LAN IPs of the clients (which in turn I find odd as I believed our corporate firewall, a Speedtouch 608WL, performs SIP header alterations for NATing). I might try tomorrow with a public internet IP directly on a client to see what happens then.
The port redirection idea was our first call (iptables), but for some reason we just cant get IPtables to work outside of a local LAN lab environment doing this. We havent given up on this method yet, but were hoping that having a simple software proxy act as a go-between would work.
Yes I was wondering about that message. I've tried several SIP devices, all which "speak" to asterisk 1.4.15 fine.
I'm also looking at servers like OpenSIPs, but they seem much over-powered for my needs (and complicated to set up)