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

Outbound Blind Transfer

Status
Not open for further replies.

szaidi1

IS-IT--Management
Jun 11, 2013
106
PK
System is Avaya IPO 500 v2. Trunk is PRI and all users are analog. Issue is users make an outbound call and on hearing call ringing, they press transfer button to transfer it to another user, call gets disconnected/dropped.

Yes if the far end user picks up the call, then no issue with transferring. On analog trunks, outbound calls get transferred on ringing though.

Any idea?

 
Call needs to be connected to transfer, on analogue trunks there is no signalling so once the number is dialled it's classed as connected :)

 
Hey thanks for the swift reply. There is no workaround you can achieve this type of transfer on PRI?
 
Well just checked with another client where Avaya CM is deployed. Outgoing calls do get transferred on ringing. Here it's a common practice for operators to dial out and as soon as they hear a couple of rings, they transfer it to desired users.

DO you think it has to do with IPO?
 
It would help if you could give an acurate description of your setup & issue

you state that all users are analog but that they are pressing the transfer key to complete the transfer

Analog phoned DO NOT HAVE a transfer key
if they are pressing recal a 2nd time then they have simply placed the outbound call on hold along with the orginal call
(this can also happen if the user bounces the handset to complete the call & then make another)

Here it's a common practice for operators to dial out and as soon as they hear a couple of rings, they transfer it to desired users.
Here that is considered quite rude & unprofessional as it means the call recipient is comletly in the dark as to the nature of the call, in which cace what is the point in haveing an operator?


Do things on the cheap & it will cost you dear
 
Rude may be but then cannot judge... different cultures, different way of dealing stuff I think

Well Operator has a digital phone Avaya 1408. Call disconnects just as he hits the transfer button. Analog phones have this flash button which serves this purpose.

Just witnessed this thing happening smoothly on Avaya CM where users can transfer an outbound call to another user just as they hear ringing.


Should I try this on IP Phones?
 
There should be no problem in performing a bilnd transfer in this way from a digital handset (1408) (analog handsets can have issues if the user does not clear down correctly as previously mentioned)

Have you tried capturing a Monitor trace to see eactly what is occouring.



Do things on the cheap & it will cost you dear
 
User: 3027 name Exchange Room
Dialed Number: 03002231516
0 to seize the line


4:58:00 9558969mS CMCallEvt: 0.5411.0 1456 EXCHANGE_ ROOM.0: StateChange: END=A CMCSRingBack->CMCSCompleted
14:58:00 9558970mS CMExtnEvt: v=25 State, new=PortRecoverDelay old=Alerting,0,0,EXCHANGE_ ROOM
14:58:00 9558973mS CMLOGGING: CALL:2016/01/2914:57,00:00:00,003,3027,O,03002231516,003002231516,EXCHANGE_ROOM,,,0,,""n/a,0
14:58:00 9558974mS CD: CALL: 0.5411.0 BState=Ringing Cut=2 Music=0.0 Aend="EXCHANGE_ ROOM(3027)" (13.27) Bend="Line 9" [Line 9] (5.27) CalledNum=03002231516 () CallingNum=3027 (EXCHANGE_ ROOM) Internal=0 Time=22735 AState=Idle
14:58:00 9558974mS CD: CALL: 0.5411.0 Deleted
14:58:00 9558974mS CMExtnEvt: EXCHANGE_ ROOM: CALL LOST (CMCauseNormal)
14:58:00 9558974mS CMExtnEvt: EXCHANGE_ ROOM: Extn(3027) Calling Party Number(3027) Type(CMNTypeInternal)
14:58:00 9558974mS CMExtnEvt: EXCHANGE_ ROOM: CMExtnHandler::SetCurrent( id: 5411->0 )
14:58:00 9558974mS CMCallEvt: 0.5411.0 -1 EXCHANGE_ ROOM.-1: StateChange: END=X CMCSCompleted->CMCSDelete
14:58:00 9558975mS CMCallEvt: 0.5439.0 -1 BaseEP: NEW CMEndpoint f4f3326c TOTAL NOW=21 CALL_LIST=7
14:58:00 9558975mS CMCallEvt: 0.5439.0 -1 EXCHANGE_ ROOM.-1: NEW CMExtnEndpoint f4f3326c, Name=EXCHANGE_ ROOM, Extn=3027, Phys Extn=3027
14:58:00 9558975mS CMExtnEvt: EXCHANGE_ ROOM: CMExtnHandler::SetCurrent( id: 0->5439 )
14:58:00 9558975mS CMExtnEvt: v=25 State, new=Idle old=PortRecoverDelay,0,0,EXCHANGE_ ROOM
14:58:00 9558975mS CMCallEvt: 0.5439.0 -1 EXCHANGE_ ROOM.0: StateChange: END=X CMCSIdle->CMCSCompletedTone
14:58:00 9558976mS CMExtnEvt: v=25 State, new=CMESCompleted old=Idle,0,0,EXCHANGE_ ROOM
14:58:00 9558978mS CMLineTx: v=9
CMDisconnect
Line: type=Q931Line 9 Call: lid=0 id=5418 in=0
Cause=16, Normal call clearing
14:58:00 9558978mS CMCallEvt: 0.5418.0 -1 Q931 Trunk:9 CHAN=26: StateChange: END=X CMCSRinging->CMCSCompleted
14:58:00 9558978mS CMCallEvt: END CALL:1456 (f463d034)
14:58:00 9558979mS CMTARGET: 0.5411.0 -1 BaseEP: ~CMTargetHandler f4f30bdc ep f509051c
14:58:00 9558979mS CMCallEvt: 0.5411.0 -1 BaseEP: DELETE CMEndpoint f509051c TOTAL NOW=20 CALL_LIST=7
14:58:00 9558979mS CMCallEvt: 0.5440.0 -1 BaseEP: NEW CMEndpoint f509051c TOTAL NOW=21 CALL_LIST=7
14:58:00 9558979mS CMCallEvt: 0.5440.0 -1 EXCHANGE_ ROOM.-1: NEW CMExtnEndpoint f509051c, Name=EXCHANGE_ ROOM, Extn=3027, Phys Extn=3027
14:58:00 9558980mS CMCallEvt: CREATE CALL:1466 (f463d034)
14:58:00 9558980mS CMCallEvt: 0.5441.0 -1 BaseEP: NEW CMEndpoint f477d9dc TOTAL NOW=22 CALL_LIST=7
14:58:00 9558983mS CMExtnEvt: EXCHANGE_ ROOM: CMExtnHandler::SetCurrent( id: 5439->5440 )
14:58:00 9558984mS CMCallEvt: 0.5439.0 -1 EXCHANGE_ ROOM.-1: StateChange: END=X CMCSCompletedTone->CMCSDelete
14:58:00 9558984mS CMCallEvt: 0.5439.0 -1 BaseEP: DELETE CMEndpoint f4f3326c TOTAL NOW=21 CALL_LIST=8
14:58:00 9558984mS CMExtnEvt: v=25 State, new=Idle old=CMESCompleted,0,0,EXCHANGE_ ROOM
14:58:00 9558985mS CMExtnRx: v=3027, p1=0
CMSetup
Line: type=AnalogueExtn 11 Call: lid=0 id=25 in=0
Called[] Type=Default (100) Reason=CMDRdirect Calling[3027] Type=Internal Plan=Default
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
IE CMIECallingPartyName (110)(Type=CMNameDefault) name=EXCHANGE_ ROOM
IE CMIECallingPartyKName (226)(Type=CMNameDefault) name=SERVER ROOM
14:58:00 9558985mS CMCallEvt: 0.5440.0 1466 EXCHANGE_ ROOM.0: StateChange: END=A CMCSIdle->CMCSDialInitiated
14:58:00 9558985mS CMExtnEvt: v=25 State, new=Dialling old=Idle,0,0,EXCHANGE_ ROOM
14:58:00 9558986mS CMTARGET: 0.5440.0 1466 EXCHANGE_ ROOM.0: LOOKUP CALL ROUTE: type=100 called_party= sub= calling=3027 dir=out complete=0 ses=0
14:58:00 9558986mS CMTARGET: 0.5440.0 1466 EXCHANGE_ ROOM.0: ADD TARGET (N): number= type=100 depth=1 nobar=1 setorig=1 ses=0
14:58:00 9558986mS CMCallEvt: 0.5440.0 1466 EXCHANGE_ ROOM.0: StateChange: END=A CMCSDialInitiated->CMCSDialling
14:58:00 9558987mS CMExtnTx: v=3027, p1=0
CMSetupAck
Line: type=AnalogueExtn 11 Call: lid=0 id=25 in=0
BChan: slot=13 chan=27
UUI type=Local [......2Pd..] [0x01 0x02 0x00 0x00 0x00 0x02 0x32 0x50 0x64 0x00 0x00 ]
Timed: 29/01/16 14:58
14:58:00 9558987mS CD: CALL: 0.5440.0 BState=Idle Cut=1 Music=3.0 Aend="EXCHANGE_ ROOM(3027)" (13.27) Bend="" [] (0.0) CalledNum= () CallingNum=3027 (EXCHANGE_ ROOM) Internal=1 Time=7 AState=DialInitiated
14:58:00 9558989mS CMMap: PCG::UnmapBChan pcp[118]b1r0 cp_b f5242498 other_cp_b f5004448
14:58:00 9558989mS CMMap: a=13.27 b=5.27 M02
14:58:00 9558989mS CMMap: PCG::UnmapBChan pcp[376]b1r0 cp_b f5004448 other_cp_b 0
14:58:00 9558990mS CMMap: a=13.27 b=0.0 D1
14:58:00 9558991mS ISDNL3Evt: v=9 stacknum=9 State, new=DiscReq, old=Delivered id=5418
14:58:00 9558991mS ISDNL3Tx: v=9 peb=9
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=001C(Remote)
Message Type = Disconnect
 
Guys anything?

Scenario is there are 200 analog users who do not have dialing-out rights. There are around 10 operators (Digital Avaya 1408/1416) who dial out for them. So if a user wants to talk to someone outside, he dials operator's extension and tells him the number to dial out and then he hangs up. After that operator dials that number and on hearing the ringing, he presses transfer button to transfer it to the desired user.

On analog trunks,there is no problem in this type of transfer. But on PRI, call gets disconnected/dropped on pressing transfer button. No problem when the operator waits for the call to be picked up and then transfers it to the internal user. But this is not desirable.

System Avaya IP Office 9.0. I have checked with AVaya CM. There is no problem in this type of outbound blind transfer.

Could it IPO specific?
 
You need to investigate the feature 'transfer to dialtone'

Alternatively, try moving away from a 1970s mode of operation of a telephone system

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top