› VitalPBX Community Support › General Discussion › Inbound issue pjsip – Outbound is fine › Reply To: RE: Inbound issue pjsip – Outbound is fine
-
- August 17, 2019 at 1:46 am
Still not working. Here is what I did
1) I deleted all trunks except the one term.skyetel.com
2) I changed the port to 5060
3) I added the match IP addresses
(See image attached)
I have DID 678-345-1700 from Skyetel pointed to ext 102
Ext 102 is on a Yealink T29G.
I made sure the port in the T29G is 5062
When I dial the 678-345-1700 I get the voice mail for ext 102. If I change the destination to my cell phone using custom destination it works. That tells me the DID is reaching the server. I just can’t figure why it won’t ring the yealink and goes straight to voice mail
When I try to dial the DID linked to the yealink, this is what the log says . . .
[2019-08-16 21:39:25] ERROR[15472]: res_pjsip.c:3533 ast_sip_create_dialog_uac: Endpoint ‘102’: Could not create dialog to invalid URI ‘102’. Is endpoint registered and reachable?
[2019-08-16 21:39:25] ERROR[15472]: chan_pjsip.c:2509 request: Failed to create outgoing session to endpoint ‘102’
[2019-08-16 21:39:25] WARNING[11872][C-00000060]: app_dial.c:2578 dial_exec_full: Unable to create channel of type ‘PJSIP’ (cause 3 – No route to destination)
[2019-08-16 21:39:25] ERROR[3387]: res_pjsip.c:3533 ast_sip_create_dialog_uac: Endpoint ‘102-2’: Could not create dialog to invalid URI ‘102-2’. Is endpoint registered and reachable?
[2019-08-16 21:39:25] ERROR[3387]: chan_pjsip.c:2509 request: Failed to create outgoing session to endpoint ‘102-2’
[2019-08-16 21:39:25] WARNING[11872][C-00000060]: app_dial.c:2578 dial_exec_full: Unable to create channel of type ‘PJSIP’ (cause 3 – No route to destination)The issue is why the yealink is not ringing, instead of going straight to VM
BTW – I can make outbound calls (using voip innovations as my termination) with no issues
0