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 biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

FWD All Mitel 5000 on SIP 2

Status
Not open for further replies.

liquidshokk

Technical User
Jan 31, 2007
940
GB

Hi

Having problems forwarding all calls for a user on a SIP DDI either by setting the forward information (using SIP trunk CO Group, associated TG username/description, forward type 1 and forward public network set to yes) or by the phone "FWD All" key which also sets the forward information correctly. When the extension is called internally the extension forwards to mobile correctly but calls to the users DDI don't forward and just give engaged tone. I assume this is a SIP specific issue as works fine on ISDN.

Is there something that needs setting to allow DDI call forwarding on SIP DDI's?

Thanks
 
I believe the issue is that the SIP carrier does not allow the calling parties CLI to be passed through their service.
You will need to find how to replace the Calling Party ID with one within your DDI range. ISDN was more forgiving and normally replaced it at the carrier level if it didn't match the DDI range (in AU anyway)

Not 100% sure where this is in the 5000.
 
Look at 'Propagate Original Caller ID' in the Trunk Group Parameters and change it to 'no' if it is set to yes.
 
Thanks. The plot thickens then.. On our test system I set the DDI that is pointing at the forwarded user as the calling party number and the SIP ddi forwarded the call! Hurrah... BUT, when I try this on the customer system with the same set up I'm still getting busy tone.... I'm guessing the SIP provider doesnt like th CLI that I'm sending out despite it being the DDI on that SIP circuit?!
 
SIP provider may be expecting the main circuit number rather than a DDI< shot in the dark. have you checked what number is being presented by the system in each forward scenario.

Is there anywhere where you can set CPN on the 5000; on the 3300 you can set these also; Public Calling Party Number Passthrough (which would have to be NO)
Use Diverting Party Number as Calling Party Number (which would be set as yes) anything similar on 5000?
 
SOLVED! You both win :)

On the site where this wasn't working the calling party number didnt have any effect at all but changing Propogate Original Caller ID to YES rather than the usual NO made the forward work.

Funny, as on the site that was working from the start the forward worked with it set to NO, but they are using different SIP providers.

Thanks for your help
 
I have an open DCR for this, On SIP trunks it depends on the SIP provider if its authenticated the forwarded call will may fail as the Propogate Original Caller ID ption causes the SIP invite P-Asserted ID From and From headers to all get over written with the incoming CLI and the SIP server has nothing to authenticate with.

With SIP trunk with no authentication the setup is trusted via the originating IP so it generally works.

If its not broke tweak it..
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top