- Joined
- Jul 20, 2011
- Messages
- 5
- Reaction score
- 0
Hi everyone!
I am new to 3cx and am having some issues getting bandwidth.com SIP Trunks working with 3cx. Outbound calls seem to work just fine, but inbound is where the problem occurs. Bandwidth.com doesn't use registration with it's trunks, so I assume that is where the problem lies. Even though I have "Require registration for" set to "Do not require," it isn't working.
A screenshot of my log is attached. You can see where I am getting the "Unidentified incoming call. Review INVITE and adjust source identification" error. I followed the 3CX FAQ on the topic, but that didn't seem to help.
Here is what I did:
Went to my bandwidth.com trunk,
went to "Source ID" tab
Under SIP Field, selected "Requested Line URI: User Part"
Under Variable, selected Custom Field, and entered My_Public_IP:5060
That didn't work.
So I deleted that, and tried it with Requested Line URI: Host Part (everything else was the same). It kinda worked. The call would come through, but the system would not recognize the DID, so I cant route the DIDs. They all route to where ever the main trunk is routed.
Anyone have any insight?
I am new to 3cx and am having some issues getting bandwidth.com SIP Trunks working with 3cx. Outbound calls seem to work just fine, but inbound is where the problem occurs. Bandwidth.com doesn't use registration with it's trunks, so I assume that is where the problem lies. Even though I have "Require registration for" set to "Do not require," it isn't working.
A screenshot of my log is attached. You can see where I am getting the "Unidentified incoming call. Review INVITE and adjust source identification" error. I followed the 3CX FAQ on the topic, but that didn't seem to help.
Here is what I did:
Went to my bandwidth.com trunk,
went to "Source ID" tab
Under SIP Field, selected "Requested Line URI: User Part"
Under Variable, selected Custom Field, and entered My_Public_IP:5060
That didn't work.
So I deleted that, and tried it with Requested Line URI: Host Part (everything else was the same). It kinda worked. The call would come through, but the system would not recognize the DID, so I cant route the DIDs. They all route to where ever the main trunk is routed.
Anyone have any insight?