Hello, I am using OXE v11.
Recently I needed to use SIP trunk to connect to ISDN.
SIP provider gave me the SBC IP address - Default Gateway - Subnet Mask and my own IP address.
I asked the network administrator to create the NAT settings so that he could convert the IP address of CS2 to the address defined by SIP provider. These things were done and I also configured SIP trunk. Finally, when I tried to connect to ISDN, the phone ringing but after picking up the phone, no sound was transmitted. I asked the SIP provider why this happend. After checking the SIP packets, he told me that he sees the IP address of CS2 as the source device, not the address defined in the NAT. The network administrator also says that we have transferred the addresses correctly and that this is your problem. Now I want to know Is it possible to specify another address ( in a different range than the CS2 address) for the SIP trunk source? Or is there another solution (other than using a peripheral device) for me?
sip trunk by using NAT
Re: sip trunk by using NAT
hi
tel you admin that Nat is not sip friendly and he should take care of the sip packet
if signaling exchange is ok , media is not necessary following and could be KO why CUZE media information's are exchanged in the sdp wich your nat could not be aware about it , also your Firewall is not opening the good port by sip inspection rules .
BTW it's note recommended to expose directly your OXE to the WAN except if you are seeking troubles X-D
3 SOLUTIONS :
Use SBC it's the best practice and mandatory for normalisation, interworking and security purpose especially when your'e on internet
Use sip profile Manipulation (aka normalisation) this must be done under the router who has voice applications capabilities like Cisco ios -can be done by sbc-, sometimes a loopback interface created in the router can handle the issue
Firewall / NAT Configurations
The sbc must have a Public IP for interconnecting. There are multiple ways to get Public IP to PRIVATE , either directly assign Public IP in one of the SBCinterfaces or configure NAT, so that it can translate Private IP of sbc to Public IP. For Enterprise deployments, have meeting with your network and firewall team to get this completed. In your case, you do have a Public IP and you will be doing the NAT. This will make sure any SIP, HTTP, RTP Traffic to your public IP will be forwarded to Private IP of sbc
tel you admin that Nat is not sip friendly and he should take care of the sip packet
if signaling exchange is ok , media is not necessary following and could be KO why CUZE media information's are exchanged in the sdp wich your nat could not be aware about it , also your Firewall is not opening the good port by sip inspection rules .
BTW it's note recommended to expose directly your OXE to the WAN except if you are seeking troubles X-D
3 SOLUTIONS :
Use SBC it's the best practice and mandatory for normalisation, interworking and security purpose especially when your'e on internet
Use sip profile Manipulation (aka normalisation) this must be done under the router who has voice applications capabilities like Cisco ios -can be done by sbc-, sometimes a loopback interface created in the router can handle the issue
Firewall / NAT Configurations
The sbc must have a Public IP for interconnecting. There are multiple ways to get Public IP to PRIVATE , either directly assign Public IP in one of the SBCinterfaces or configure NAT, so that it can translate Private IP of sbc to Public IP. For Enterprise deployments, have meeting with your network and firewall team to get this completed. In your case, you do have a Public IP and you will be doing the NAT. This will make sure any SIP, HTTP, RTP Traffic to your public IP will be forwarded to Private IP of sbc
