Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Thread Tools Search this Thread Display Modes
Old 06-17-2021, 07:24 AM
rime rime is offline
Join Date: Dec 2011
Posts: 66
rime has 10 reputation points
Post ISDN PRI: "Redirecting Number" in SETUP for EC500 call

The telephone service provider has inserted an ISDN<->SIP converter between the MM710B and the public telephone network at one of our customer's sites. Since then, calls which tandem through the Avaya Media Gateway (typically EC500) have their outgoing leg disconnected by the public network. The service provider says that we should either include a calling party number from the site's DDI range or include the "Redirecting Number" IE in the outgoing Setup message. I have activated SA8052 and SA8146 but do not see the "Redirecting Number" IE. Thanks in advance for some ideas on this issue.
Reply With Quote
Old 06-17-2021, 11:43 AM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Join Date: Sep 2010
Location: New York
Posts: 510
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points

Try enabling SA8983 (replace CPN when calls forwarded off-net). A new field on p2 of the ISDN trunk group will appear called "CPN to Send for Redirected Calls". When this field is set to "calling", the CPN of the originating caller is sent on forwarded/redirected calls. The customer's service provider is disallowing this. When this field is set to "redirected", the CPN of the station performing the off-net forward is sent as administered in the public numbering table. Use "redirected" in this case. The mobile device will not receive the originating CPN, but at least the call will complete.

This Special Application SA8983 modifies the calling party number for outgoing ISDN trunk calls that are the result of either call forwarding to an external number or the EC500 feature. With this feature active, the calling party number for these calls will be that of the call forwarding or EC500 station rather than that of the call originator. This feature works for both station-to-station and for incoming trunk calls to the call forwarding or EC500 station. All types of call forwarding–unconditional, busy/don’t answer, and enhanced call forwarding–are supported.
Meridian IT - Senior Engineer
Reply With Quote
Old 06-18-2021, 02:01 AM
rime rime is offline
Join Date: Dec 2011
Posts: 66
rime has 10 reputation points
Check Mark SA8983 effect on EC500 call: it does the job!

Thanks, much appreciated! it is a partial solution but yes, the call is no longer rejected by the public telephone network. Instead of the original calling party number (which would be ideal), the DDI of the EC500 user is sent as calling party number to the mobile phone receiving the call, which normally is the EC500 user's mobile phone. The mobile phone user can guess that it must be an external call because the own DDI or the own name is displayed on the mobile phone.
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 06:01 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.