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

BCM400 => Asterisk: no ringing near end ex BCM 2

Status
Not open for further replies.

cndr99

Programmer
Jun 5, 2016
71
CA
Hello Everyone, and Happy New Year!

I've run into an issue that has me scratching my head - perhaps someone might have a suggestion?

We have Nortel T- and M-series phones on a BCM400/3.7 It has a SIP trunk over private network to Asterisk 20.5.0 box, with SIP extensions and a Digium Analog Gateway registered to it.

Calls made from any of the Nortel phones through the BCM to the Asterisk to a SIP extension or through Digium Gateway do not hear any ringing signal.

While ringing on the far end, call status in Asterisk monitor shows trunks Ringing, but BCM Monitor only shows Dialing - then Connected, once answered - never ringing.

BCM Extension -> BCM400 -> SIP TRUNK -> ASTERISK --------------------> SIP Extension
\-> Digium Gateway -> Analog Extension


Calls in the reverse direction from SIP or Analog extensions do receive ringing signal.

Caller ID works in both directions.

I've been through all the settings on the Asterisk box, tried forcing its trunks to ring.

Cannot find anything in the BCM - nothing seems to enable ringing on the near end on calls from the BCM extensions.

Is it possibly a limitation of SipUA 36.110.0.67 - or is there something we have overlooked?

Thanks!


Verulam Telephone:
Communicating is our Pleasure!

Serving Northern Ontario
 
My thoughts are if it's something that was working fine, but no longer is now.

Or is it that you are still configuring the SIP link to the BCM?



Firebird Scrambler

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

Website = linkedin
 
Thanks - should have mentioned that as well - it was working before...

Before the BFT went defective and nuked the hard-drive. Swapped the MSC onto a new BFT, and then inserted fresh hard-drive.

Had to start with fresh image of 3.7, and most - but not all - of the programming restored from backups. Most significantly, none of the telephony programming would restore, so had to start again from scratch and poor documentation of the previous setup.

What changed:

BCM 3.7 is now fully patched, previous system was patched only as far as BCM_370.203_VP2.41.0303 dated 02/13/2007.

Asterisk is now at version 20.5.0, previous was 18.0.0.

I strongly suspect its an issue with Asterisk - but thought I might start here and see if anyone else had dealt with it from the BCM end.

Ringing at the near end is heard normally on trunk calls to outside the system.
 
SIP Messages from Asterisk:

[tt] xINVITE sip:X74@192.XXX.XXX.XXX:5060 SIP/2.0
192.XXX.XXX.XXX:5060 192.XXX.XXX.XXX:5060xVia: SIP/2.0/UDP 192.XXX.XXX.XXX:5060;rport;branch=z9hG4bKPj1
qqqqqqqqqqwqqqqqqqqq qqqqqqqqqqwqqqqqqqqqx2b30e-1ed9-4176-92be-97cc4947fdd8
x INVITE (SDP) x
09:23:05.418500 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x
+0.004245 x 401 Unauthorized x
09:23:05.422745 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x
+0.000269 x ACK x
09:23:05.423014 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x
+0.000163 x INVITE (SDP) x
09:23:05.423177 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x
+0.005704 x 100 Trying x
09:23:05.428881 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x
+0.078753 x 180 Ringing x
09:23:05.507634 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x
+0.001104 x 180 Ringing x
09:23:05.508738 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x
+6.216181 x CANCEL x
09:23:11.724919 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x
+0.002416 x 200 OK x
09:23:11.727335 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x
+0.001026 x 487 Request Terminated x
09:23:11.728361 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x
+0.000465 x ACK x
09:23:11.728826 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x


xFrom: "XXXXXXX XXX" <sip:+XXXXXXXXXX@192.XXX.XXX.XXX>;tag=d1
xd048-ac0c-4889-83d6-6100e11083fd
xTo: <sip:874@XXX.XXX.XXX>
xContact: <sip:asterisk@XXX.XXX.XXX:5060>
xCall-ID: eb9e4957-024d-46fc-b8a0-e47e268732fb
xCSeq: 7966 INVITE
xAllow: OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, RE
xSTER, SUBSCRIBE, NOTIFY, PUBLISH, MESSAGE, REFER
xSupported: 100rel, timer, replaces, norefersub, histinfo
xSession-Expires: 1800
xMin-SE: 90
xMax-Forwards: 70
xUser-Agent: FPBX-16.0.40.7(20.5.0)
xContent-Type: application/sdp
xContent-Length: 341
x
xv=0
xo=- 1430735690 1430735690 IN IP4 192.XXX.XXX.XXX
xs=Asterisk
xc=IN IP4 192.XXX.XXX.XXX
xt=0 0
xm=audio 15964 RTP/AVP 0 8 3 111 9 101
xa=rtpmap:0 PCMU/8000
xa=rtpmap:8 PCMA/8000
xa=rtpmap:3 GSM/8000
xa=rtpmap:111 G726-32/8000
xa=rtpmap:9 G722/8000
xa=rtpmap:101 telephone-event/8000
xa=fmtp:101 0-16
xa=ptime:20

/tt
 
 https://files.engineering.com/getfile.aspx?folder=c2e0b29b-a83d-421d-88f6-1a29c8b96bd8&file=874.PNG
[tt]xSIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.XXX.XXX.XXX:5060;rport=5060;received=192
x68.2.244;branch=z9hG4bKPjcab94d97-325f-472e-a297-08a46c4491
x
xCall-ID: eb9e4957-024d-46fc-b8a0-e47e268732fb
xFrom: "XXXXXXX_XXX" <sip:+XXXXXXXXXX@192.XXX.XXX.XXX>;tag=d1
xd048-ac0c-4889-83d6-6100e11083fd
xTo: <sip:874@192.XXX.XXX.XXX>;tag=cb10fc22-c7ad-4c76-8dfc-764
xefc404b
xCSeq: 7967 INVITE
xServer: Digium Gateway
xContact: <sip:192.XXX.XXX.XXX:5060>
xAllow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BY
x CANCEL, UPDATE, PRACK, REGISTER, REFER, MESSAGE
xP-Asserted-Identity: "Digium 4" <sip:874@192.XXX.XXX.XXX>
xContent-Length: 0[/tt]


Perhaps I have missed something obvious?
Signal Ringing is enabled on all routes on the Asterisk.
 
BCM 3.7 ran on Windows NT. It wasn't the best and patching it often caused more grief if done in the wrong order.

Sometimes another patch needed to be updated prior to the one you needed.

Firebird Scrambler

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

Website = linkedin
 
Yes - I saw that, but could not find a complete list for the order of operations, so I waded through all the 'readme' files and made sure the prerequisites went in first...do you happen to have a complete list in order for patching? Here's what I have for patches:

BCM_370.033_VP.41.001
BCM_370.039_SECURITY.00.896422
BCM_370.039_SECURITY.00.999999
BCM_370.040_MSM.26.202
BCM_370.041_MSCSVC.20.372100
BCM_370.053_UM2.39.001
BCM_370.060_WANDVR.17.241
BCM_370.061_WIN.00.899588
BCM_370.061_WIN.00.999999
BCM_370.062_NRU.16.1001
BCM_370.080_MPS.34.003
BCM_370.094_CDR.64.151
BCM_370.097_ALRMMON.46.11
BCM_370.102_DSPFW.09.5125
BCM_370.110_CUMULATIVE.99.1
BCM_370.114_QOS.70.3709
BCM_370.116_IPSEC.71.3707
BCM_370.117_CORE.08.0709
BCM_370.119_VM.22.0104
BCM_370.120_UTPS
BCM_370.126_FEPS.33.371900
BCM_370.127_BRU.10.020
BCM_370.130_IPVSB.62.012
BCM_370.132_SETFW.56.161
BCM_370.139_HGMR.148.240
BCM_370.148_OS.00.001
BCM_370.151_SIPUA.67.361100
BCM_370.155_PCM.43.129
BCM_370.157_CTE.40.251
BCM_370.158_CPISB.22.2500628
BCM_370.159_WIN.00.911280
BCM_370.161_UM3.39.002
BCM_370.166_DSPFW.09.5134
BCM_370.169_DP.57.017
BCM_370.171_WIN.00.917159
BCM_370.174_CP.22.2500629
BCM_370.175_FEPS.33.372200
BCM_370.179_WIN.00.921883
BCM_370.183_CORE.08.0714
BCM_370.184_IVR.02.3509
BCM_370.189_UTPS.12.17180
BCM_370.191_RCC.61.344
BCM_370.192_VM.22.0109
BCM_370.197_SRG.51.1103
BCM_370.197_UTPS
BCM_370.201_CTI.01.370141
BCM_370.203_VP2.41.0303
BCM_370.204_CP.22.2500630
BCM_370.209_MSCSVC.20.372200
BCM_370.212_QOS.70.3710
BCM_370.213_SU.99.3
BCM_370.215_VP5.41.001
BCM_370.222_VP3.41.001
BCM_370.226_VM.22.0110
BCM_370.237_UM3.39.003
BCM_370.240_VP6.41.001
BCM_370.243_BRU.10.021
BCM_370.245_UTPS
BCM_370.248_FEPS.33.372602
BCM_370.249_CORE.08.0723
BCM_370.250_DSPFW.09.5137
BCM_370.252_RCC.61.358
BCM_370.255_VP7.41.003
BCM_370.256_OS4.00.003


 
I have most of the patches on my FTP Server, should you be needing any. Just follow the link to find out more information.

I'm guessing that after you updated the patch that the BCM 400 was rebooted?, It might be worthwhile doing a backup which if I recall was a pain to setup and do compared to the later 4.0 release.

Then do a controlled shutdown for a few minutes, before powering it up again.

The patch list I have is..

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

PATCH ID: BCM370.200-BIOS Category: GEN
PATCH ID: BCM00168 Category: GEN
PATCH ID: BCM370.243-BRU Category: GEN
PATCH ID: BCM370.252-RCC Category: GEN
PATCH ID: BCM370.256-OS4 Category: GEN
PATCH ID: BCM370.209-MSCSVC Category: GEN
PATCH ID: BCM370.213-SU3 Category: GEN
PATCH ID: BCM370.250-DSPFW Category: GEN
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 (increases disk space on the F drive)
PATCH ID: BCM370.204-CP Category: GEN
PATCH ID: BCM370.226-VM Category: GEN
PATCH ID: PreCheck_Tool Category: GEN
PATCH ID: BCM370.237-UM3 Category: GEN
PATCH ID: BCM370.245-UTPS-SRG Category: GEN
PATCH ID: BCM370.248-FEPS Category: GEN
PATCH ID: BCM370.212-QOS Category: GEN
PATCH ID: BCM370.227-WANDVR Category: GEN
PATCH ID: Patch_Wizard2.5 Category: GEN
PATCH ID: BCM370.249-CORE Category: GEN



Firebird Scrambler

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

Website = linkedin
 
Yes - it was rebooted several times during the patching.

The backups are complete copies of the original hard drive, made once the system was programmed properly and then put in a cool, dry place. I think the BRU is just about useless in these kind of situations.

Talk about a pain: i forgot about half the settings and had to rebuild a bunch of it from scratch - which is now documented in nauseating detail for going forward.

Thank goodness the system wasn't really needed for a few days due to the holidays!!!

Thanks for the patch list...wow you have a great site!

Could not locate: PATCH ID: BCM00168 Category: GEN

Cheers, and Happy New Year!





 
I wasn't aware that I had a missing patch BCM00168 Category: GEN. Hopefully one of my colleagues will have a copy.

Happy New Year

Firebird Scrambler

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

Website = linkedin
 
That patch/fix was for: Restore Usergroup List Update

I wouldn't worry about that one.

HNY to all!





small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top