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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How change analog extension to ip
- Thread starter marcosa
- Start date
explain some more please ....
The analoqe number sits in the md .
The connection to callmanager is a trunk .
You can't exchange this analoqe internal number
in the md to ip in the callmanager .
What you can do is to direct incoming calls to this
number over the trunk to callmanager and a H.323 extension there .
But theese extensions are completly isolated from eachother.
Note!
You really dont need cisco callmanager if you have a md110.
Update it to BC11 or BC12 and its fully IP extension enabled (and bc12 network md's directly via md's ELU32 card),and you have full feature transparency between
ip-extensions ,cordless extensions , analoqe extensions ,
digital extensions ,mobile extensions and operator.
Hope i got the scenario right.
Regards
SYAR
The analoqe number sits in the md .
The connection to callmanager is a trunk .
You can't exchange this analoqe internal number
in the md to ip in the callmanager .
What you can do is to direct incoming calls to this
number over the trunk to callmanager and a H.323 extension there .
But theese extensions are completly isolated from eachother.
Note!
You really dont need cisco callmanager if you have a md110.
Update it to BC11 or BC12 and its fully IP extension enabled (and bc12 network md's directly via md's ELU32 card),and you have full feature transparency between
ip-extensions ,cordless extensions , analoqe extensions ,
digital extensions ,mobile extensions and operator.
Hope i got the scenario right.
Regards
SYAR
A comment & a question :
Comment :
The importance of feature transparency mentioned by SYAR should not be underestimated. We currently have a Cisco Call Manager connected to our Ericsson BC10 with a QSig tieline. But there is no co-operation between the two oregarding common, useful features such as Group Call Pickup, Group Hunt, Callback, Supervision (monitoring of another extension), simple Diversion, ....
Also, you end up having to administer two different systems and have the added burden of trying to get some sort of integration and basic cooperation between the two.
Question :
It seems that there is no provision on an IP extension to Supervise (monitor) other Ericsson extensions, such as can be done on the DBC3213 digital using MDN and MNS. If this is so, how does one implement this feature at a BC12 site. Do you need to retain the traditional LIM in order to run ELU28 cards for digitals or is there some sort of 19" rack mount device such as the Ericsson Enterprise Branch Gateway (EEBG) which can accept ELU28s and retain full funtionality ?
The EEBG can accept TLU and ELU21 cards, although I believe the analogue cards cannot be used for faxing. You need a DRG for that, I am told. Can an EEBG also accept an ELU28 to run a DBC213 or newer model digital ?
The sort of application I have in mind is the small branch office with say 20 - 100 extensions, mostly IP handsets, but also requiring a receptionist position with the ability to monitor other extensions and handle lots of calls - traditionally the job of a DBC213. Can this be done in BC12 without the old style magazines ?
There remains a need for supporting legacy analogue equipment. There is all sorts of 3rd party equipment on the market designed for analogue lines which I think will be around for quite a while yet.
regards, John
Comment :
The importance of feature transparency mentioned by SYAR should not be underestimated. We currently have a Cisco Call Manager connected to our Ericsson BC10 with a QSig tieline. But there is no co-operation between the two oregarding common, useful features such as Group Call Pickup, Group Hunt, Callback, Supervision (monitoring of another extension), simple Diversion, ....
Also, you end up having to administer two different systems and have the added burden of trying to get some sort of integration and basic cooperation between the two.
Question :
It seems that there is no provision on an IP extension to Supervise (monitor) other Ericsson extensions, such as can be done on the DBC3213 digital using MDN and MNS. If this is so, how does one implement this feature at a BC12 site. Do you need to retain the traditional LIM in order to run ELU28 cards for digitals or is there some sort of 19" rack mount device such as the Ericsson Enterprise Branch Gateway (EEBG) which can accept ELU28s and retain full funtionality ?
The EEBG can accept TLU and ELU21 cards, although I believe the analogue cards cannot be used for faxing. You need a DRG for that, I am told. Can an EEBG also accept an ELU28 to run a DBC213 or newer model digital ?
The sort of application I have in mind is the small branch office with say 20 - 100 extensions, mostly IP handsets, but also requiring a receptionist position with the ability to monitor other extensions and handle lots of calls - traditionally the job of a DBC213. Can this be done in BC12 without the old style magazines ?
There remains a need for supporting legacy analogue equipment. There is all sorts of 3rd party equipment on the market designed for analogue lines which I think will be around for quite a while yet.
regards, John
whosrdaddy
Vendor
EEBG is nothing more than a stupid webswitch 2000. this means NO analog extensions by default, you need like you said an analog card which is specific for webswitch (is no MD110 hardware) so forget about putting digital extensions on the EEBG. your need for support to have traditional hardware will be adressed in future version of the MD110 where the switching part will be overtaken by a standard unix server (MECS).
- Thread starter
- #5
An easier way would be to
EXTEE
IR=1111;
NANSE:NUMTYP=EX,NUMSE=1111;
Initiate 1111 as common abbrivated number:
NANSI:NUMTYP=AC,NUMSE=1111;
initiate the common abbrivated number with
access code(xx) for the ip-trunk + the H.323.number(yyyy)
ADCOI:ABB=1111,CLASS=0&3,TRA=XXYYYY;
syar
EXTEE
IR=1111;NANSE:NUMTYP=EX,NUMSE=1111;
Initiate 1111 as common abbrivated number:
NANSI:NUMTYP=AC,NUMSE=1111;
initiate the common abbrivated number with
access code(xx) for the ip-trunk + the H.323.number(yyyy)
ADCOI:ABB=1111,CLASS=0&3,TRA=XXYYYY;
syar
- Thread starter
- #7
- Thread starter
- #8
You pick out one number from the EX range .
And put it in the ED range series.
e.g
NANSE:NUMTYP=EX,NUMSE=2212;(not neccesary if not used)
NANSI:NUMTYP=ED,NUMSE=2212;
Or if 22xx is unused use only 22 as numse and roddi.
That will give 2200-2299 , 100 numbers if 4.digits.
Then make the destination
RODDIEST=2212,ROU=X,SRT=1,ADC=..;
Does this make sense for you...
syar
And put it in the ED range series.
e.g
NANSE:NUMTYP=EX,NUMSE=2212;(not neccesary if not used)
NANSI:NUMTYP=ED,NUMSE=2212;
Or if 22xx is unused use only 22 as numse and roddi.
That will give 2200-2299 , 100 numbers if 4.digits.
Then make the destination
RODDI
EST=2212,ROU=X,SRT=1,ADC=..;Does this make sense for you...
syar
- Thread starter
- #10
- Status