CustomerEndpoint Address telephone number not consistent

0

For past few days we are seeing inconsistency in telephone number value in 'CustomerEndpoint.Address' . Due to inconsistency in value identifying the user was difficult. Any reasons why this is happening and solution that can be implemented here?

Thanks

1回答
0
承認された回答

Hi Bala,

Can you provide an example of the inconsistency you are seeing?

profile pictureAWS
エキスパート
回答済み 6ヶ月前
  • When I call from my number +91 74XXXXXXXX ,for few times I see Customer endpoint adress is different telephone number like +161568623XX.

    Out of 5 calls it is showing exactly my number 1 or 2 times only. Few months back when I used connect , it used to show exact number I'm calling from.

  • The start of your phone number, +91 is the country code for India. +1 is the country code for US and surrounding territories.

    CustomerEndpoint will be a value of the number we receive from our telecom partners. A couple questions and areas to explore:

    1. Are you forwarding calls in from another provider to Connect? This could influence the number shown to our system.
    2. Are you sure you have correlated the correct call? You may be receiving actual calls from a US number.
    3. Your telecom carrier for your +91 number could forwarding your call to a US based number before creating an outbound leg to the Connect service. Connect would not have visibility into that leg.
  • Out of above areas ,I belive it could be reason (point 3) with telecom carrier making that outbound leg to connect +1 troll free number.

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ