You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
asterisk phone server with name piasterisk is configured to run on UDP 5063 and TCP 5064
A sipsorcery softphone tries to reach "sip:301@piasterisk"
301 is reachable by dialplan and another registered softphone using TCP 5064
Question 1:
Is there a possibility to specify the destinations communication params other than using the URI extension like the following
"sip:301@piasterisk"; // uses default udp 5060
"sip:301@piasterisk:5063"; // uses udp 5063
Question 2:
Is there a possibility to specify the destinations communication params other than using the URI extension like the following
"sip:301@piasterisk;transport=tcp";
"sip:301@piasterisk:5064;transport=tcp"
The thought behind:
Trying to reach sip:301@piasterisk using the UDP 5063 connection also when 301 is registered via TCP 5064
Or maybe is this not a valid scenario ??
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi everybody
May someone give me a hint for this?
My testenvironment:
Question 1:
Is there a possibility to specify the destinations communication params other than using the URI extension like the following
Question 2:
Is there a possibility to specify the destinations communication params other than using the URI extension like the following
The thought behind:
Trying to reach sip:301@piasterisk using the UDP 5063 connection also when 301 is registered via TCP 5064
Or maybe is this not a valid scenario ??
Beta Was this translation helpful? Give feedback.
All reactions