Adtran
Help
The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
kenny70
New Contributor
‎09-10-2021 01:05 PM

TA 908e 3rd Gen Configuration

Jump to solution

Using the TA 908e with Sky Voice SIP trunks to a PRI handoff. Inbound working fine. Can not make an outbound call. Call is being rejected due to No Caller ID being sent.

The PBX is sending a Caller ID number. Not sure where or how to configure the TA908e to pass Caller ID. 

Attached is the capture of a failed call to 815-735-8925.

Any guidance would be appreciated.

 

 Thanks

0 Kudos
Reply
1 Solution

Accepted Solutions
geo
Adtran Team
‎09-13-2021 12:03 PM

Re: TA 908e 3rd Gen Configuration

Jump to solution

Hello Kenny,

 

Thanks for posting to the forum.  Normally you do not have to make changes to pass the CID on a PRI to SIP call, but not every deployment and piece of equipment is alike.  I see that there is some information in the SIP FROM: header which is pulled from the ISDN Setup message:

From: <sip:ATISIPTrunks2.22787.service:5060;transport=UDP>

It looks like the PRI setup message is not in the debug.  If you provide the entire call, I can make a suggestion for you. Also, this is a straight outbound PRI to SIP call right?  Not a call forward scenario?

 

Thanks!

Geoff

 

 

View solution in original post

0 Kudos
Reply
1 Reply
geo
Adtran Team
‎09-13-2021 12:03 PM

Re: TA 908e 3rd Gen Configuration

Jump to solution

Hello Kenny,

 

Thanks for posting to the forum.  Normally you do not have to make changes to pass the CID on a PRI to SIP call, but not every deployment and piece of equipment is alike.  I see that there is some information in the SIP FROM: header which is pulled from the ISDN Setup message:

From: <sip:ATISIPTrunks2.22787.service:5060;transport=UDP>

It looks like the PRI setup message is not in the debug.  If you provide the entire call, I can make a suggestion for you. Also, this is a straight outbound PRI to SIP call right?  Not a call forward scenario?

 

Thanks!

Geoff

 

 

0 Kudos
Reply