Convert IP programmed phone to TDM

[lhiraman]

All,

We are in the early stages of moving from PRIs to SIP. We are on a HipAth 4000 v5 switch. We have about 15 phones that is setup as IP phones but in order to get a SIP trial in, we need to move the 15 phones.

Is there a quick way to move the phones from IP to DIRECT (TDM) without deleting the line and recreating?

Thanks!

I have a ticket open with our provider but it is taking awhile.

 

[LoPath]

I'm a bit confused here. There should be no reason to convert your phones if you're only converting your trunks. You can flip phones from HFA to SIP and vice-versa by changing the firmware. To my knowledge, TDM phones are a different model and can't be converted.

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, Xpressions, Contact Center

 

[sbcsu]

If you only have the one STMI card and it is already setup to provide only IP Phones then yes, you will have to delete (backwards) all the configuration of that card including the phones.
If you REG-SBCSU; REG-SDAT; REG-ZIEL:ALL; REG-ACTDA; REG-PERSI:STN; then you should have all the information when changing the phones to TDM.
A full REGEN of all information before any changes is also advisable.
When changing to TDM just grab the previous (IP Configured) line and change the phone type.
If you already have TDM phones installed then this will be obvious.
The phones themselves will need to be changed as the IP phones (as already outlined) will only work as IP devices, either HiPath Feature Access (HFA) or Session Initiated Protocol (SIP) not Time Division Multiplex (TDM).
TDM on the 4K uses the propitiatory ISDN UP0E of 2 bearer and 1 data channels.

 

[lhiraman]

Hi LoPath,

Thank you for replying. Currently, the IP phones are connected to a 24 port PoE switch, from the PoE switch it is connected to the SMTI4 card. We would like to use the card to handle the SIP service. That is why we are looking to free up the card so we can use the Ethernet port on the STMI4 card for the SIP service.

 

[LoPath]

lhiraman, OK...that makes perfect sense! Good luck with the SIP trunks!

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, Xpressions, Contact Center

 

[Moriendi]

Why not configure the STMI for both trunk and phones ? Are you putting the STMI in DMZ/WAN side so phones can no longer reach it?

 

[lhiraman]

I will be on a DMZ. I was wondering the impression that the STMI4 card had to have all the phones removed from it in-order to conduct a SIP testing with keeping all existing configuration.

The goal of this is to test SIP with a local carrier (cost savings). We currently have 3 PRIs to handle all inbound outbound calls. Having the SIP to test with will require a special access code to make outbound calls, while incoming calls should be allowed via the local number the provide gives us along side the PRIs.

I was told that I would need to remove the extension located on the STMI card before the test can be done.

 

[sbcsu]

If you have only one STMI card you will still have to remove the phones to re-setup the card with a new BFDAT.

 

[Moriendi]

If your STMI is keeping an IP that the phones can reach, then you can reconfigure the card to support both trunk (HG3550) and phones (HG3530). Yes you'll have to delete and readd the phones to do it, but you were going to delete that anyway to make them TDM - easier just to run the regen back in when the card has been reconfigured and keep them as IP.

You are going to have a problem if the STMI is on a private IP and you are NATting from a public IP. The SIP messages the card creates will be built using the private IP - so the to/from headers, the SDP, will all contain the private IP. You will see this if you make a wireshark trace. NAT will get the TCP message from the public IP to the private, but it won't rewrite the contents of the SIP message as well to adjust those IPs. So the end result will be the SIP provider receiving private IPs for SDP that it can't stream RTP to, and you'll get no speech path etc.

You'll need another application like a session border controller which is capable of rewriting the messages on the fly to mask that private IP so the SIP CO only sees the public...

If the STMI has a public IP then that problem will not exist.

 

[lhiraman]

Thanks! The SMTI card will have a public IP. UNIFY decided to send me a routing document. I am currently in process of moving the IP phones fromto TDM.

I will then deal with the reconfiguting the card. Now back to the document, I asked them to create a special code to access the SIP service since this is only a test. I do not know if they expect me to do it myself or what.

I guess it mybe be time to leave UNIFY maintenance and move to blackbox or something because they outsouced all the off-site engineering

 

[donb01]

Just because it's mildly getting on my nerves, please note (unless I am wrong) that TDM phones are "hardwired" phones such as analog and digital phones like OS40T, and use an old school phone cord to hook to a wall jack. There is no way to change IP phones to TDM phones because IP phones hook up with an ethernet cable...

I do understand what your goal was - to remove everything off the board so you can reconfigure it, but the thread title really has nothing to do with that )

Sorry... It's really cold up here in the frigid North so I'm probably more cranky than I usually am!!!


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[lhiraman]

Donb01,

Thanks for the input. I do understand that the subject is miss leading, but the goal was to move off all the IP configured phones to TDM (old school) so the STMI card could be used as the test. I do understand that the IP phones can not be used as TDM phones.