Ok certainly, below is the monitor trace with the ISDN L3 Transmit and Receive filter enabled.
What is happening is my number, 2504848484, is calling 4032791631 which is twinned to the external number 4036800910.
The call to the desk phone before it is twinned successfully shows my number and...
Have tried that already earlier today without success.
The caller ID number always passes through without issue but the number does not.
The only part that is infuriating me is that the customer had a similar setup with an Adtran TA908 as the SIP/PRI gateway and apparently it worked without...
So actually perhaps there is some confusion.
After digging into it a little bit I think I may have jumped the gun.
Since the Avaya IP Office is configured with a PRI trunk to the Adtran TA904 there are no SIP URI settings.
I have a monitor trace I can post as well.
UNICODE-UTF8
enu...
Well I work for a company that is the SIP provider and we provided the Adtran as the SIP/PRI gateway.
We do allow the passing of the originator caller ID, we do not modify or restrict caller ID and leave that to the upstream carriers.
I apologize because I am not familiar with Avaya IP office...
Having an issue here with an Avaya IP Office PBX that is running through an Adtran TA904e as a SIP/PRI gateway.
Essentially, caller ID is working normally for inbound and outbound calls, but when twinning the caller ID name is either that of the user who has twinned their extension or of the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.