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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Twin Mobile over SCN??
- Thread starter delanderb
- Start date
- Thread starter
- #3
Did know that source number so far...
It is not possible to use internal twinning with SCN users. Even if Avaya tries to tell us that SCNed systems and especially Server Edition systems behave like one single system.
You could use external twinning as a workaround but you will not get the twinned user to send the primary phone's number internally.
It is not possible to use internal twinning with SCN users. Even if Avaya tries to tell us that SCNed systems and especially Server Edition systems behave like one single system.
You could use external twinning as a workaround but you will not get the twinned user to send the primary phone's number internally.
Have you tried setting up the users in Server Edition and let them login och the phones on the gateway?
Or put a SARI license to make their DECT bases a separate system and register it on the gateway?
"Trying is the first step to failure..." - Homer
Or put a SARI license to make their DECT bases a separate system and register it on the gateway?
"Trying is the first step to failure..." - Homer
Everything except the option (given by Avaya) to use internal twinning with all solution users doesn't make sense. Even though it is not possible so far.
Think of a primary server with 400 IP phones and an expansion system (IP500V2) to connect ISDN trunks and 20 9508 stations because of missing network cabling. Where should you connect the DECT system? You have to decide if you want to connect it to primary server and be able to twin IP phones with DECT handsets or if you want to connect DECT to IP500V2 and be able to twin digital stations with DECT handsets.
Server edition is not ONE system. It is a network of many single systems.
Think of a primary server with 400 IP phones and an expansion system (IP500V2) to connect ISDN trunks and 20 9508 stations because of missing network cabling. Where should you connect the DECT system? You have to decide if you want to connect it to primary server and be able to twin IP phones with DECT handsets or if you want to connect DECT to IP500V2 and be able to twin digital stations with DECT handsets.
Server edition is not ONE system. It is a network of many single systems.
- Thread starter
- #7
janni1978 said:
That only makes sense if gateway and server are at different locations. If you mostly use IP endpoints connected to the server and a few digital stations connected to the gateway in the same building makes that scenario almost impossible. Besides... you build two DECT systems at one single location. So you will have two base stations next to each other at every BS position ;-)
- Thread starter
- #10
Yes but the problem is the customer has arround 220 digital stations and has @ this moment arround 100 dects on the IP dect gateways ( 3 )
but it wil grow to arround 150. thats 220 + 150 = 370 and ipo gateways goes to 384 extensions
its gona get full full full no
but it wil grow to arround 150. thats 220 + 150 = 370 and ipo gateways goes to 384 extensions
its gona get full full full no
This system is sold terrible.
Why on earth sell digital basestations while you have a server edition?
The dect gateways only are around $12.000 each.
You can buy a lot of IP basestation for that.
But indeed the server edition is sold as one system so kick some ass at Avaya to get the internal twinning working in a server edition.
You could try to create a fake user with a follow me to the dect phone and use the fake user ar the internal twinning destination.
BAZINGA!
I'm not insane, my mother had me tested!
Why on earth sell digital basestations while you have a server edition?
The dect gateways only are around $12.000 each.
You can buy a lot of IP basestation for that.
But indeed the server edition is sold as one system so kick some ass at Avaya to get the internal twinning working in a server edition.
You could try to create a fake user with a follow me to the dect phone and use the fake user ar the internal twinning destination.
BAZINGA!
I'm not insane, my mother had me tested!
- Thread starter
- #12
@ tlpeter yes we know and the customer knows olso its expensif but there was no other option. The IT dept sed NO to IP and they dont want other hardware on there network even on other VLAN's and not enough fiber to create another separed network + the site of the customer is arround 250 meters large and 400 wide and he had already old cabling on site to connect the dect antenna's on Two wires.
thx for the info and help im waiting for avaya support to respond ill post it when i receve it
thx for the info and help im waiting for avaya support to respond ill post it when i receve it
- Thread starter
- #13
So the respons off avaya support :-( :-(
Server edition and twinning
Rate Content Rate this Page
Doc ID: SOLN253308
Version: 1.0
Status: Published
Published date: 15 Jul 2014
Author:
John Tucker
DETAILS
No call switching through at accepting calls by Mobile Twinning from a external call´s
When a external call comes over SCN throug a DS-Port from another IP500V2 and this DS-Port has Mobile Twinning through an IP-DECT User.
PROBLEM CLARIFICATION
This is a installation with a ServerEdition an two IP500V2 attached over SCN.
One IP500V2 (Gateway1) has connection to a IP-Dect Gateway with 7 slaves.
The other IP500V2 (Gateway 2) have a PRI installed for the incoming and outgoing calls. The Gateway 2 have 384 Phone Ports.
The incoming calls are routed from Gateway 2 over SCN to ServerEdition and then to Gateway 1 where a phone is ringing which has Mobile Twinning to a IP-Dect Phone. No internal twinning because both users are to remain selected.
CAUSE
Currently correct operation in a server environment.
This is how twinning works in a Server edition environment it will only show the
local user on the same system not solution wide I.E. across expansion units or
Server edition users
SEEE :
Server edition and twinning
Rate Content Rate this Page
Doc ID: SOLN253308
Version: 1.0
Status: Published
Published date: 15 Jul 2014
Author:
John Tucker
DETAILS
No call switching through at accepting calls by Mobile Twinning from a external call´s
When a external call comes over SCN throug a DS-Port from another IP500V2 and this DS-Port has Mobile Twinning through an IP-DECT User.
PROBLEM CLARIFICATION
This is a installation with a ServerEdition an two IP500V2 attached over SCN.
One IP500V2 (Gateway1) has connection to a IP-Dect Gateway with 7 slaves.
The other IP500V2 (Gateway 2) have a PRI installed for the incoming and outgoing calls. The Gateway 2 have 384 Phone Ports.
The incoming calls are routed from Gateway 2 over SCN to ServerEdition and then to Gateway 1 where a phone is ringing which has Mobile Twinning to a IP-Dect Phone. No internal twinning because both users are to remain selected.
CAUSE
Currently correct operation in a server environment.
This is how twinning works in a Server edition environment it will only show the
local user on the same system not solution wide I.E. across expansion units or
Server edition users
SEEE :
- Status