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 - saturated

Pages: [1]
1
It works as expected. I ended up also trying a polycom SIP phone and the same issue exists.

2
I am running 6.0.11. On the grandstream phones I set the call timeout to 3 minutes (system forward is set to 15 seconds) to make sure it was not the phone dropping the call.

3
So, I found a temporary workaround:

If I create a hunt group with the SIP phone extension
create a system forward path to the SIP hunt group in slot 1 and then VM in slot 2
set the phone forwarding path to immediate and to the new system forward path

node to node calls work as expected and forward to VM after ringing.

Does give anyone a clue as to why it's not working without this extra setup?

4
unfortunately, yes.

5
Hello,

We are trying to integrate SIP phones (Grandstream GXP2140) to our Mitel 5000/250.

Node A: local node where the SIP phones exist
Node B: remote node

Everything works as expected when calling from any device type internally on node A.
When node B calls a SIP phone on node A, the phone will ring but not use the VM forwarding path unless it is set to immediate.
When node B calls a non-SIP phone on node A, everything works as expected.

Both systems are running firmware 6.0.11. System Forward Initiate is set to 15 on both systems.

Any ideas on how I could work around this? Is this a limitation of using SIP endpoints?

Thanks,

Pages: [1]