[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.

Post Reply 
Thread Rating:
  • 1 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Outgoing calls fail - Forbidden
Author Message
TotalNet Offline
Junior Member

Posts: 3
Joined: Feb 2020
Reputation: 0
Post: #1
Outgoing calls fail - Forbidden
My business is closed due to the national lockdown here in NZ and I'm trying to get my business phones working from my home office and it's not going so well. Any help for a Yealink newcomer is gratefully appreciated!

Essentially, I believe my ISP/VoIP provider is blocking my outgoing calls from off-network, however, they have said no at 1st level support so I need some ammo to get through to level 4 ideally.

I have a W60B with 1 W56H and a T41S with the DD10 DECT adapter.

The line is registered and receives incoming calls on that line. When I attempt an outgoing call if fails quickly with "Forbidden".

There are other accounts registered on the W60B with a cloud PBX and my home ISP/VoIP working perfectly. I have set up the T41S for this account without the DECT adapter and get the same failure.

At the business office I use a CISCO ATA (SPA112) for this line and have used its settings for the registration on the W60B, with the intention of replacing it with the Yealink setup soon. This ATA device does not work from my home office either.

I have setup a syslog server to trace the call process and can attach here but the key entries I see are:

- a new call is established (call staus update [0]==>[2])
- a packet is successfully sent to the SIP server and a reply received
- a couple more exchanges of packets with the SIP server
- call status changes to 19 (call status update [2]==>[19])
- the call is released <<RELEASE-REASON>> (0xe2)

There is no SIP proxy involved, the connection is UDP only.

I'm sure there are many reasons behind a "forbidden" call failure (it's often as much about what's not in the log) so please let me know if there's another area I can look at, perhaps it's my network setup (NAT?) which is why the ATA I brought home doesn't work either.

Here's a highlight of the syslog output (phone# replace with NN):

DCX <5+notice> 632.873.481:TX[0] HS 2 --> T[55597] {CC-INFO}  P_IT(240)
DCX <5+notice> 632.873.625:  <<Calling Party Number>>  (0x6c)
DCX <5+notice> 632.873.769: Number type:  
DCX <5+notice> 632.873.910: Numbering plan: ISDN/telephony plan
DCX <5+notice> 632.874.055: Presentation indicator: , Screening indicator: User-provided, not screened
DCX <5+notice> 632.875.883: Number: 0xNN ("N") 0xNN ("N") 0xNN ("N") 0xNN ("N") 0xNN ("N") 0xNN ("N") 0xNN ("N") 0xNN ("N") 0xNN ("N")  
DCX <5+notice> 632.876.071:  <<Calling Party Name>>  (0x6d)
DCX <5+notice> 632.876.227: "NNNNNNNNN
DCX <5+notice> 632.876.373:  <<Call information>>  (0x7e)
DCX <5+notice> 632.876.518: Call ID:  0x0  
DCX <5+notice> 632.879.676:
DCX <5+notice> 632.879.872:
APP <5+notice> [SIP] SIP_C2S_CALL_NEW_OUTGOING, lid:0, cid:32795,callmask:0x00000000,callee:NNNNNNNNN
CAL <5+notice> [000] call status update [0]==>[2]
DLG <5+notice> [000] Sending Packet :to dest= msglen  = 929
DLG <5+notice> [000] End of Sending Packet :msglen  = 929
NET <5+notice> [000] ===>>>> UDP socket send 929 bytes
NET <5+notice> [255] <<<<=== UDP socket read 246 bytes  
DLG <5+notice> [000] Data Received :from src= msglen  = 246
DLG <5+notice> [000] End of Data Received :msglen  = 246
NET <5+notice> [255] <<<<=== UDP socket read 277 bytes  
DLG <5+notice> [000] Data Received :from src= msglen  = 277
DLG <5+notice> [000] End of Data Received :msglen  = 277
DLG <5+notice> [000] Sending Packet :to dest= msglen  = 318
DLG <5+notice> [000] End of Sending Packet :msglen  = 318
NET <5+notice> [000] ===>>>> UDP socket send 318 bytes
CAL <5+notice> [000] call status update [2]==>[19]
SS7 <5+notice> 633.047.590:SS7_ReqRelExt instance=0x1003000e, reason=0x75,msg:(null) rel_msg_len=0
SS7 <5+notice> 633.048.034:service_SS7_ReqRel inst=0x1003000e,Reason=117,Call Id:0
APPC<5+notice> 633.048.266:appmedia_CallObjMediaStop inst:0xf,ChannelID:0
APPC<5+notice> 633.048.453:CallObjMediaSet inst:0xf,state:1
APPC<5+notice> 633.050.701:appcall_ReleaseCall CallId:0, Reason:0x75, RelMsgLen:0, CallIns:0xf, Hs:2
DCX <5+notice> 633.261.418:
DCX <5+notice> 633.261.635:FTMLP_ID/0,3,8,0x0,0x0,0,<0>
DCX <5+notice> 633.291.416:
DCX <5+notice> 633.291.633:FTMLP_ID/0,3,7,0x4,0x0,4,<0>
DCX <5+notice> 633.331.383:
DCX <5+notice> 633.331.590:FTMLP_ID/0,3,7,0x5,0x0,5,<0>
DCX <5+notice> 633.351.965:
DCX <5+notice> 633.352.222:FTMLP_ID/0,3,7,0x6,0x0,6,<0>
DCX <5+notice> 633.352.379:
DCX <5+notice> 633.352.528:RX[0] HS 2 <-- T(55645) {CC-RELEASE-COM} [HS-2]  P_IT(140)
DCX <5+notice> 633.352.676:  <<RELEASE-REASON>>  (0xe2)
DCX <5+notice> 633.352.819: Normal

Whether making a call or not I also get the occasional DESV<3+error > 792.450.786:get_ip failed ret= -1

I would port my phone number to the cloud PBX but I get an unbeatable package with unlimited free national and mobile calls on 2 lines Sad

Cheers for any assistance

(This post was last modified: 03-31-2020 05:45 AM by TotalNet.)
03-31-2020 05:40 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 

Messages In This Thread
Outgoing calls fail - Forbidden - TotalNet - 03-31-2020 05:40 AM

Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  IP Phone sometimes does not receive calls from my own mobile phone. willywonka 4 1,369 05-27-2020 01:12 AM
Last Post: willywonka
Question T23G Recovery Mode Upload Fail stan0ne 6 5,012 05-26-2020 02:52 PM
Last Post: Lewis-H
  Push xml with firmware 84 - 403 forbidden always nSolvePaul 2 1,150 03-10-2020 12:47 PM
Last Post: roelvanmeer
  Some calls missing from Paced Calls History ipandco 3 1,296 01-21-2020 03:30 PM
Last Post: ipandco
  Record all calls to USB dcfindlay 1 1,030 12-02-2019 08:39 AM
Last Post: Paz_Yealink
  Is there a way to make the "calls are forwarded on no answer TO VOICEMAIL" go away? justingoldberg 1 1,433 10-14-2019 06:56 AM
Last Post: Garry_Yealink
  SIP-T21P_E2 refusing calls issue Alvaro 1 1,030 09-10-2019 02:36 PM
Last Post: Alvaro
  Missed Calls not shown on T48G Germain 1 1,117 08-22-2019 07:54 AM
Last Post: Babylonia
  How to make Outgoing AIP URI calls? KNERD 3 1,730 05-08-2019 02:53 PM
Last Post: complex1
  Transfer calls T26P agalindo 2 2,196 09-17-2018 09:10 AM
Last Post: agalindo

Forum Jump:

User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication