01-13-2021 06:51 AM
I am having an issue that I wanted to put out there to see if anyone in the community has experienced something similar and may know the answer.
I am making an outbound call from our internal infrastructure via a Cisco CUBE to a provider. The trunk is a Registration based trunk so we receive a challenge from our INVITE for SIP Digest authentication (and go through all the normal steps) but it eventually bombs with a 487 Request terminated from the provider.
Based on the attached screenshot from translator-X (in my estimations) the called endpoint (provider side) should be responding after the 100 TRYING with a 180 RINGING but is not. The provider however says that the timeout is due to too long inactivity due to us not sending them a response - but cannot tell us what response they are expecting.
Solved! Go to Solution.
01-25-2021 07:54 AM
For anyone else experiencing this or a similar issue it ends up that the provider did not support Clip No Screening/calling line identification presentation (which means you cannot present any number you want as CLID) so were rejecting the call(s).
01-25-2021 07:54 AM
For anyone else experiencing this or a similar issue it ends up that the provider did not support Clip No Screening/calling line identification presentation (which means you cannot present any number you want as CLID) so were rejecting the call(s).
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide