Mobile twinning issue in hunt group

[ianns]

Using IP Office 9.

Setup a hunt group to collective ring for an event tomorrow. Created 4 dummy users, mobile twinning enabled, twin hunt groups, twin while logged out.

When calling it I watch system status and it shows a brief connection on all 4 twinned devices before 3 of those drop and only one of the twinned devices rings. This is also random - any 1 of the 4 could be the one to ring.

I tested ringing the user extensions from handsets in the office simultaneously and all twinned devices ring.

Any help would be appreciated.

 

[amriddle01]

How many lines? What type of lines? If analogue forget it

 

[ianns]

SIP lines. 20 licences both in IP office and also with the provider.

 

[amriddle01]

Probably by design to be honest, Avaya probably assume you are trying to use distributed groups without SCN licencing and so block the multiple calls, what does monitor show?

 

[ianns]

Not great with these logs but this looks like the related part as CPSarah and CPShylo are two of the user names in that group. I've deleted phone numbers/IPs. Not sure about that part saying cmcauseansweredbyother as the call was not answered.

15:22:53 678432395mS CMCallEvt: 0.32998.0 6461 CPShylo.0: StateChange: END=T CMCSRinging->CMCSConnReq
15:22:53 678432395mS CMCallEvt: 0.32990.0 6461 TargetingEP: RequestEnd 0.32998.0 6461 CPShylo.0
15:22:53 678432396mS CMTARGET: 18.32983.1 6461 SIPTrunk Endpoint: Removed HG from Callinfo
15:22:53 678432396mS CMCallEvt: 0.32986.0 6461 ACDTep(CPOffice): StateChange: END=??? CMCSIdle->CMCSDelete
15:22:53 678432396mS CMCallEvt: 0.32986.0 -1 BaseEP: DELETE CMEndpoint f4acad70 TOTAL NOW=20 CALL_LIST=9
15:22:53 678432397mS CMTARGET: 18.32983.1 6461 SIPTrunk Endpoint: CancelTimer CMTCNoAnswerTimeout
15:22:53 678432397mS CMCallEvt: 0.32990.0 -1 BaseEP: DELETE CMEndpoint f4be88f0 TOTAL NOW=19 CALL_LIST=9
15:22:53 678432399mS CMExtnEvt: CPSarah: CALL LOST (CMCauseAnsweredByOther)
15:22:53 678432399mS CMExtnEvt: CPSarah: Extn(650) Calling Party Number(///) Type(CMNTypeUnknown)
15:22:53 678432399mS CMCallEvt: 0.32994.0 -1 CPSarah.0: StateChange: END=X CMCSRinging->CMCSCompleted
15:22:53 678432399mS CMExtnEvt: v=-1 State, new=PortRecoverDelay old=Ringing,0,0,CPSarah
15:22:53 678432400mS CMExtnTx: v=650, p1=0
CMReleaseComp
Line: type=NoLine 0 Call: lid=0 id=32994 in=0
Called[650] Type=Default (100) Reason=CMDRdirect Calling[///] Type=Unknown Plan=Default
Cause=124, Answered By Other(IPO)
15:22:53 678432400mS CMExtnEvt: CPSarah: CMExtnHandler::SetCurrent( id: 32994->0 )
15:22:53 678432400mS CMCallEvt: 0.32994.0 -1 CPSarah.-1: StateChange: END=X CMCSCompleted->CMCSDelete
15:22:53 678432401mS CMCallEvt: 0.32991.0 6462 GHOST:: StateChange: END=A CMCSRingBack->CMCSCompleted
15:22:53 678432402mS PRN: CDR - TCPSend maxqueuesize=3000 framecount=0 operational=1
15:22:53 678432403mS CMLOGGING: CALL:2015/02/2615:22,00:00:00,000,///,O,///,///,CPSarah,,,0,,""n/a,0
15:22:53 678432404mS CMCallEvt: 0.32991.0 -1 GHOST:: CallLost (Ghost @) cause=CMCauseAnsweredByOther
15:22:53 678432404mS CMCallEvt: 0.32991.0 -1 GHOST:: StateChange: END=X CMCSCompleted->CMCSDelete
15:22:53 678432405mS CMLineTx: v=0
CMReleaseComp
Line: type=SIPLine 18 Call: lid=18 id=32993 in=0
Cause=124, Answered By Other(IPO)

 

[derfloh]

Cause=124, Answered By Other(IPO)

Looks like Mobile Answer Guard decides to stop the call.