SIP URI calls at "11101xxx221@toronto4.voip.ms" fail

Support zone
Post Reply
rybshik
Posts: 33
Joined: Mon Jun 08, 2009 2:20 am

SIP URI calls at "11101xxx221@toronto4.voip.ms" fail

Post by rybshik » Sat Sep 24, 2016 9:05 pm

I have a virtual VoIP.MS DID "11101xxx221" with Point of Presence "toronto4.voip.ms".
And I use "11101xxx221@toronto4.voip.ms" to receive incoming SIP URI calls.

SIP uri calls received at "11101xxx221@toronto4.voip.ms" from Sipsorcery do not go through. but It works well with other providers.
Last edited by rybshik on Mon Sep 26, 2016 8:59 pm, edited 1 time in total.

Aaron
Site Admin
Posts: 4652
Joined: Thu Jul 12, 2007 12:13 am

Re: SIP URI calls at "11101xxx221@toronto4.voip.ms" fail

Post by Aaron » Mon Sep 26, 2016 11:29 am

Can you provide a dialplan Console trace of the failing call? Info about the Console can be found here http://www.sipsorcery.com/mainsite/Help/Console.

rybshik
Posts: 33
Joined: Mon Jun 08, 2009 2:20 am

Re: SIP URI calls at "11101xxx221@toronto4.voip.ms" fail

Post by rybshik » Mon Sep 26, 2016 11:07 pm

Code: Select all

3.201.229.19:19678.
DialPlan 23:03:59:614 sip1(9500): Information response 100 Trying for sip:11101xxx221@toronto4.voip.ms.
DialPlan 23:03:59:630 sip1(9500): Response 503 Service Unavailable for sip:11101xxx221@toronto4.voip.ms.
DialPlan 23:03:59:630 sip1(9500): Call failed with a failure status of TemporarilyUnavailable and Couldn't connect the call.
DialPlan 23:03:59:645 sip1(9500): UAS call failed with a response status of 480 and Couldn't connect the call.
DialPlan 23:03:59:661 sip1(9500): Dialplan cleanup for rybshik1.
DialPlan 23:03:59:911 sip1(9500): Dial plan execution completed with normal clearing.
DialPlan 23:04:01:127 sip1(9500): Using dialplan default for In call to sip:Megafon.rybshik1@67.222.131.147;rinstance=DFXUGU.
NewCall 23:04:01:143 sip1(9500): Executing script dial plan for call to Megafon.rybshik1.
DialPlan 23:04:01:190 sip1(9500): Commencing Dial with: 11101xxx221@toronto4.voip.ms.
DialPlan 23:04:01:205 sip1(9500): Attempting to locate a provider for call leg: sip:11101xxx221@toronto4.voip.ms.
DialPlan 23:04:01:205 sip1(9500): ForkCall commencing call leg to sip:11101xxx221@toronto4.voip.ms.
DialPlan 23:04:01:205 sip1(9500): Switching to sip:11101xxx221@toronto4.voip.ms:5060 via udp:67.222.131.147:5060.
DialPlan 23:04:01:205 sip1(9500): SDP on UAC call had public IP not mangled, RTP socket 193.201.229.19:12162.
DialPlan 23:04:01:283 sip1(9500): Information response 100 Trying for sip:11101xxx221@toronto4.voip.ms.
DialPlan 23:04:01:283 sip1(9500): Response 503 Service Unavailable for sip:11101xxx221@toronto4.voip.ms.
DialPlan 23:04:01:283 sip1(9500): Call failed with a failure status of TemporarilyUnavailable and Couldn't connect the call.
DialPlan 23:04:01:283 sip1(9500): UAS call failed with a response status of 480 and Couldn't connect the call.
DialPlan 23:04:01:299 sip1(9500): Dialplan cleanup for rybshik1.
DialPlan 23:04:01:455 sip1(9500): Dial plan execution completed with normal clearing.

Aaron
Site Admin
Posts: 4652
Joined: Thu Jul 12, 2007 12:13 am

Re: SIP URI calls at "11101xxx221@toronto4.voip.ms" fail

Post by Aaron » Tue Sep 27, 2016 10:30 am

I suspect you need to use your voipms SIP provider account for the call instead of trying to place it anonymously.

Code: Select all

sys.DIal("11101xxx221@voipms") # Replace voipms with the name of your voip.ms SIP Provider entry.

rybshik
Posts: 33
Joined: Mon Jun 08, 2009 2:20 am

Re: SIP URI calls at "11101xxx221@toronto4.voip.ms" fail

Post by rybshik » Tue Sep 27, 2016 11:16 pm

Aaron wrote:I suspect you need to use your voipms SIP provider account for the call instead of trying to place it anonymously.
I want to pass/keep the CallerID of incoming calls. If I use my VoIP.ms account, it will force the account's CID.

And, why does anonymous forwarding at "11101xxx221@toronto4.voip.ms" work with other providers, but not Sipsorcery?

Aaron
Site Admin
Posts: 4652
Joined: Thu Jul 12, 2007 12:13 am

Re: SIP URI calls at "11101xxx221@toronto4.voip.ms" fail

Post by Aaron » Wed Sep 28, 2016 10:21 am

Where is the call you are forwarding originating from?

If it's coming from voipms as well there will likely be issues where the voipms server will think the From header is one of it's own accounts and try and authenticate it.

Post Reply