Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Tandem Forward 2

Status
Not open for further replies.

AntBan

Technical User
Nov 5, 2001
80
US
I have a QSIG trunk and a non-QSIG PRI (DMS-100) trunk on my Mitel 3300 ICP.

I can make tandem calls through the 3300, and I can transfer calls through it, but I can not forward an inbound call from the DMS trunk out the QSIG trunk.

I checked FAQs, and I have "Public Network to Public Network Connection Allowed" set to "yes".

I am not sure what I am missing. I don't have any kind of "checklist".
 
Make sure the trunk Cor can do it. Go into trunk service and make sure the cor is set to something unrestricted, make sure the cos in there has public access vian dpnss and public to public set to yes and cfwd ext on the trubk cos is yes
 
Thank M1tel
I've checked all settings you mentioned and made sure they are set as per your suggested config, but still no luck. I tested the callforward scenario in the opposite direction (VM--QSIG---MITEl PBX---ISDN---PSTN) and this works. The issue is seen only when the call is originated from the PSTN and is forwarded out to the QSIG trunk (PSTN--ISDN--MITEL PBX--QSIG--VM)

Any idea why this issue would be seen in this direction?

Thanks
 
Have you check system options
DPNSS/QSIG Diversion Enabled
and qsig enabled in the dig link descriptor
 
I was caught by this as well.
If your PRI and QSIG links share the same circuit descriptor you will have this problem. When QSIG is enabled in the link descriptor on the PRI, calls which should forward to other switches do not.

Turn it off for a quick test, if your sharing the descriptor like I did. If the call forwards, then if I recall, I had to delete my QSIG trunk programming to change the descriptor.
 
Thank You AnotherVoipTech2

Your suggestion worked like a charm. Now let's hope the Microsoft Exchange UM box doesn'r break :)

Thanks again.
 
to AVT2

Gave you a star and the owner forgot apparently

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top