Hi Sven,
many thanks for you answer.
In all our previous deploy with a miniedge, we've used a WAN interface to communicate with external trunk (in the same lan of edge) and with PureCloud and WebRTC trunk, and all works fine.
Now, the question is simply that:
with mini edge, could we use the LAN interface to connect the external trunk (in the customer LAN) and WAN to connect to WebRTC trunk? as per documentation, no gateway it's configured in LAN, because the online docs says that the gateway need to be configured only in WAN; LAN interface need static route to works correctly, non gateway.
But with this configuration, we saw that External trunk goes green in LAN and WebRTC goes grey in WAN; in we configure External Trunk and WebRTC in WAN both have green color.
What could be the error?
Many thanks, Alessandro
------------------------------
Alessandro Boni
ComApp S.r.l
------------------------------
Original Message:
Sent: 02-10-2020 14:20
From: Sven Schiller
Subject: Mini Edge with LAN/WAN cabled
The LAN side would typically be used for trunks available on the LAN, such as a provider gateway with SIP channels (I think this would be your Cisco gateway), or phones in the corporate network. If you don't have a trunk on the WAN side, why do you care if it is up? As long as you can see the edge in the admin interface.
I don't think you have to have a trunk on the WAN side.
Make sure your static routes are setup correctly, and your trunk allows the Cisco to talk to it (check the access list). The edge should show the trunk as operational.
------------------------------
Sven Schiller
Kognitiv
Original Message:
Sent: 02-07-2020 02:55
From: Alessandro Boni
Subject: Mini Edge with LAN/WAN cabled
Hi all,
we're configuring a MiniEdge with two different interface, LAN for External Trunk to Cisco using private address (no gateway configured, only static route as per documentation), and WAN for Cloud comunication; the WAN has a Gateway.
The strange situation we're encountering is this: at EDGE startup, only the external Trunk goes up, the WAN remain grey but is cabled; if we enable the WAN from Edge, and disable/enable LAN, the WAN goes up and LAN goes down. IP interface are separated, so we think there are not network congestion,
After we enable protocol and media capture in WAN/LAN, we see traffic, but if we made a call from Cisco to Edge, we saw an:
"404 Not available trunk found"
There are any particular configuration in case we use LAN for internal traffic (i.e. to Cisco Voice Gatewa) and WAN for Cloud?
Firewall is opened any from WAN to external, so we think at someone on edge configuration....
LAN and WAN are on separate network, but in Edge device the LAN must have the route to WAN and viceversa for your knowledge?
Any help would be appreciated
BR Alessandro
#Implementation
------------------------------
Alessandro Boni
ComApp S.r.l
------------------------------