jermudgeon
IS-IT--Management
Hi all. Partial success story here:
I have an Option 11C that I've hooked up via a T1, TIE lines, to an Asterisk VOIP system. I've used some of the walkthroughs from this forum & other places on the web.
Using steering codes, calls work great in both directions, from Asterisk to the Nortel, and back. Love it. No problems.
Sample DCH messages:
DCH 4 IMSG SETUP blah blah
CALLING #:4460 NUM PLAN: E164
CALLED #:5411 NUM PLAN: E164
DCH 4 OMSG ALERT blah blah
DCH 4 OMSG CONNECT
DCH 4 IMSG CONN ACK
and upon hangup, the proper DISC/ NORMAL CALL CLEARING/RELEASE messages are generated.
Making a call that goes out over our T1 (COT setup) to the PSTN fails in this regard:
The call is completed, audio works, but the CONNECT message never is sent, so Asterisk thinks the call hasn't been answered, and hangs up after 5 minutes, which is the max ringtime I have it sent to.
Sample DCH messages:
DCH 4 IMSG SETUP
CALLING #:4460
CALLED #:9XXXXXXX (obscured)
DCH 4 OMSG CALLPROC
DCH 4 OMSG PROGRESS
PROGRESS: CALL IS NOT END TO END ISDN
And no connect message is generated.
Disconnect supervision works fine from either side in a call like this, a normal OMSG DISC or IMSG DISC.
Bad consequences:
1. Unless I set my call timeout to never from the Asterisk side, outbound calls get forcibly dropped
2. Call duration never gets logged to CDR in Asterisk (this is sort of OK, because I have the CDR from Nortel)
3. Any ACDs on the Option 11C that NCFW to to an "outside" line (i.e., over our PSTN trunks) just don't work at all from the Asterisk side. This is the worst and may be an unrelated problem, sadly.
I'm happy to post any configs, version numbers, etc. anyone can suggest. This has been a problem for about 6 months, and I could really use a solution.
Thanks to any and all,
Jeremy Austin
7 years Nortel Admin
5 years Asterisk
Nortel Meridian Option 11C (about 120 500's)
Asterisk VOIP (3 systems, 20 clients)
I have an Option 11C that I've hooked up via a T1, TIE lines, to an Asterisk VOIP system. I've used some of the walkthroughs from this forum & other places on the web.
Using steering codes, calls work great in both directions, from Asterisk to the Nortel, and back. Love it. No problems.
Sample DCH messages:
DCH 4 IMSG SETUP blah blah
CALLING #:4460 NUM PLAN: E164
CALLED #:5411 NUM PLAN: E164
DCH 4 OMSG ALERT blah blah
DCH 4 OMSG CONNECT
DCH 4 IMSG CONN ACK
and upon hangup, the proper DISC/ NORMAL CALL CLEARING/RELEASE messages are generated.
Making a call that goes out over our T1 (COT setup) to the PSTN fails in this regard:
The call is completed, audio works, but the CONNECT message never is sent, so Asterisk thinks the call hasn't been answered, and hangs up after 5 minutes, which is the max ringtime I have it sent to.
Sample DCH messages:
DCH 4 IMSG SETUP
CALLING #:4460
CALLED #:9XXXXXXX (obscured)
DCH 4 OMSG CALLPROC
DCH 4 OMSG PROGRESS
PROGRESS: CALL IS NOT END TO END ISDN
And no connect message is generated.
Disconnect supervision works fine from either side in a call like this, a normal OMSG DISC or IMSG DISC.
Bad consequences:
1. Unless I set my call timeout to never from the Asterisk side, outbound calls get forcibly dropped
2. Call duration never gets logged to CDR in Asterisk (this is sort of OK, because I have the CDR from Nortel)
3. Any ACDs on the Option 11C that NCFW to to an "outside" line (i.e., over our PSTN trunks) just don't work at all from the Asterisk side. This is the worst and may be an unrelated problem, sadly.
I'm happy to post any configs, version numbers, etc. anyone can suggest. This has been a problem for about 6 months, and I could really use a solution.
Thanks to any and all,
Jeremy Austin
7 years Nortel Admin
5 years Asterisk
Nortel Meridian Option 11C (about 120 500's)
Asterisk VOIP (3 systems, 20 clients)