Twilio Integration with Genesys

[cavagnaro]

You need to go back to the basics of SIP.
SBC or similar software/hardware is needed to be able to change the destination address...your private IP is obviously not reachable by Twilio or any SIP equipment, therefore you need something to modify headers.
All solutions here refer to a SBC or similar being used


If you are using WDE as Endpoint then you can use this maybe:
https://docs.genesys.com/Documentation/SESDK/9.0.0NET/Developer/DefaultConfigSettings#public_address


But if you are sending calls to MCP then no way as far as I know as it needs to advertise the local IP for connection settings

[KRS]

That's what I had figured, and why I was surprised to read that the previous posters were able to get the trunk working directly with SIP Server (IE no SBC).

Their configurations would be extremely helpful in understanding. Thanks for the responses.

[jamesmurphyau]

I was the one that said I got it working and unfortunately I couldn't find any details about how I managed to do it and this was a while ago

In regards to private IP in contact header, you resolve this by using DNS. Regarding private IP in SDP, you can use DNS here too for WDE but last I tried MCP did not allow this. For MCP you can specify a different (public) IP in the SDP with a setting.. this would only work for calls that access MCP from outside your network and becomes difficult when you have more than 1 MCP.

What I've also seen done is configuring the public IP as an IP on the machines that run the software - but this seems overkill and with DNS solving lots of the problems around internal/external contact, via, etc headers you just need to do that.. ensure the dns record resolves to internal IP for your internal DNS, and public IP for public facing DNS

[cavagnaro]

  Sorry but a DNS management can't fix the IP Address sent at the via IP parameter in SDP...would be so easy if so and there would be no need for SBCs or Firewalls doing NAT alteration

[jamesmurphyau]

You can specify FQDN in the SDP using MCP options and now thinking about it I'm not 100% sure if it was WDE or if t was MCP that supported it, but at the time one of the components did support it and one did not.

But like I said you can force MCP to send a different IP (ie the public IP) using an option.. Actually you can set it to FQDN or a public IP using the same option - mpc/sdp.connection

https://docs.genesys.com/Documentation/Options/Current/GVP/GVP_MCP-mpc#sdp-connection ..

MCP Options:
[code]mpc/sdp.connection = IN IP4 110.12.13.14
sip/transport.localaddress = mcp-01.company.com[/code]

And obviously ensure that SIP Server only uses FQDN everywhere..

The only place that needs to be an actual IP in the SIP messages is SDP but even in that case the RFC does allow for FQDN so devices should support it (but lots don't - I always like to try when connecting to something new)

[code]; sub-rules of 'c='
connection-address =  multicast-address / unicast-address

; generic sub-rules: addressing
unicast-address = IP4-address / IP6-address / FQDN / extn-addr
...
FQDN = 4*(alpha-numeric / "-" / ".")
; fully qualified domain name as specified
; in RFC 1035 (and updates)[/code]