Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - AlasdairL

Pages: [1]
1
MiVoice Office 250/Mitel 5000 / Re: Mitel 5000 Inbound SIP Issue
« on: February 26, 2015, 09:10:47 AM »
I've got a NAT policy ensuring that all outbound SIP 5060 traffic to the Voiceflex server is presented as a set IP address. This IP address is set as the NAT IP address on the Mitel.
There is a NAT policy ensuring that all inbound SIP 5060 traffic from the Voiceflex server is directed to the Mitel's internal address.

There is a firewall rule to allow SIP 5060 traffic from Voiceflex going to the Mitel.

So think that should cover the port forwarding aspect.
Packet filter suggests that there is traffic coming from Voiceflex to the Mitel on port 5060 in response to an outbound message. this traffic tends to be SIP/2.0 404 Not Found messages.
Just not getting any data relating to inbound calls.

From what I can see in the logs, it suggests that the system is not registering with Voiceflex.
but can't figure out why.

2
MiVoice Office 250/Mitel 5000 / Re: Mitel 5000 Inbound SIP Issue
« on: February 24, 2015, 04:00:37 PM »
The System NAT address was set but i've now set the Processor Module address as well.

And thanks for pointing me in the direction of the logging options.
from looking at packet capture and the logs, the one thing i see a lot of is SIP/2.0 404 Not Found messages alongside <username>@<nat_Ip_address> to <Voiceflex IP address>.
This same is true if i enable SIP Transformations on the sonicwall.

3
MiVoice Office 250/Mitel 5000 / Re: Mitel 5000 Inbound SIP Issue
« on: February 24, 2015, 08:43:52 AM »
SIP Trunk Group Configuration is set with the same CRT for Day and Night.
This is a fresh CRT that i don't use elsewhere and is set to route based on inbound number pattern with +44 prefix, with 0 prefix and without either as i wasn't 100% sure which one was required.

NAT is currently set to Non-SIP-Aware and SIP transforms are disabled on the Sonicwall.
Although I'm pretty sure I've tried all the different combination of NAT and SIP Transform settings.

4
MiVoice Office 250/Mitel 5000 / Mitel 5000 Inbound SIP Issue
« on: February 24, 2015, 06:26:34 AM »
Hoping someone might be able to assist with an issue I'm currently having on a Mitel 5000 system.

I've recently setup SIP trunks provided by VoiceFlex.
Now while I can make outbound calls, attempt at inbound just result in an engaged tone.

It's probably going to end up being something straight forward but it's driving me nuts trying to figure it out.

At the moment it is 2 trunks with one number which I have entered into call routing table along with the catch all.
Firewall is a Sonicwall NSA 2400 and at the moment I've setup inbound and outbound NAT rules for the Mitel when communicating with Voiceflex.

Any suggestions on what might be causing this would be appreciated.

Thanks


5
MiVoice Office 250/Mitel 5000 / Re: External Fowarding
« on: April 03, 2014, 11:58:01 AM »
Hi TE,

yeah we don't currently have MoH setup.
It is something we are looking at but wanted to make sure this problem wouldn't exist even with MoH

The settings you mention are currently set as
Audio for Calls Camped onto this Device - Tick Tone
Music-On-Hold - Tick Tone
Audio on Transfer to Ring - Ringback
Audio on Transfer to Hold - Music-On-Hold
Audio on Hold for Transfer Announcement - Music-On-Hold

If one of those settings can be changed just now to give us a ring tone at the required moment, let me know and i'll give it a try.

Thanks

6
MiVoice Office 250/Mitel 5000 / External Fowarding
« on: April 03, 2014, 09:43:40 AM »
Looking for a bit of advice on whether I can improve part of our 5200 configuration or not.

Calls to our main office number ring a hunt group for our reception staff.
Any calls not answered are forwarded to an external call centre who act our behalf and take a message or forward the call to the correct direct dial.

The hunt group consists of an extension list and is set to recall to a phantom device after 15 seconds.
Phantom device is set to forward calls to the call centre.

The process all works correctly but we've had comments that its not very seamless.
The problem we have is that for inbound callers being forwarded, there is a period of silence after the hunt group recalls while the ISDN is connected before it starts ringing the call centre.
This seems to be about 8 seconds

Is there any way we can mask this silence? with ring tone or message on hold for instance?
or an alternative way of setting up the forwarding rules?
Ideally we would have it ring the hunt group right up until the point the forwarding is connected to the call centre.


any suggestions would be much appreciated.

Thanks

Pages: [1]