Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties


Target release6.15.0
Epic

Jira Legacy
serverDialogic JIRA
serverId8f70d0a4-20da-363f-81e2-5b2706a93a6a
keyBRKT-1212

FR

Jira Legacy
serverDialogic JIRA
serverId8f70d0a4-20da-363f-81e2-5b2706a93a6a
keyBRKT-45

Document status

Status
colourYellow
titleDraft

Document owner


...

Solution: Allow the setting of an IP address that will be used to modify the SIP headers, such as From and Contact, as well as the SDP headers defining the RTP connection information to the external IP of the EC2 instance.

The SR140 needs to be aware of the NAT device's public IP address.  This public IP address will be used in place of the private IP address.  This setting can be a single value for the whole system assigned when SR140 starts (in configuration file).

Assumptions


Requirements

#TitleUser StoryImportanceNotes
1




...

QuestionOutcome
  1. Will the external IP address be the same for SIP and RTP?

2. Who will obtaining the public IP address? Is it the responsibility of
the customer or is the SR140 required to figure out what external IP
of the system is?

3. If there is a new keyword for the public IP address in the callctrl.cfg file, will this keyword take
precendence over the other keywords such as sip_Contact, sip_ip_interface and sip_From?

4. What about the Request URI and the To: header fields? Will these use the public IP address? I actually think that these should use the IP address of the remote side which is receiving the fax.

5. Support for both IPv4 and IPv6 or just IPv4?


https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html


http://bot.whatismyipaddress.com/

http://ipinfo.io/ip


...