AWS Chime

[robert]

I have been attempting to connect to the AWS Chime "voice connector" to use strictly for outbound calling.

After quite a bit of frustration I have received a clue from AWS, but I am not smart enough to decipher the clue.


AWS: "We just got an update from the Service Team, they said that at right now you are so close, you just need to update the called and calling number to use E.164 format (i.e., add a '+' before the 1)"

[ERROR] - [xxx.xxx.xxx.xxx][sip:xxxxxxx@xxxxxxxxx.voiceconnector.chime.aws]: [INVITE] --> [sip:xxxxxxxxxxx@xxxxxxxxxxxx.voiceconnector.chime.aws;x-vine-id=5d4c5037-4636-485e-9946-7e0dxxxxc8f;call-id=PzsvKDdRLdthDzr4A3sgTxxxxScm4NewdTfxuQS8VrwK;sourceNumber=DCjaDwqxxxxZM] failed E.164 format verification

Any help will be appreciated.

 

[ad5ou]

Sounds like they expect your caller Id to be +12225551234 and outbound needs a prefix of +1 if dialing 10 digits or just the “+” if dialing 11 digits

 

[robert]

SOLVED: I finally figured this out, it was that I needed to have E.164 for both my dialing format as well as my outgoing caller id.

 

[marco114]

@robert
Sorry to bring up an old topic, how did you get the gateway to register? Mine never does. In the Amazon Chime Dashboard, I have my IP in the Allowed list, a username and password in there. It says FAIL_WAIT in the status.

On FusionPBX I have the gateway, username, password and proxy set the same as the gateway. expire 800, register = true, retry 30, context public, profile external, enabled=true

can you show how you set the dialing format and caller id

 

[robert]

no username or password, use the "Register False". See attached graphic.

Also for Chime, your "Outbound Caller ID Number" has to be +15555551212 if you don't have the +1, it wont go out.

I hope this helps.

 

[marco114]

thanks for the reply, I feel like I am close but still not connecting. any other tips in the dial plan?
just trouble shooting, i can't even connect using telnet to my chime endpoint over 5060, seems like aws is blocking me

edit: I can connect via telnet, so the connection is ok, but still won't make a call.

 

[marco114]

I am making progress, but getting "SIP/2.0 400 Source number is not valid E.164 or anonymous value".

{"voice_connector_id":"vn0p2nvhoewXXXXXXXXX","event_timestamp":"2021-10-28T14:42:42Z","aws_region":"us-east-1","call_id":"25dc141c-b2a0-123a-4db2-0a8fdd303743","sip_message":"SIP/2.0 400 Source number is not valid E.164 or anonymous value
Via: SIP/2.0/UDP 199.184.000.57:5080;received=199.184.000.57;rport=5080;branch=z9hG4bKjjK3teF404tcN
From: "JOHN SMITH" <sip:FreeSWITCH@vn0p2nvhoewXXXXXXXXX.voiceconnector.chime.aws>;tag=aUZr6jDrXU2eN
To: <sip:+1336688XXX@vn0p2nvhoewXXXXXXXXX.voiceconnector.chime.aws>;tag=y0r4B4HStND3N
Call-ID: 25dc141c-b2a0-123a-4db2-0a8fdd303743
CSeq: 43162289 INVITE
Content-Length: 0"}

My thinking is where it says "FreeSWITCH" is supposed to be the number, but how to I tell FusionPBX to put the number there?

FYI: I anonymized some of the info.

 

[marco114]

I figured it out. This added the phone number in the from instead of "FreeSWITCH'

In the gateway settings:

Caller ID In From = True
Sip CID Type = rpid

Note: You may need to restart freeswitch after doing this setting.