Should be Answer B; Bearer-cap 0x8090A2 is already speech. Dialed nr starting 011 seems to me not an international number. Source; https://www.cisco.com/c/en/us/support/docs/voice/h323/14006-h323-isdn-callfailure.html
yeap, I'm going to B also. From eliminating other answers... bearer-cap as speech is already there as you said (0x8090A2)... no need for transcoder or changing switch-type as we got "normal call clearing" on disconnect cause, So probably we got "wrong number dialer from ITSP", then removing 011 will do the work to correct digits to pstn
From answers i would ignore A,C,D
A is not suiting, is already speach: 0x8090A2 Speech
https://www.cisco.com/c/en/us/support/docs/voice/h323/14006-h323-isdn-callfailure.html
C is not required, IDSN Debug is not showing codec issues on given cause codes
D is about Configuring the Switch Type, which i do not see as an issue, when focusing on given cause codes
suspecious is 0x929F, which indicates issues in other related searches to signaled called number
I checked on our customer in USA, we send it with leading 011 + plan:unknown
I assume it is provider depending, but with plan:international it might be necessary stripping 011
I am no so sure if it is B or C. If you see the stamps between the PROGRESS msg and the DISCONNECT msg, they are 17:43:21 and 17:43:46, so 25 seconds in difference doing ringing the called-phone in one side, and getting ringback the calling-phone in the other side. After 25 seconds, the caller-phone hangs-on, furthermore I do not see a problem of call routing or some unallocated number or stuff like that, just a normal call clearing, is really the problem the "011" (even when the hanging-on side was the GW, no the CO)?, if it were the "011" issue, then it wouldn't have ringing and ringbacking for 25 seconds. I am very confused.
By the way, indeed, A. and D. are absolutely discarded.
let us to consider the caller as the callref 0x12BE, and the called as the callref 0x92BE, and the caller was who hanged up after 25 seconds hearing ringback. If the called-side was who answered the call, It could has appeared the CONNECTED message, and then a DISCONNECT from the calling side for some issue of resources. In order of that, it seem that there was not any failed call, then may be I would be a bit more agree with B than C.
Another think to suspect is that PROGRESS, if it is tunneling a SIP message in a B2BUA configuration in the Gateway, is is similar a 183 Session in Progress (early media). There we do not know whats is happening in the caller side phone, if he is receiving ringback or just silence. Is the caller just hear silence, nothing, he might hang up impatiently. The same stuff if it is interworking H.323 with ISDN abut early media, we do not know. Whit the information provided by the question, it seems there is not failed call. And the solution would be a best practice, no such a fix, removing the "011", it is other reason I would be a bit more agree with B than C.
A quick debug isdn q931 helps determine the issue:
A normal call will have:
Bearer Capability i = 0x8090A2
A failed call wil have the following:
Bearer Capability i = 0x8890
https://it-learn.io/2014/05/01/sip-devices-unable-to-stablish-pstn-calls/
If 011 is sent out we should get fast busy right ? Then why the question is not mentioning that but just say the call is failed ? So Answer A could be right
Its B . You do not need 011 in front when call type is set to International
upvoted 1 times
...
...
This section is not available anymore. Please use the main Exam Page.350-801 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
remmie_78
Highly Voted 1 year, 10 months agoCollabhunter
1 year, 10 months agotimmyz
1 year, 8 months agotimmyz
1 year, 8 months agoVG224
1 year, 6 months agoDaKenjee
Most Recent 5 months agoSal007
5 months, 3 weeks agoSal007
5 months, 3 weeks ago[Removed]
11 months, 1 week ago[Removed]
11 months, 1 week ago[Removed]
11 months agonuno_paulo
1 year, 4 months agoBhaiKyare
1 year, 8 months agoVG224
1 year, 6 months ago