Need Help Avaya CM 6.3 H.323 Trunk with Ericsson MD110

[navid52]

Avaya CM S8700 6.3 H.323 Trunk with Ericsson MD110
HI Friends,
I configure H.323 ISDN IP trunk with Ericsson, but signaling group showing busy out bypass, channels status showing oos/FE-IDL, I tried ping Test to Ericsson that is OK
PLS any one send me Avaya cm configuration to verify pls.

Thanks,
Navid

 

[kyle555]

There's almost nothing to it. I've never had a problem getting a h323 sig group up. Sure, there's options and features to fight with but the basics are that you have an h323 sig group with near-end procr and far-end the node name of whatever you want to signal to on the other side.

Do you have other IP trunks and sets working OK?

The only thing on CM I can think of off hand that would prevent any IP trunk group from coming up is lack of DSPs. Like if you just spun up a CM in a lab with no gateway, or if you made the far end network region of that sig group unable to connect to any other network region with DSPs. Say something like you made it region 240 and if you display ip-network-region 240 that you have no connectivity to any other region. If CM can't get a DSP for a region, it won't allow registrations from IP sets or bring up IP trunks in that region.

 

[navid52]

Thanks kyle555,
No Trunks working before it’s 1st H.323 trunk in system, I attached CM configuration pls review it, it’s blame game start Ericsson throw to me that issue in Avaya, pls guide me how can I sure that CM is ok.
ange node-names ip Page 1 of 2
IP NODE NAMES
Name IP Address
ASBC 192.168.10.17
SBC 192.168.10.18
SM 192.168.10.8
aes 192.168.10.6
default 0.0.0.0
ericson 192.168.10.19
procr 192.168.10.4
procr6 ::

ng-group 10 Page 1 of 6
SIGNALING GROUP

Group Number: 10 Group Type: h.323
SBS? n Remote Office? n Max number of NCA TSC: 0
Q-SIP? n Max number of CA TSC: 0
IP Video? n Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 10 X-Mobility/Wireless Type: NONE
TSC Supplementary Service Protocol: a Network Call Transfer? n
T303 Timer(sec): 10
H.245 DTMF Signal Tone Duration(msec):
Near-end Node Name: procr Far-end Node Name: ericson
Near-end Listen Port: 1720 Far-end Listen Port: 1720
Far-end Network Region: 4
LRQ Required? n Calls Share IP Signaling Connection? n
RRQ Required? n H245 Control Addr On FACility? n
Bypass If IP Threshold Exceeded? n
H.235 Annex H Required? n
DTMF over IP: out-of-band Direct IP-IP Audio Connections? y
Link Loss Delay Timer(sec): 90 IP Audio Hairpinning? n
Enable Layer 3 Test? n Interworking Message: PROGress
H.323 Station Outgoing Direct Media? n DCP/Analog Bearer Capability: 3.1kHz

Page 2 of 6
LIMIT SIGNALING GROUP USAGE

Enable on the main Processor(s)? y

Enable on Survivable Processors (ESS and LSP): all


Page 3 of 6
ADMINISTERED NCA TSC ASSIGNMENT

Service/Feature: As-needed Inactivity Time-out (min):
TSC Local Adj. Mach.
Index Ext. Enabled Established Dest. Digits Appl. Name ID
1: n
2: n
3: n
4: n
5: n
6: n
7: n
TRUNK GROUP

Group Number: 10 Group Type: isdn CDR Reports: y
Group Name: Ericson H.323 trunks COR: 3 TN: 1 TAC: 6
Direction: two-way Outgoing Display? n Carrier Medium: H.323
Dial Access? y Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n
Member Assignment Method: auto
Signaling Group: 10
Number of Members: 30

Page 2 of 21
Group Type: isdn

TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Charge Advice: none
Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc


Digital Loss Group: 18
Incoming Calling Number - Delete: Insert: Format:

Disconnect Supervision - In? y Out? y
Answer Supervision Timeout: 0
CONNECT Reliable When Call Leaves ISDN? n
XOIP Treatment: auto Delay Call Setup When Accessed Via IGAR? n


Page 3 of 21
TRUNK FEATURES
ACA Assignment? n Measured: none
Internal Alert? n Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: y Send Calling Number: y
Used for DCS? n Send EMU Visitor CPN? n
Suppress # Outpulsing? n Format: private
UUI IE Treatment: service-provider

Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Send Connected Number: y
Network Call Redirection: none Hold/Unhold Notifications? n
Send UUI IE? y Modify Tandem Calling Number: no
Send UCID? n
Send Codeset 6/7 LAI IE? y


Show ANSWERED BY on Display? y

Page 4 of 21
QSIG TRUNK GROUP OPTIONS

SBS? n


QSIG Value-Added? n

Page 5 of 21
TRUNK GROUP
Administered Members (min/max): 1/30
GROUP MEMBER ASSIGNMENTS Total Administered Members: 30

Port Name Night
1: T00001 Ericson H.
2: T00002 Ericson H.


ip-codec-set 1
Page 1 of 2
IP CODEC SET
Codec Set: 1
Audio Silence Frames Packet
Codec Suppression Per Pkt Size(ms)
1: G.711A n 2 20
2: G.711MU n 2 20
3:
4:
5:
6:
7:
Media Encryption

 

[kyle555]

yeah, you're fine. Like I said, there's nothing to it. Someone's gotta break out the wireshark and see who's not playing nice with who and go from there. You can display alarms, errors, events on that sig and trunk, maybe something'll turn up on your side, but just about all it could be would be DSP availability to that far end network region.

 

[navid52]

Thanks dear,
kyle555 pls guide me to get trace the call via wire shark, Ericsson thrown to me, now I have to proof them that Avaya side is ok.
pls help.

 

[kyle555]

You don't have root on CM and so you can't wireshark from it's server on your own.

Many alternatives are available. Get your LAN guy to port mirror the CM to another network port and sniff it with a laptop.

You could tell the Ericsson guy that you spoke to somebody on the Internet and you know what's up and he should quit complaining and send you a wireshark trace

Or, if you're on system platform, from dom0, you can "tshark -i avpublic host 1.1.1.1" presuming the far end signaling IP is 1.1.1.1 and that'll print packets to your terminal. if you add a -w /home/cust/myericssonpbxisbroken.pcap then you can take the packet capture off later with winscp or something.

You shouldn't be running wireshark on live PBXs and if you forget it and leave it running, you might really screw things up. Nothing wrong with getting the LAN guy to mirror a port besides it being a little slower to get done.

But even before you wireshark, you can display alarms and errors on that signaling group, you can test it in CM and get all sorts of error and failure codes that can tell you what's going on without resorting to looking at raw packets - like if they're actually talking or not, you'll get something to clue you in on that. Your Ericsson guy won't care, but at least that way you can feel like a tough guy when you send him that wireshark trace later.