Maximum call duration - R11.1 SIP Trunks

[tac84]

Hi all,
Is there a system default setting that sets the maximum call duration to 2 hours?

I'm getting disconnected on long teleconferences that exceed two hours and receive a 1 minute warning.

SIP provider is saying it's not their end.

Any advice as always would be greatly appreciated.

Thanks, Tim
Adelaide, Australia

 

[sizbut]

What sort of warning?

It is possible to set a limit to call length in IP Office, but its not used by default and it doesn't provide any form of warning.

Stuck in a never ending cycle of file copying.

 

[tac84]

Hi @sizbut

Yeah it was a strange one.

It was a voiceover (Sounded like the standard automated voice in IPO) basically saying the call will terminate in 1 minute or something like that, then the call was disconnected.

I'm having the SIP provider check again at their end as I couldn't find any setting in IPO that would cause this.

Thanks, Tim
Adelaide, Australia

 

[IPOLackey]

Hey Tac84,

There isn't a max call duration really, however some third party conference providers may disconnect calls where they no longer receive audio from you after a set period of time. Normally it's only 2 mins but this could be different depending on the provider.

What you want to do is capture a sysmon trace of a test call and see who is actually sending the BYE message. This will tell you who's disconnecting the call and where to look further.

 

[sizbut]

Agree. It sounds like scheduled conference reservation or something else was involved in the call. You need to get more detail from the users about what they were doing. It certainly wasn't a simple outgoing or incoming call, it involved some other service.

one-X Portal can be used to configure scheduled conferences. They prompt (through the portal UI) the user 5 minutes before the end and whether the user wants to extend.

There also used to be an IP Office Conferencing Server but that hasn't been supported for ages - how old is the customer system?

More info needed but its not the core IP Office - there is another service involved in the call routing.

Stuck in a never ending cycle of file copying.

 

[tac84]

Thanks all.
I was dialled into a Cisco WebEx teleconference and had my line on mute for two hours. Maybe the webex was what disconnected me. Just thought it was strange that I was the only one booted off. Will see how I go for the rest of the week

Thanks again!

Thanks, Tim
Adelaide, Australia

 

[tac84]

Hi all

Just an update on this one. It happened on today's teleconference but I'm pretty sure it's the Cisco WebEx system I'm dialling into that is disconnecting the call after two hours.

After some more google searches I did see other complaints from other users that dial in using a SIP service..

Nothing appears unusual in the sysmon below to suggest otherwise:

10:31:50 427864443mS SIP Rx: UDP 125.213.XXX.XXX:5060 -> 10.10.XX.XX:5060
BYE sip:09801XXXXXXXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0
Via: SIP/2.0/UDP 125.213.XXX.XXX:5060;branch=z9hG4bK27dd5a0521119ae38bBYE47c599d55fa0
Max-Forwards: 35
To: "09801XXXXXXXXX"<sip:09801XXXXXXXXX@sip10.mynetfone.com.au>;tag=94b7569c153ec0ce
From: <sip:18310293382221@sip10.mynetfone.com.au>;tag=47c59f5d-co24480-INS002
Call-ID: 147f3e4de6b95c8aa756d46279bf6a49
CSeq: 2448001 BYE
User-Agent: ENSR3.0.6
Content-Length: 0

10:31:50 427864446mS SIP Tx: UDP 10.10.XX.XX:5060 -> 125.213.XXX.XXX:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 125.213.XXX.XXX:5060;branch=z9hG4bK27dd5a0521119ae38bBYE47c599d55fa0
From: <sip:18310293382221@sip10.mynetfone.com.au>;tag=47c59f5d-co24480-INS002
Call-ID: 147f3e4de6b95c8aa756d46279bf6a49
CSeq: 2448001 BYE
Supported: timer
Server: IP Office 11.1.1.1.0 build 18
To: "09801XXXXXXXXX" <sip:09801XXXXXXXXX@sip10.mynetfone.com.au>;tag=94b7569c153ec0ce
Content-Length: 0

10:31:50 427864447mS CMLineRx: v=0
CMReleaseComp
Line: type=SIPLine 17 Call: lid=17 id=6570 in=0
Called[] Type=Default (100) Reason=CMDRdirect Calling[2103] Type=Internal Plan=Default
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=018310293382221
IE CMIEDeviceDetail (231) 0a0a0a02000019aa LOCALE=ena HW=15 VER=11 class=CMDeviceSIPTrunk type=0 number=17 channel=1 features=0x0 rx_gain=32 tx_gain=32
ep_callid=6570 ipaddr=10.10.XX.XX apps=0 loc=999 em_a_loc=999 em_d_loc=0 features2=0x0 is_spcall=1 ignores_dtmf=0
avgsid=<>
Cause=16, Normal call clearing
10:31:50 427864447mS CMCallEvt: 0a0a0a02000019aa 17.6570.0 185 SIPTrunk Endpoint: StateChange: END=B CMCSConnected->CMCSCompleted
10:31:50 427864450mS CMExtnTx: v=2103, p1=0
CMFacility
Line: type=IPLine 250 Call: lid=255 id=6567 in=0
IE CMIEFastStartInfoData (6) 2 item(s)
Timed: 07/07/21 10:31
10:31:50 427864450mS CMExtnTx: v=2103, p1=8004
CMFacility
Line: type=IPLine 250 Call: lid=255 id=1 in=1
IE CMIEFastStartInfoData (6) 2 item(s)
10:31:50 427864452mS CMLineTx: v=0
CMFacility
Line: type=SIPLine 17 Call: lid=17 id=6570 in=0
IE CMIEFastStartInfoData (6) 2 item(s)


Thanks again all for your advice.


Thanks, Tim
Adelaide, Australia

 

[IPGuru]

As others gave said IPO does not limit outbound calls without deliberate programming and it most certainly does not play a warning anouncement.

I would hapily bet a family pack of Marsbars that this is the Cisco WebEx & they just happened to employ the same speach artist for the recordings (this is quite uncommon, she seems very popular)




Do things on the cheap & it will cost you dear

 

[tac84]

Agree IPGuru! Cheers.

Thanks, Tim
Adelaide, Australia