01-19-2020 07:25 PM
Hi everyone,
I have a problem with incoming call on our cucm systems. when we received incoming call from external number phone (*such as mobile phone number), the ip phone screen is not get the caller-id or an unknown number appears on ip phone screen.
telco confirmed that they already sent the caller-id on their side and when they try some test with phone analog, the caller-id is appear as mobile phone normally.
we tried check the log on our VG on port Voice-port and the log is shown that the caller-id received but the ip phone still unknown number.
the route map protocol is like this :
PSTN - FO - MODEM ZTE - FXO - VG - MGCP - SIP PHONE
here is the log on our VG voice-port 0/1/0
Jan 14 02:39:21.553: [0/1/0] get_fxo_caller_id:Caller ID received. Message type=4 length=25 checksum=6F
023992: Jan 14 02:39:21.553: [0/1/0] Caller ID String 04 16 30 31 31 34 30 39 33 37 2B 36 32 38 39 36 34 36 38 35 33 32 37 31 6F
023993: Jan 14 02:39:21.554: [0/1/0] get_fxo_caller_id calling num=+6289646853271 calling name= calling time=01/14 09:37
023994: Jan 14 02:39:21.555: fxols_callerid_done: call being answered
01-19-2020 10:58 PM
Please check these three things in your FXO port configuration,
1) CPTONE set to your exact country code
2) "Caller ID enabled" command configured in that port
3) Caller id ring alert is greater than or equal to your Telco configured rings.
01-19-2020 11:30 PM
Hi Aswin,
here is the configuration of the voice-port
voice-port 0/1/0
supervisory disconnect dualtone mid-call
supervisory custom-cptone fxo
no battery-reversal
timeouts call-disconnect 3
timeouts wait-release 3
timing hookflash-out 50
timing guard-out 1000
caller-id enable
following your suggest
1) CPTONE set to your exact country code
- i tried to changed the cptone same as our country indonesia. so, i changed the cptone to cptone id. but it still not solved.
2) "Caller ID enabled" command configured in that port
-"caller ID enabled" already
3) Caller id ring alert is greater than or equal to your Telco configured rings.
- i tried changing the ring signal from 1 to 4 sequential, it also nothing happen.
anybody have an idea to fix this problem?
01-20-2020 12:10 AM
Then please try "Caller ID alerting line-reversal" concept in your FXO port to trigger the reading of caller id when it receives.
01-20-2020 12:24 AM
01-20-2020 02:39 AM
Yes please try "caller-id alerting dsp-pre-alloc" as this is FXO line.
01-22-2020 07:01 PM
Hi Aswin,
I had try that command but it still not fix the problem.
currently i got the log information from VG like this
05290260.000 |09:37:17.722 |SdlSig |MGCPNotify |wait |MGCPInit(1,100,170,1) |MGCPHandler(1,100,171,1) |1,100,171,1.87404^*^* |[R:N-H:0,N:1,L:0,V:0,Z:0,D:0] aaln/S0/SU1/0@KKUEA-VGM-RTR01 - portNum= 0 NTFY 24696755 Observed event=14 pkg=128 optStr="",+6289646853271,""
05290261.000 |09:37:17.722 |SdlSig |MGCPNotify |wait |MGCPManager(1,100,168,1) |MGCPInit(1,100,170,1) |1,100,171,1.87404^*^* |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] aaln/S0/SU1/0@KKUEA-VGM-RTR01 - portNum= 0 NTFY 24696755 Observed event=14 pkg=128 optStr="",+6289646853271,""
05290262.000 |09:37:17.723 |SdlSig |MGCPNotify |restart0 |MGCPTrunkD(1,100,163,15) |MGCPManager(1,100,168,1) |1,100,171,1.87404^*^aaln/S0/SU1@KKUEA-VGM-RTR01 |[R:N-H:0,N:1,L:0,V:0,Z:0,D:0] aaln/S0/SU1/0@KKUEA-VGM-RTR01 - portNum= 0 NTFY 24696755 Observed event=14 pkg=128 optStr="",+6289646853271,""
05290262.001 |09:37:17.723 |AppInfo | MGCPTrunkD::processCallerId - Invalid caller_id (number)= ""
05290263.000 |09:37:17.723 |SdlSig |DmPidReq |initialized |DeviceManager(1,100,208,1) |Da(1,100,214,1) |1,100,171,1.87403^*^aaln/S0/SU1@KKUEA-VGM-RTR01 |[T:N-H:0,N:0,L:0,V:0,Z:0,D:0] Cepn=1e393f94-efbf-d1f7-0fd1-9c878476a3fe Id=3848318784
05290264.000 |09:37:17.723 |SdlSig |MGCPNotifyRes |wait
MGCPTrunkD::processCallerId - Invalid caller_id (number)= ""
does anyone know what that's mean?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide