[SR-Users] Kamailio as SBC and far end nat

Martin Schiøtz malinux at gmail.com
Thu Jul 19 13:12:02 CEST 2012


Hi

I'm trying to configure kamailio version 3.3.0 to be a Session Border
Controller which only purpose is to handle far-end-nat.

On the far end site I have a SIP client with IP '192.168.1.2' which is
NAT'ed to IP 'zz.zz.85.230'. The SIP ALG is disabled on the NAT
firewall. The SIP client is communicating with the kamailio server and
the Kamailio server is forwarding every thing to an Avaya SIP server
'xx.xx.173.15' and vice versa. The kamilio is konfigured to do this
stateless.

The REGISTER and SUBSCRIBE part works fine. The kamailio is using the
'Via:' field and I also needed to do subst on the 'Contact:' field in
order for our SIP server to communicate back to the kamailio. But when
I get to the NOTIFY packet from the SIP server to the kamailio there
is no 'Via:' field or any other information about the SIP clients
IP/port and the Kamailio just sends back 'SIP/2.0 404 Not here.' to
the SIP server.

I guess that this can not be solved with a statless kamailio?
I guess that I need some kind of state table in the kamailio - is that
possible without doing REGISTER directly with the kamailio?
Any other good ideas are welcome?

Cheers,
Martin


Tell me if need more info the issue?
-----
#
T xx.xx.173.15:38059 -> yy.yy.159.211:5060 [AP]
NOTIFY sip:2001012 at yy.yy.159.211:5060;transport=TCP SIP/2.0.
Call-ID: NjQ5ZDNlYzRjOWFjMzMzN2JlYzAwMTg4ODYwZTJlYWY..
From: "2001012"
<sip:2001012 at bsosip.domain.dk>;tag=-667195155*1*016asm-callprocessing.sar229435981~1342570131099~1170998434~1.
To: "2001012" <sip:2001012 at bsosip.domain.dk>;tag=7ca0af7d.
CSeq: 3 NOTIFY.
Contact: <sip:xx.xx.173.14:15060>.
Via: SIP/2.0/TCP
xx.xx.173.15;branch=z9hG4bK4DEAAD0E478B838008189457-AP;ft=xx.xx.173.15~13c4.
Via: SIP/2.0/UDP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838008189457.
Via: SIP/2.0/TCP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838018189455.
Event: message-summary.
Content-Type: application/simple-message-summary.
Content-Length: 69.
Subscription-State: active;expires=299.
Max-Forwards: 68.
User-Agent:  AVAYA-SM-6.1.4.0.614005.
.
Messages-Waiting: no.
Message-Account: sip:2001012 at bsosip.domain.dk.

##
T yy.yy.159.211:5060 -> xx.xx.173.15:38059 [AP]
SIP/2.0 404 Not here.
Call-ID: NjQ5ZDNlYzRjOWFjMzMzN2JlYzAwMTg4ODYwZTJlYWY..
From: "2001012"
<sip:2001012 at bsosip.domain.dk>;tag=-667195155*1*016asm-callprocessing.sar229435981~1342570131099~1170998434~1.
To: "2001012" <sip:2001012 at bsosip.domain.dk>;tag=7ca0af7d.
CSeq: 3 NOTIFY.
Via: SIP/2.0/TCP
xx.xx.173.15;branch=z9hG4bK4DEAAD0E478B838008189457-AP;ft=xx.xx.173.15~13c4;rport=38059.
Via: SIP/2.0/UDP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838008189457.
Via: SIP/2.0/TCP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838018189455.
Server: kamailio (3.3.0 (i386/linux)).
Content-Length: 0.
.

#
T xx.xx.173.15:38059 -> yy.yy.159.211:5060 [A]
......
#
T yy.yy.159.211:5060 -> xx.xx.173.15:38059 [AP]
SIP/2.0 404 Not here.
Call-ID: NjQ5ZDNlYzRjOWFjMzMzN2JlYzAwMTg4ODYwZTJlYWY..
From: "2001012"
<sip:2001012 at bsosip.domain.dk>;tag=-667195155*1*016asm-callprocessing.sar229435981~1342570131099~1170998434~1.
To: "2001012" <sip:2001012 at bsosip.domain.dk>;tag=7ca0af7d.
CSeq: 3 NOTIFY.
Via: SIP/2.0/TCP
xx.xx.173.15;rport=38059;branch=z9hG4bK4DEAAD0E478B838008189457-AP;ft=xx.xx.173.15~13c4.
Via: SIP/2.0/UDP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838008189457.
Via: SIP/2.0/TCP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838018189455.
Server: kamailio (3.3.0 (i386/linux)).
Content-Length: 0.
-----



More information about the sr-users mailing list