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

Conferencing using Siemens optipoint 420

Status
Not open for further replies.

AntBan

Technical User
Nov 5, 2001
80
US
Hi,
I have Siemens HiPath 4000 Release 5.0 system which has SIP phones (optipoint 420) and Digital stations configured. Conferencing works fine on Digital stations but on SIP station I see the message "conference refused" on the phone. I configured the conference uri on the phone following the below documentation but it still fails.

I am calling from Digital StationA(5021)to SIP StationB(5032)then hit Consult/transfer (StationA plays MoH here), dial Digital StationC(5022) and then hit "Add to conference" on SIP Station B.

I see the following SIP message on wireshark "484 Address incomplete".

Please find attached the wireshark trace too.
 
I don't have the SIP ones, I have the IP ones, but in the document you referenced have a look at page 4-23 where you indicate what features the phone is allowed to access - I would assume local conference should be checked if it isn't already.

That's all I can offer, sorry...
 
Most of those parameters that are buried in the guts of the optiPoint 420 SiP phone are used only when connecting the device to a SiP Service Provider, where practically every feature must be built to conform to the vendor's specs, e.g. the vendor's Conference server's URI. That document whose link you provided clearly states this information near the front of the document.

If the SiP phone is working for station-to-station calls on the 4K V5, then all you should need to do to support Conference or "Second Call" on the optiPoint 420 SiP is to add the attribute "MBCHL" to the SiP phone's AMO SDAT record.
CHA-SDAT:<station number>,TYPE=ATTRIBUT, then add MBCHL.

Please post the results. Should work in V5.
Note: I'm not sure if changing the conference URI XML parameter will present a conflict or not, but my guess is NOT.
 
Hi, Thanks for your response. My station already has the attribute MBCHL. Find below the output of the dis-sdat command.

DISPLAY-SDAT:STNO=5032;
H500: AMO SDAT STARTED

---------------------------- SUBSCRIBERDATA ----------------------------
STNO = 5032 COS1 = 5 DPLN = 0 SSTNO = NO
PEN : 1- 1- 1- 3 COS2 = 5 ITR = 0 TRACE = NO
DVCFIG : S0PP LCOSV1 = 15 COSX = 0 ALARMNO = 0
AMO : SBCSU LCOSV2 = 15 SPDI = 30 RCBKB = NO
LCOSD1 = 15 SPDC1 = RCBKNA = NO
KEYSYS : LCOSD2 = 15 SPDC2 =
------------------------------------------------------------------------
CDRACC =
SRCGRP = 1 TCLASS =
CLASSMRK = EC G711 G729AOPT
PUBNUM = 4085270000 TON = NATIONAL NPI = ISDN
NNO = 100 HOTIDX =
STNOOOS = MVHFAIP = NO
STNOAPE = AMOALTRT = NO
GWIPADR : CLUSTID =
SVCDOM =
PRECLEV =
BWLIDX =
CLASSSEC = SECURE
------------------------------- ATTRIBUTES -----------------------------
KN VC DMCALLWD MBCHL
------------------------------------------------------------------------

AMO-SDAT -111 ADMINISTRATION OF SUBSCRIBER ATTRIBUTES AND DATA
DISPLAY COMPLETED;
 
Hi,
After investigating a lot and opening a ticket with Siemens Service Perosnnel, he worked on the system for two days to make this work and finally gave me the following answer.

"A SIP terminal can take part in a conference, but cannot initiate one on Hipath 4000 Rel 5.0"
Also, this seems to be the case with "blind transfer".

Thanks for your help in trying to debug the issue.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top