0

Cannot make call to specific number

Carlo van Dongen

September 27, 2017 10:17

None

Follow

Hi,

 

I have a strange problem, from this morning I cannot make calls to 1 specific number.

== Using SIP RTP Audio CoS mark 5
-- Executing [06512XXXXX@DLPN_DialPlan219:1] YsWalkContext("PJSIP/219-000065bf", "blacklist-outbound,06512XXXXX,1,219,outbound") in new stack
-- Executing [06512XXXXX@DLPN_DialPlan219:2] NoOp("PJSIP/219-000065bf", "No Pinset") in new stack
-- Executing [06512XXXXX@DLPN_DialPlan219:3] Set("PJSIP/219-000065bf", "ORGINEXTEN=06512XXXXX") in new stack
-- Executing [06512XXXXX@DLPN_DialPlan219:4] Set("PJSIP/219-000065bf", "ORGINROUTE=Lijn7") in new stack
-- Executing [06512XXXXX@DLPN_DialPlan219:5] Set("PJSIP/219-000065bf", "ORGINCONTEXT=DLPN_DialPlan219") in new stack
-- Executing [06512XXXXX@DLPN_DialPlan219:6] Set("PJSIP/219-000065bf", "MRMEMORYHUNT=no") in new stack
-- Executing [06512XXXXX@DLPN_DialPlan219:7] GetNextOutRouter("PJSIP/219-000065bf", "Lijn7,06512XXXXX") in new stack
-- Executing [06512XXXXX@DLPN_DialPlan219:8] Goto("PJSIP/219-000065bf", "a1") in new stack
-- Goto (DLPN_DialPlan219,06512XXXXX,11)

 

There is nothing in the blacklist of the PBX and it is from all extensions.

Someone who know what happend?

 

Regards

Carlo

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  Carlo van Dongen September 28, 2017 13:59

  Even getting more strange, today everything is working fine again.

• 0
  
  Larry Neblett October 03, 2017 13:23

  The syslog is simply showing the steps that it is taking to validate the call's ability to be sent. I do not believe that it is indicating that anything is blacklisted, but rather checking to be certain that it was not. 

   

  To truly understand, it would have been helpful to get more details such as if there was a message or recording that indicated something or if it simply timed out. I am guessing that there was some type of indication to the call. Also, a wireshark (pcap) capture is usually more informative about SIP related call issues. If nothing changed in your setup, then it may have been a provider issue. 

• 0
  
  Carlo van Dongen October 03, 2017 13:42

  It looks like a provider issue, the call was to short for recording and we don't have wireshark running 24/7, lateron the call was made without any problem.