Avaya CM 5.2.1 connection with BSS

1. Brekeke Product Name and Version: sip3_9_5_8

2. Java version: jre-8u271-linux-x64.tar with apache-tomcat-9.0.39

3. OS type and the version: CentOS 7 64bit

4. UA (phone), gateway or other hardware/software involved:

5. Your problem:
we can do setup and testing call in/out from BSS, success. but connection Avaya trunk for BSS still out-of-service-NE. does it need additional device like converter interconnection, or license open-sip for Avaya CM 5.2.1 ?

FYI:
https://docs.brekeke.com/interop/config ... pbx-cm-5-2

Tata wrote:FYI:
https://docs.brekeke.com/interop/config ... pbx-cm-5-2

Hi Tata, thank you for reply.
its previously has been for Avaya CM, but connection trunk status still


status trunk 333 Page 1

TRUNK GROUP STATUS

Member Port Service State Mtce Connected Ports
Busy

0333/001 T00211 out-of-service-NE no
0333/002 T00212 out-of-service-NE no
0333/003 T00213 out-of-service-NE no
0333/004 T00214 out-of-service-NE no
0333/005 T00215 out-of-service-NE no


Administration for the solution required the following steps:
 Add node-names bssdev ip-add
 Add SIP Signaling Group 15
 Add SIP Trunk Group 333
 Add IP-Network-Region 246
 Change Route Pattern 955
 Change AAR Analysis 880xx
 Confirm IP codecs 1
 Change public-unknown-numbering



this Avaya CM 5.2.1. capacity :

display capacity Page 7 of 13
SYSTEM CAPACITY

System
Used Available Limit
-----------------------
TRUNKS
DS1 Circuit Packs: 16 506 522
DS1 With Echo Cancellation: 0 522 522
ICHT For ISDN/SIP Trunks: 165 9834 9999
ISDN CBC Service Selection Trunks: 0 200 200
Trunk Groups: 178 1822 2000
Trunk Ports: 719 11281 12000
H.323 Trunks (included in 'Trunk ports'): 45 5276 5321
Remote Office Trunks (included in 'Trunk ports'): 0 12000 12000
SBS Trunks (included in 'Trunk ports'): 0 1000 1000
SIP Trunks (included in 'Trunk ports'): 115 185 300
Ad-hoc Video Conferencing Ports: 0 100 100


what is it need interconnection device ? or not yet fit the configuration ?
plz help
tq

I recommend you to talk to Avaya admin to configure the trunk because the settings are depending on versions and deployment.

Hi..

SUCCESS!
status trunk avaya now in-service

status trunk 333 Page 1

TRUNK GROUP STATUS

Member Port Service State Mtce Connected Ports
Busy

0333/001 T00211 in-service/idle no
0333/002 T00212 in-service/idle no
0333/003 T00213 in-service/idle no
0333/004 T00214 in-service/idle no
0333/005 T00215 in-service/idle no
0333/006 T00216 in-service/idle no
0333/007 T00217 in-service/idle no
0333/008 T00218 in-service/idle no
0333/009 T00219 in-service/idle no
0333/010 T00220 in-service/idle no
0333/011 T00221 in-service/idle no
0333/012 T00222 in-service/idle no
0333/013 T00223 in-service/idle no
0333/014 T00224 in-service/idle no


i can test call from from Avaya to BSS, and vice versa.
i just tuning in ip-codec-set. i think BSS can read only 1 codec.

many thanks Tata & Brekeke.

As a SIP proxy, BSS passes SDP what Avaya sent. so BSS doesn't care even if there are multiple codecs.