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

HiPath4000 V5 Openstage WL3 Call Diversion

Status
Not open for further replies.

tiagofcnmoreira

Technical User
May 12, 2015
67
PT
Hello all,

I have a customer with some SIP phones (Polycom, Huawei, and Unify). However, there is some kind of difference in call diversion on the WL3 phones.

Let me explain, all users from this system are not allowed to forward their calls to external numbers. Everything was working ok, until we deployed some WL3 phones, and those users found out that they could configure Call Forward Unconditional to an external number.
This only happens with WL3 phones, other SIP phones works as it should.

Here is the COS used for SIP phones with external access (the users CAN forward calls to external, but it wasn't supposed to):
ADD-COSSU:,250,,,,,,,,"SIP EG";
CHA-COSSU:COS,250,TA&TNOTCR&CDRATN&DNDOVR&COSXCD&DICT&SPKR&TTT;
CHA-COSSU:COS,250,MTRACE&MSN&CCBS&TP&UUS1IM&UUS3;
CHA-COSSU:COS,250,,NOCO&NOTIE&BASIC&TTT;
CHA-COSSU:COS,250,,,TA&TNOTCR&BASIC&TTT&MSN&UUS1IM&UUS3;

Here is the COS used for SIP phones with NO external access (the user CANNOT forward calls to external, works as it should):
ADD-COSSU:,251,,,,,,,,"SIP-EXT. SEM ACESSO AO EXTERIOR";
CHA-COSSU:COS,251,NOCO&TNOTCR&CDRSTN&CDRC&COSXCD&MB&VCE&FWDNWK;
CHA-COSSU:COS,251,MSN&FWDECA;
CHA-COSSU:COS,251,,NOCO&NOTIE;
CHA-COSSU:COS,251,,,NOCO&NOTIE&MSN;


 
Normally it would be FWDNWK which would control call forwarding to external numbers.
However, I can see that COS 250 has Trunk to Trunk Transfers allowed (TTT) which isn't something you would have on a handset unless you really need it.
I would try removing TTT.

 
The WL3 is a SIP phone also, put it in COS 251 and see
 
Hello,

I already tried putting the COS 251, but it didn't make any difference. Only if I alter LCOSV to one without external access, it works. But that isn't a solution.
I need to have extensions with external access to make calls, but not to ble able to divert their calls to external numbers.
 
Is the phone a NAVAR Night Service phone ?
 
I had already checked that matrix, and the one that I should consider is: Call forwardings (busy/no reply/unconditional) station controlled, which is possible in HiPath4000. However the customer has an HiPath4000 V5, don't know if there are any issues there. The thing being "station controlled", don't know if the problem is there, I mean, it should be the PABX controlling who can or can not forward calls to external destinations.
 
Is the phone a NAVAR Night Service phone ?
Can you forward and remove the forwardings from Comwin and does that make a difference
 
No, it's not a NAVAR. It's a pure SIP phone. If we use the same extension on another phone (for example Polycom), the problem doesn't happen. So I guess it's some kind of imcompatibility between WL3 and HiPath4000 v5.

I got in touch with Unify to see if there are any issues regarding this.
 
I had`t seek anything about WL3 and CFNU for HP4000 v5 to Portal Unify.
I will do it tomorrow.
But generally need to install all new HotFix and new LW.
After you may to look for any errors.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top