I saw this question asked before but have not seen any replies that address the issue.
My system consists of four Option 11C's (25.30) connected using ITG cards that emulate tie lines. It has a coordinated dial plan. Here is what is happening:
SCENARIO A (good)
-----------------
1. Outside caller calls main number (PRI circuit).
2. Call is answered by auto-attendant (AA).
3. Caller dials four-digit internal DN via AA. This
DN is located at the same location as the AA.
4. AA transfers caller to DN (blind transfer).
5. DN display first shows AA ACD pilot number upon
initial ringing but display quickly changes to
show the external caller's CLID while it continues to
ring and after being answered.
SCENARIO B (bad)
----------------
1. Outside caller calls main number.
2. Call is answered by AA.
3. Caller dials four-digit internal DN via AA. This
DN is at another location.
4. AA blind transfers caller to DN. Since the DN is
at another location, it is carried over the tie
connection via CDP.
5. DN display shows AA ACD pilot number. DN display
is never updated to show the external caller's CLID,
even after being answered, put on hold, and retrieved.
SCENARIO C (good)
-----------------
1. Outside caller calls main number.
2. Call is answered by AA.
3. Caller dials 0 to transfer to live attendant.
4. Live attendant transfers caller to DN at another
location.
5. DN at other location shows the external caller's CLID.
Why does scenario B happen? What is the difference between the auto-attendant doing a blind transfer (using 2616 ports) and a live attendant doing a blind transfer using a 2250 console? Both calls in scenarios B & C end up being carried over the TIE connection.
For what it is worth, the auto-attendant is not Meridian Mail. It is Centigram/Mitel Mail/Baypoint (many name changes) and it has an integration package that makes it emulate a 2616 style phone. After it blind transfers the call, it definitely releases the line because it becomes available for another incoming call.
I'm unaware of any settings on the tie route because scenario C shows that CLID is being sent with the call. I thought that the CLS settings for the AA DN's may be wrong but scenario A disproves that.
The only thing that makes sense is that the call progess information is not getting updated over the TIE route, since the initial call setup is from the AA DN and this is what first gets sent via the TIE route. When the AA "hangs up", the TIE route does not update the display of the still ringing DN at the other location.
My system consists of four Option 11C's (25.30) connected using ITG cards that emulate tie lines. It has a coordinated dial plan. Here is what is happening:
SCENARIO A (good)
-----------------
1. Outside caller calls main number (PRI circuit).
2. Call is answered by auto-attendant (AA).
3. Caller dials four-digit internal DN via AA. This
DN is located at the same location as the AA.
4. AA transfers caller to DN (blind transfer).
5. DN display first shows AA ACD pilot number upon
initial ringing but display quickly changes to
show the external caller's CLID while it continues to
ring and after being answered.
SCENARIO B (bad)
----------------
1. Outside caller calls main number.
2. Call is answered by AA.
3. Caller dials four-digit internal DN via AA. This
DN is at another location.
4. AA blind transfers caller to DN. Since the DN is
at another location, it is carried over the tie
connection via CDP.
5. DN display shows AA ACD pilot number. DN display
is never updated to show the external caller's CLID,
even after being answered, put on hold, and retrieved.
SCENARIO C (good)
-----------------
1. Outside caller calls main number.
2. Call is answered by AA.
3. Caller dials 0 to transfer to live attendant.
4. Live attendant transfers caller to DN at another
location.
5. DN at other location shows the external caller's CLID.
Why does scenario B happen? What is the difference between the auto-attendant doing a blind transfer (using 2616 ports) and a live attendant doing a blind transfer using a 2250 console? Both calls in scenarios B & C end up being carried over the TIE connection.
For what it is worth, the auto-attendant is not Meridian Mail. It is Centigram/Mitel Mail/Baypoint (many name changes) and it has an integration package that makes it emulate a 2616 style phone. After it blind transfers the call, it definitely releases the line because it becomes available for another incoming call.
I'm unaware of any settings on the tie route because scenario C shows that CLID is being sent with the call. I thought that the CLS settings for the AA DN's may be wrong but scenario A disproves that.
The only thing that makes sense is that the call progess information is not getting updated over the TIE route, since the initial call setup is from the AA DN and this is what first gets sent via the TIE route. When the AA "hangs up", the TIE route does not update the display of the still ringing DN at the other location.
