8.1.69 twinning issue

[AACon]

Ran into a weird issue after an upgrade. Twinning no longer seems to work as normal. When calling an extension that is twinned to an external mobile device, as soon as the mobile device starts to ring, the users desk phone stops ringing, almost like the mobile phone answered...but did not. They get about 1 ring, and then nothing. No forwarding on for the user or anything goofy like that. Defaults are in place for mobile dial delay (2 seconds), user is not logged out or anything.
Anyone else run into this?

-Austin
ACE: Implement IP Office

 

[holdmusic34]

Yes believe it has been seen mate. I'm sure it's on a current thread. The tech had to go down to 8.1.63.
On a mobile so can't link to it.

 

[AACon]

Yeah? Guess the search is broken for me . Thing works fine on my system...

-Austin
ACE: Implement IP Office

 

[holdmusic34]

I've been looking for you while munging my kfc and antibiotics but can't find it. I only remember the tech doesn't post all the time.
The post was def related to 8.1.69 and twinning with you issue mentioned though.
Maybe it was such a bombshell it was rf
Google's no help either. Maybe i'm delirious.
Clue:reckon peter responded. Check his replies!

 

[holdmusic34]

Can't find it man. Sorry.
Pretty sure the tech was dealing with a Siemens carrier tech at the same time who made recommendations to the config after the ip office tech got it working by downgrade. The tech didn't want to keep playing with it once he had it working again and left it there.

 

[tlpeter]

AAcon, this sounds like twinning and analog trunks.
Are you sure you use supported trunks? (just to be sure)


BAZINGA!

I'm not insane, my mother had me tested!

 

[AACon]

I knew someone would ask that. No, it's a PRI, all day long.

-Austin
ACE: Implement IP Office

 

[Westi]

http://www.tek-tips.com/viewthread.cfm?qid=1713481

above thread had issues with calls on PRI and downgrading did the trick, you could also upgrade and see if 8.1.73 fixes it.


they drive me nuts when they break analog trunks

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

“Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.”

 

[intrigrant]

I just installed a 8.1.69 with 30 users using twinning over BRI & SIP lines without a problem.
Maybe it is related to the PRI, there are known issues with PRI as this release was delayed because of those problems.

 

[holdmusic34]

@ Westi
thanks!

 

[Westi]

you are welcome, but for what?

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

“Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.”

 

[AACon]

So, this issue persists even after an upgrade to 8.1.73.

The deskphone will ring briefly, and then twin out as soon as the trunk connects. Monitor shows: CALL LOST(CMCauseAnsweredByOther).
This would make sense if the call was actually answered, but it is not, it's still ringing on the twinned device.

I'm wondering if it's an issue with the T1/PRI provider. Sometimes when dialing a DID (ends in 3305), monitor/ssa will show a DID of 3300 coming in...hard to pinpoint where the issue is exactly.



-Austin
ACE: Implement IP Office