connections do not complete because of timeout

[claudiolpena]

connections do not complete because of timeout
how can i increase timeout in sip trunk in bcm400 ?

 

[curlycord]

Which release do you have?
examples 3.X or 4.0

If 4.0 then Resources/IP Trunks/SIP Trunking/Accounts/UserAccounts/ Modify the Expiry at the bottom of the popup window.


________________________________________

Add me to LinkedIN

=----(((((((((()----=

http://www.curlycord.com

Toronto, CAN

 

[claudiolpena]

hi
the release is 4.0.2.03
I using IP trunk and some calls do not complete because they require more time.

 

[curlycord]

Sorry I should have said if R6 and not 4.0

You may want to post a lot more details as to setup and where you see this error and how you are dialing.


________________________________________

Add me to LinkedIN

=----(((((((((()----=

http://www.curlycord.com

Toronto, CAN

 

[claudiolpena]

I have an IPO500 interconnected with the bcm
I make the IPO call and leave through the BCM
in the BCM the call enters by IP Trunk and exits by PRI Trunk
some long-distance calls complete
and some long distance calls do not complete because they need more time
the IP Trunk is canceling the connection
so i need increase the IP Trunk timeout

 

[claudiolpena]

hi
this is a trace of IPO500 requesting timeout

863590328mS Sip: License, Valid 1, Available 5, Consumed 0
863590338mS Sip: 17.23748.0 7223 SIPTrunk Endpoint(f55c0080) received CMSetup
863590340mS SIP Call Tx: 17
INVITE sip:00211137378256@192.168.50.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.54.150:5060;rport;branch=z9hG4bKa53bbf56b2851cc4724fae3d89b843aa
From: "Anonymous" <sip:3137865561@192.168.50.150>;tag=d8b7735362174871
To: <sip:00211137378256@192.168.50.150>
Call-ID: 585a73765218aabcd671ea350156290f@192.168.54.150
CSeq: 1541940112 INVITE
Contact: "Anonymous" <sip:3137865561@192.168.54.150:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO
Content-Type: application/sdp
Content-Length: 226

v=0
o=UserA 419433452 924337 IN IP4 192.168.54.150
s=Session SDP
c=IN IP4 192.168.54.150
t=0 0
m=audio 49152 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
863590341mS SIP Tx: UDP 192.168.54.150:5060 -> 192.168.50.150:5060
INVITE sip:00211137378256@192.168.50.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.54.150:5060;rport;branch=z9hG4bKa53bbf56b2851cc4724fae3d89b843aa
From: "Anonymous" <sip:3137865561@192.168.50.150>;tag=d8b7735362174871
To: <sip:00211137378256@192.168.50.150>
Call-ID: 585a73765218aabcd671ea350156290f@192.168.54.150
CSeq: 1541940112 INVITE
Contact: "Anonymous" <sip:3137865561@192.168.54.150:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO
Content-Type: application/sdp
Content-Length: 226

v=0
o=UserA 419433452 924337 IN IP4 192.168.54.150
s=Session SDP
c=IN IP4 192.168.54.150
t=0 0
m=audio 49152 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
863590352mS SIP Rx: UDP 192.168.50.150:5060 -> 192.168.54.150:5060
SIP/2.0 100 Trying
From: "Anonymous"<sip:3137865561@192.168.50.150>;tag=d8b7735362174871
To: <sip:00211137378256@192.168.50.150>
Call-ID: 585a73765218aabcd671ea350156290f@192.168.54.150
CSeq: 1541940112 INVITE
Via: SIP/2.0/UDP 192.168.54.150:5060;rport=5060;branch=z9hG4bKa53bbf56b2851cc4724fae3d89b843aa
Supported: 100rel,sipvc
User-Agent: Nortel Networks BCM VoIP Gateway release_41 version_41.500.0.33
Privacy: None
Contact: <sip:00211137378256@192.168.50.150>
Allow: INVITE,UPDATE,INFO,ACK,OPTIONS,CANCEL,BYE,NOTIFY,PRACK
Content-Length: 0

863590354mS SIP Call Rx: 17
SIP/2.0 100 Trying
From: "Anonymous"<sip:3137865561@192.168.50.150>;tag=d8b7735362174871
To: <sip:00211137378256@192.168.50.150>
Call-ID: 585a73765218aabcd671ea350156290f@192.168.54.150
CSeq: 1541940112 INVITE
Via: SIP/2.0/UDP 192.168.54.150:5060;rport=5060;branch=z9hG4bKa53bbf56b2851cc4724fae3d89b843aa
Supported: 100rel,sipvc
User-Agent: Nortel Networks BCM VoIP Gateway release_41 version_41.500.0.33
Privacy: None
Contact: <sip:00211137378256@192.168.50.150>
Allow: INVITE,UPDATE,INFO,ACK,OPTIONS,CANCEL,BYE,NOTIFY,PRACK
Content-Length: 0

863590355mS Sip: Find End Point 17.23748.0 7223 SIPTrunk Endpoint (f55c0080) Sip CallId 585a73765218aabcd671ea350156290f@192.168.54.150

********** SysMonitor v10.0.0.1.0 build 53 [connected to 192.168.54.150 (DCML_CONTAGEM)] **********
863600346mS SIP Rx: UDP 192.168.50.150:5060 -> 192.168.54.150:5060
SIP/2.0 408 Request Timeout
From: "Anonymous"<sip:3137865561@192.168.50.150>;tag=d8b7735362174871
To: <sip:00211137378256@192.168.50.150>;tag=404b86b0-9632a8c0-13c4-5ae1baab-2dae9441-5ae1baab
Call-ID: 585a73765218aabcd671ea350156290f@192.168.54.150
CSeq: 1541940112 INVITE
Via: SIP/2.0/UDP 192.168.54.150:5060;rport=5060;branch=z9hG4bKa53bbf56b2851cc4724fae3d89b843aa
Supported: 100rel,sipvc
User-Agent: Nortel Networks BCM VoIP Gateway release_41 version_41.500.0.33
Privacy: None
x-nt-corr-id: 585a73765218aabcd671ea350156290f@192.168.54.150
Allow: INVITE,UPDATE,INFO,ACK,OPTIONS,CANCEL,BYE,NOTIFY,PRACK
Content-Length: 0

863600348mS SIP Call Rx: 17
SIP/2.0 408 Request Timeout
From: "Anonymous"<sip:3137865561@192.168.50.150>;tag=d8b7735362174871
To: <sip:00211137378256@192.168.50.150>;tag=404b86b0-9632a8c0-13c4-5ae1baab-2dae9441-5ae1baab
Call-ID: 585a73765218aabcd671ea350156290f@192.168.54.150
CSeq: 1541940112 INVITE
Via: SIP/2.0/UDP 192.168.54.150:5060;rport=5060;branch=z9hG4bKa53bbf56b2851cc4724fae3d89b843aa
Supported: 100rel,sipvc
User-Agent: Nortel Networks BCM VoIP Gateway release_41 version_41.500.0.33
Privacy: None
x-nt-corr-id: 585a73765218aabcd671ea350156290f@192.168.54.150
Allow: INVITE,UPDATE,INFO,ACK,OPTIONS,CANCEL,BYE,NOTIFY,PRACK
Content-Length: 0

863600348mS Sip: Find End Point 17.23748.0 7223 SIPTrunk Endpoint (f55c0080) Sip CallId 585a73765218aabcd671ea350156290f@192.168.54.150
863600351mS SIP Call Tx: 17
ACK sip:00211137378256@192.168.50.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.54.150:5060;rport;branch=z9hG4bKa53bbf56b2851cc4724fae3d89b843aa
From: "Anonymous" <sip:3137865561@192.168.50.150>;tag=d8b7735362174871
To: <sip:00211137378256@192.168.50.150>;tag=404b86b0-9632a8c0-13c4-5ae1baab-2dae9441-5ae1baab
Call-ID: 585a73765218aabcd671ea350156290f@192.168.54.150
CSeq: 1541940112 ACK
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO
Content-Length: 0

863600351mS SIP Tx: UDP 192.168.54.150:5060 -> 192.168.50.150:5060
ACK sip:00211137378256@192.168.50.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.54.150:5060;rport;branch=z9hG4bKa53bbf56b2851cc4724fae3d89b843aa
From: "Anonymous" <sip:3137865561@192.168.50.150>;tag=d8b7735362174871
To: <sip:00211137378256@192.168.50.150>;tag=404b86b0-9632a8c0-13c4-5ae1baab-2dae9441-5ae1baab
Call-ID: 585a73765218aabcd671ea350156290f@192.168.54.150
CSeq: 1541940112 ACK
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO
Content-Length: 0

863600359mS Sip: ~SipTrunkEndpoint 17.23748.0 -1 SIPTrunk Endpoint

 

[Firebird Scrambler]

You mentioned a BCM 400 system. As Curly had stated above, this system comes in different versions and the last one was at 4.0 which is Linux based and you need to use the BCM Element Manager tool in order to access it. The 3.7 system was accessible via the browser.

Bearing in mind that this is an old product, can you let us know what the current patching level is as the final ones for 3.7 and 4.0 are..

BCM 3.7
==================================

PATCH ID: BCM370.200-BIOS Category: GEN done
PATCH ID: BCM00168 Category: GEN don't have the patch!
PATCH ID: BCM370.243-BRU Category: GEN done
PATCH ID: BCM370.252-RCC Category: GEN done
PATCH ID: BCM370.256-OS4 Category: GEN n/a
PATCH ID: BCM370.209-MSCSVC Category: GEN done
PATCH ID: BCM370.213-SU3 Category: GEN done
PATCH ID: BCM370.250-DSPFW Category: GEN n/a
PATCH ID: BCM370.215-VP5 Category: GEN n/a North America Day light saving hours
PATCH ID: BCM370.222-VP3 Category: LTD n/a Western Australia Day light saving hours
PATCH ID: BCM370.240-VP6 Category: LTD n/a New Zealand patch
PATCH ID: BCM370.255-VP7 Category: LTD n/a Australian Day light saving hours
PATCH ID: BCM370.194-OS2 Category: GEN done (increases disk space on the F drive)
PATCH ID: BCM370.204-CP Category: GEN done
PATCH ID: BCM370.226-VM Category: GEN unable to install
PATCH ID: PreCheck_Tool Category: GEN
PATCH ID: BCM370.237-UM3 Category: GEN done
PATCH ID: BCM370.245-UTPS-SRG Category: GEN unable to install
PATCH ID: BCM370.248-FEPS Category: GEN done
PATCH ID: BCM370.212-QOS Category: GEN done
PATCH ID: BCM370.227-WANDVR Category: GEN n/a
PATCH ID: Patch_Wizard2.5 Category: GEN
PATCH ID: BCM370.249-CORE Category: GEN done


BCM 4.0
==================================

PATCH ID: BCM.R400.SU.System.034-201206 Category: GEN
PATCH ID: BCM.R400.SU.Desktop.020-201203 Category: GEN
PATCH ID: BCM.R400.340-CTE-1.5-1.0 Category: GEN
PATCH ID: BCM.R400.359-ROOTFS Category: LTD
PATCH ID: BCM.R400.140-AASpecializedTransferActivate Category: LTD

Also you need to be aware that SIP trunks were only supported between compatible PABX's. Does the IPO support H323 as the BCM could if licensed work for either protocol.



Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin