Has anyone had any issues with 10.5.0 not displaying caller-id in call quality stats, nor is it sending it to the PBX. I did not have this issue with 10.3.1 on the 7100. Scenario is this Carrier interface is SIP, customer side is PRI. Sip Stack shows caller-id information in the from field and in the Call-Id context has the gui-id listed. I ran through the release notes on 10.5.0 and did not see anything indicating change to the display of caller-id.
Thanks in advance for any insight.
After looking through the complete debug output, we were able to determine that we needed to remove the "p-asserted-identity-required" option from the trust-domain command. Below is how we made this change.
voice trunk T02 type sip
no trust-domain p-asserted-identity-required
Since the unit was not receiving P-asserted-identity, it was not trusting or forwarding the CID that was being received.
Run "debug isdn l2-formatted" and see if the caller id info is being sent on the PRI.
It's possible the "isdn name-delivery" will need to be changed on the PRI interface.
Here is the output of the Debug, from what I am seeing the Presentation is being screened somewhere alogn the way. But my provider is just saying that since it is in the From Header it's not them. Any guidance on where to let them know where to look or what I might need to do differently is much appreciated.
24 ISDN.L2_FMT PRI 1 IE - 1C FACILITY Len=14
09:53:04.925 ISDN.L2_FMT PRI 1 Calling Name: not available
09:53:04.925 ISDN.L2_FMT PRI 1 IE - 6C CALLING PARTY # Len=2
09:53:04.925 ISDN.L2_FMT PRI 1 00 Numb. Type:UNKNOWN
09:53:04.926 ISDN.L2_FMT PRI 1 Numb. Plan:UNKNOWN
09:53:04.926 ISDN.L2_FMT PRI 1 C3 Presentation:UNAVAILABLE
09:53:04.926 ISDN.L2_FMT PRI 1 Screening:NTWK PROVIDED
09:53:04.926 ISDN.L2_FMT PRI 1 Ph.#
09:53:04.927 ISDN.L2_FMT PRI 1 IE - 70 CALLED PARTY # Len=8
09:53:04.927 ISDN.L2_FMT PRI 1 80 Numb. Type:UNKNOWN
09:53:04.927 ISDN.L2_FMT PRI 1 Numb. Plan:UNKNOWN
INT PRI 1 Config Verbose:
interface pri 1
isdn switch-type ni2
isdn name-delivery setup
isdn ringing-signal suppress
no calling-party override
calling-party presentation allowed
calling-party screening auto
no calling-party number
calling-party name-facility-timeout 2
connect t1 0/2 tdm-group 1
digits-transferred 7 no-prefix
role network b-channel-restarts disable
no isdn alert disable pi-8
no isdn connect enable pi-2
no isdn setup enable pi-1
no isdn setup enable pi-3
isdn setup enable redirecting-number
isdn pi-location public
no isdn supplementary-service tbct
no isdn supplementary-service tbct notify-controller
no isdn supplementary-service tbct transfer-counters
isdn supplementary-service tbct active-transfers 100
isdn supplementary-service tbct transfer-rate 10
isdn supplementary-service tbct d-channel-id auto
snmp trap link-status
Please send the output from “debug sip stack messages” as well.
This will show what the provider is sending.
I have scrubbed vital content prior to posting Let me know if you need more:
17:45:37.218 SIP.STACK MSG INVITE sip:803NXXXXXX@xx.xxx.xx.xx:5060;transport=UDP SIP/2.0
17:45:37.218 SIP.STACK MSG Via: SIP/2.0/UDP xx.xxx.xx.xx:5060;branch=z9hG4bK5brkfk20b0a1mkcb43o0.1
17:45:37.219 SIP.STACK MSG From: "XXX Comm XXX"<sip:706NXX1234@xx.xxx.xx.xx;user=phone>;tag=SDjdpff01-482818994-1356648305356-
17:45:37.219 SIP.STACK MSG To: "803NXXXXXX 803NXXXXXX"<sip:803NXXXXXX@voip.net;user=phone>
17:45:37.220 SIP.STACK MSG Call-ID: SDjdpff01-51d4feb763029f715a64dbee799ebef3-06a53o3
17:45:37.220 SIP.STACK MSG CSeq: 793061735 INVITE
17:45:37.221 SIP.STACK MSG Contact: <sip:706NXX1234@xx.xxx.xx.xx:5060;transport=udp>
17:45:37.222 SIP.STACK MSG Supported: 100rel
17:45:37.223 SIP.STACK MSG Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
17:45:37.223 SIP.STACK MSG Accept: application/media_control+xml,application/sdp,multipart/mixed
17:45:37.224 SIP.STACK MSG Max-Forwards: 9
17:45:37.225 SIP.STACK MSG Content-Type: application/sdp
17:45:37.225 SIP.STACK MSG Content-Length: 255
17:45:37.226 SIP.STACK MSG
17:45:37.227 SIP.STACK MSG v=0
17:45:37.227 SIP.STACK MSG o=BroadWorks 2207701 1 IN IP4 xx.xxx.xx.xx
17:45:37.228 SIP.STACK MSG s=-
17:45:37.228 SIP.STACK MSG c=IN IP4 xx.xxx.xx.xx
17:45:37.229 SIP.STACK MSG t=0 0
17:45:37.229 SIP.STACK MSG a=sendrecv
17:45:37.230 SIP.STACK MSG m=audio 63376 RTP/AVP 0 101
17:45:37.230 SIP.STACK MSG a=rtpmap:0 PCMU/8000
The provider is sending caller id name.
Try changing isdn name-delivery to display, proceeding, or setup
All three say presentation unavailable, screening network. This did not happen on code previous to R10.5 with this provider, however because I needed to put in custom tagging I had to use the HMR rules to modify the P-Asserted Identity headers changing the user number to a trunk number so it is also the first time we have deployed using the R10.5 code. However this is also a brand new config for this provider they are providing the service using a type of trunk group they have not previously used. I went through the release notes and did see an issue where if the caller-id info was being sent as E.164 there was an issue but it also had a work around of setting the international setting to abbreviated which I tried with no change.
Thanks for posting. This may be an issue we need to work through a regular Technical Support ticket. Please call us at 888-423-8726 to open a ticket. We will likely need to see your complete configuration and the following debug commands, all run at the same time, for a given test call.
debug sip stack message
debug voice verbose
debug isdn L2-formatted
Once we have found the problem, we can post it on the forum.
THanks for the reply. I have tested with version 10.3.1 on a different device connected to a standard trunk with the provider, and it works. I am in the process of updating to R10.5.0 on the test device to see if it breaks, if it does I know it is related to the 10.5 code, if it doesnt then I know it's related to the new configuration of the provider port. If it fails when upgrading the code to 10.5 then I will collect all the logs you have stated and open a case, however this is turning into a major issue for the customer so if it work on 10.3 but not 10.5 I will down grade thier code after collecting the logs.
I have tested the Caller-ID on a test system running the Netvanta 7100 10.5 code and caller ID displays normally. There is however one major difference between the test and the deployed system and that is the test system is doing SIP to SIP where the deployed system is doing SIP to TDM.