hmmm... another workaround then might be to use a Patton gateway as the
go-between. Josh did some work recently around using the Patton as a
termination point for SIP trunks. I think the config is in the Wiki.
Mike
On Fri, Jun 15, 2012 at 3:04 PM, Matt White wrote:
> >>> Michael Picher 06/15
>>> Michael Picher 06/15/12 2:01 PM >>>
>did you try just setting the seimens up as an unmanaged gateway?>
>why do you need it to be a trunk? then you're anchoring media...
Yeah, we are trying to get around a limitation of the Seimens. The HiPath sip
card only has a single "sip channel" as it
did you try just setting the seimens up as an unmanaged gateway?
why do you need it to be a trunk? then you're anchoring media...
On Fri, Jun 15, 2012 at 1:48 PM, Matt White wrote:
>
>
> >>> Gerald Drouillard 06/15/12 1:16 PM >>>
>
> >
> >So the IP address of the SeimensPBX is found in local s
>>> Gerald Drouillard 06/15/12 1:16 PM >>>
>
>So the IP address of the SeimensPBX is found in local subnets? Do
>you have the Siemens setup as a gateway? Send server profile and
>reboot sipx?
Yup, the ip of the seimenspbx is in included in the defined local subnets.
I'
On 6/15/2012 12:22 PM, Matt White wrote:
As I stare at my traces I'm seeing an issue with sipxbridge via headers.
The PBX is behind a NAT and has it configured. Calls to the SIP trunk
for external calls are fine.
The gateway that is configured between the PBX and the SeimensPBX are
not sepa
As I stare at my traces I'm seeing an issue with sipxbridge via headers.
The PBX is behind a NAT and has it configured. Calls to the SIP trunk for
external calls are fine.
The gateway that is configured between the PBX and the SeimensPBX are not
separated by nat. The IP address is separated b
Anyone want to take a look at debug file and give me some thoughts?
Here is what I have. Its bit complicated.
Seimens PBX is trunked to PBX1. The seimens sends calls to sipxbridge (5080)
on PBX1. No nats anywhere
PBX1 uses a TLS trunk (5081) to PBX2.
The TLS trunk between PBX1 and PBX2 wor
