Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Caller ID shows leading 001

Status
Not open for further replies.
84Mike

84Mike

Technical User
Nov 8, 2005
518
US
I have an IP Office 8.1 using E.164...all inbound calls are showing a leading 001 on the caller-id screen...so 724-555-1212 shows as 0017245551212. How do I drop the 001 on the caller id?
 
Sort by date Sort by votes
Check you Line.
Prefix/National Prefix/International Prefix:
Any excessive input of 0's?

Kind regards

Gunnar

________________________________________

Oh, for fox sake!
 
Upvote 0 Downvote
Prefix shows nothing...
National prefix shows 0
International prefix shows 00
 
Upvote 0 Downvote
you prefixes look incorrect for the USA.
even so the symptoms would suggest to me that the problem is with the presentation form your line provider
system monitor should be able to confirm this.


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
 
Upvote 0 Downvote
The invite shows "From: <sip:+1724xxxxxxx@192.xxx.xxx.xxx;isup-oli=61>

But below that, I am seeing 001724xxxxxxx
 
Upvote 0 Downvote
Then tick the "Caller ID from From header" box in the SIP line setting :)

 
Upvote 0 Downvote
Tried that both checked and unchecked. Still looks the same on the phone.
 
Upvote 0 Downvote
Most likely the first 0 is your own "fault", that comes from your 0 in National Prefix.
01, that's the "+1724xxx" you see from the provider.

If you don't get them to remove it, you can strip it with a short code so it's possible to call back.



Kind regards

Gunnar

________________________________________

Oh, for fox sake!
 
Upvote 0 Downvote
I wanted to post an actual trace from Monitor, to see if anyone can help. Someone previously said it is the carrier adding the 001, I just want to be sure. Thanks!


CANCEL sip:+1412438xxxx@50.xxx.xxx.xxx:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK918a.790bcaf4.0
From: <sip:[highlight #FCE94F]+1724322xxxx[/highlight]@192.168.xxx.xxx;isup-oli=61>;tag=gK087a7776
Call-ID: 336077417_69374901@192.168.xxx.xxx
To: <sip:+1412438xxxx@67.231.xxx.xxx>
CSeq: 7369 CANCEL
Max-Forwards: 70
User-Agent: Bandwidth.com TRM (bw7.gold.13)
Content-Length: 0

10429328mS SIP Tx: UDP 50.xxx.xxx.xxx:5060 -> 216.82.224.202:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK918a.790bcaf4.0
From: <sip:+1724322xxxx@192.168.xxx.xxx;isup-oli=61>;tag=gK087a7776
To: <sip:+1412438xxxx@67.231.xxx.xxx>;tag=8f0ff0970e980404
Call-ID: 336077417_69374901@192.168.xxx.xxx
CSeq: 7369 CANCEL
Supported: timer
Server: IP Office 8.1 (43)
Content-Length: 0

10429330mS SIP Tx: UDP 50.xxx.xxx.xxx:5060 -> 216.82.224.202:5060
SIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK918a.790bcaf4.0
Via: SIP/2.0/UDP 67.231.xxx.xxx;branch=z9hG4bK918a.11ad5d92.0
Via: SIP/2.0/UDP 192.168.xxx.xxx:5060;branch=z9hG4bK08B10cb0e8225abcd95
Record-Route: <sip:216.82.224.202;lr;ftag=gK087a7776>
Record-Route: <sip:67.231.xxx.xxx;lr=on;ftag=gK087a7776>
From: <sip:+1724322xxxx@192.168.xxx.xxx;isup-oli=61>;tag=gK087a7776
To: <sip:+1412438xxxx@67.231.xxx.xxx>;tag=8f0ff0970e980404
Call-ID: 336077417_69374901@192.168.xxx.xxx
CSeq: 7369 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
Server: IP Office 8.1 (43)
Content-Length: 0

10429331mS CMLineRx: v=0
CMReleaseComp
Line: type=SIPLine 17 Call: lid=17 id=1035 in=1
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=[highlight #FCE94F]001724322xxxx[/highlight]@192.168.xxx.xxx
IE CMIEDeviceDetail (231) LOCALE=enu HW=15 VER=8 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1035 ipaddr=192.168.1.1 apps=0
Cause=16, Normal call clearing
10429331mS CMCallEvt: 17.1035.1 10 SIPTrunk Endpoint: StateChange: END=A CMCSRingBack->CMCSCompleted
10429331mS CMTARGET: 17.1035.1 10 SIPTrunk Endpoint: CancelTimer CMTCCoverageTimeout
10429333mS CMLOGGING: CALL:2013/10/2114:50,00:00:00,008,[highlight #FCE94F]001724322xxxx[/highlight]@192.168.xxx.xxx,I,1886,[highlight #FCE94F]001412438xxxx[/highlight],,,,0,,""n/a,0
10429333mS CD: CALL: 17.1035.1 BState=Ringing Cut=0 Music=0.0 Aend="Line 17" (0.0) Bend="J Doe(1886)" [J Doe(1886)] (0.0) CalledNum=1886 (J Doe) CallingNum=001724322xxxx@192.168.xxx.xxx () Internal=0 Time=8776 AState=Idle
10429333mS CD: CALL: 17.1035.1 Deleted
10429333mS CMCallEvt: 17.1035.1 -1 SIPTrunk Endpoint: StateChange: END=X CMCSCompleted->CMCSDelete
10429334mS CMCallEvt: 0.1036.0 -1 BaseEP: DELETE CMEndpoint f4f5b7b0 TOTAL NOW=2 CALL_LIST=0
10429335mS CMExtnEvt: J Doe: CALL LOST (CMCauseNormal)
10429335mS CMExtnEvt: J Doe: Extn(1886) [highlight #FCE94F]Calling Party Number(001724322xxxx@192.168.xxx.xxx[/highlight]) Type(CMNTypeUnknown)
10429336mS CMCallEvt: 259.1037.0 -1 J Doe.0: StateChange: END=X CMCSRinging->CMCSCompleted
10429336mS CMExtnEvt: v=3 State, new=PortRecoverDelay old=Ringing,0,0,J Doe
10429337mS CMExtnTx: v=1886, p1=0
CMReleaseComp
Line: type=IPLine 250 Call: lid=259 id=1037 in=0
Called[1886] Type=Default (100) Reason=CMDRdirect Calling[001724322xxxx@192.168.xxx.xxx] Type=Unknown Plan=Default
Cause=16, Normal call clearing
Timed: 21/10/13 14:50
 
Upvote 0 Downvote
I wanted to post an actual trace from Monitor, to see if anyone can help. Someone previously said it is the carrier adding the 001, I just want to be sure. Thanks!


CANCEL sip:+1412438xxxx@50.xxx.xxx.xxx:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK918a.790bcaf4.0
From: <sip:[highlight #FCE94F]+1724322xxxx[/highlight]@192.168.xxx.xxx;isup-oli=61>;tag=gK087a7776
Call-ID: 336077417_69374901@192.168.xxx.xxx
To: <sip:+1412438xxxx@67.231.xxx.xxx>
CSeq: 7369 CANCEL
Max-Forwards: 70
User-Agent: Bandwidth.com TRM (bw7.gold.13)
Content-Length: 0

10429328mS SIP Tx: UDP 50.xxx.xxx.xxx:5060 -> 216.82.224.202:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK918a.790bcaf4.0
From: <sip:+1724322xxxx@192.168.xxx.xxx;isup-oli=61>;tag=gK087a7776
To: <sip:+1412438xxxx@67.231.xxx.xxx>;tag=8f0ff0970e980404
Call-ID: 336077417_69374901@192.168.xxx.xxx
CSeq: 7369 CANCEL
Supported: timer
Server: IP Office 8.1 (43)
Content-Length: 0

10429330mS SIP Tx: UDP 50.xxx.xxx.xxx:5060 -> 216.82.224.202:5060
SIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK918a.790bcaf4.0
Via: SIP/2.0/UDP 67.231.xxx.xxx;branch=z9hG4bK918a.11ad5d92.0
Via: SIP/2.0/UDP 192.168.xxx.xxx:5060;branch=z9hG4bK08B10cb0e8225abcd95
Record-Route: <sip:216.82.224.202;lr;ftag=gK087a7776>
Record-Route: <sip:67.231.xxx.xxx;lr=on;ftag=gK087a7776>
From: <sip:+1724322xxxx@192.168.xxx.xxx;isup-oli=61>;tag=gK087a7776
To: <sip:+1412438xxxx@67.231.xxx.xxx>;tag=8f0ff0970e980404
Call-ID: 336077417_69374901@192.168.xxx.xxx
CSeq: 7369 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
Server: IP Office 8.1 (43)
Content-Length: 0

10429331mS CMLineRx: v=0
CMReleaseComp
Line: type=SIPLine 17 Call: lid=17 id=1035 in=1
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=[highlight #FCE94F]001724322xxxx[/highlight]@192.168.xxx.xxx
IE CMIEDeviceDetail (231) LOCALE=enu HW=15 VER=8 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1035 ipaddr=192.168.1.1 apps=0
Cause=16, Normal call clearing
10429331mS CMCallEvt: 17.1035.1 10 SIPTrunk Endpoint: StateChange: END=A CMCSRingBack->CMCSCompleted
10429331mS CMTARGET: 17.1035.1 10 SIPTrunk Endpoint: CancelTimer CMTCCoverageTimeout
10429333mS CMLOGGING: CALL:2013/10/2114:50,00:00:00,008,[highlight #FCE94F]001724322xxxx[/highlight]@192.168.xxx.xxx,I,1886,[highlight #FCE94F]001412438xxxx[/highlight],,,,0,,""n/a,0
10429333mS CD: CALL: 17.1035.1 BState=Ringing Cut=0 Music=0.0 Aend="Line 17" (0.0) Bend="J Doe(1886)" [J Doe(1886)] (0.0) CalledNum=1886 (J Doe) CallingNum=001724322xxxx@192.168.xxx.xxx () Internal=0 Time=8776 AState=Idle
10429333mS CD: CALL: 17.1035.1 Deleted
10429333mS CMCallEvt: 17.1035.1 -1 SIPTrunk Endpoint: StateChange: END=X CMCSCompleted->CMCSDelete
10429334mS CMCallEvt: 0.1036.0 -1 BaseEP: DELETE CMEndpoint f4f5b7b0 TOTAL NOW=2 CALL_LIST=0
10429335mS CMExtnEvt: J Doe: CALL LOST (CMCauseNormal)
10429335mS CMExtnEvt: J Doe: Extn(1886) [highlight #FCE94F]Calling Party Number(001724322xxxx@192.168.xxx.xxx[/highlight]) Type(CMNTypeUnknown)
10429336mS CMCallEvt: 259.1037.0 -1 J Doe.0: StateChange: END=X CMCSRinging->CMCSCompleted
10429336mS CMExtnEvt: v=3 State, new=PortRecoverDelay old=Ringing,0,0,J Doe
10429337mS CMExtnTx: v=1886, p1=0
CMReleaseComp
Line: type=IPLine 250 Call: lid=259 id=1037 in=0
Called[1886] Type=Default (100) Reason=CMDRdirect Calling[001724322xxxx@192.168.xxx.xxx] Type=Unknown Plan=Default
Cause=16, Normal call clearing
Timed: 21/10/13 14:50
 
Upvote 0 Downvote
The provider is sending it (the +), so that's what it displays, try removing your international prefix :)

 
Upvote 0 Downvote
Update:

I have removed both National and International prefix (just made them blank) and that got rid of the 00, only have a "1" in front of number now.
 
Upvote 0 Downvote
So after all, it was the usual suspect:)

Kind regards

Gunnar

________________________________________

Oh, for fox sake!
 
Upvote 0 Downvote
Again, they are sending the 1.... unless they stop sending the 1 the system will keep displaying it, it is after all the caller ID it's being presented with :)

 
Upvote 0 Downvote
Our SIP provider in the UK (Gamma) allows us to select the CLI format from 3 options:

Option 1 Canonical = +44113xxxxxxx - IP Office strips the + and inserts the international code (00) to display 0044113xxxxxxx

Option 2 National Number with leading 0= 0113xxxxxxx - IP Office recognises national code (0) and displays 0113xxxxxxx

Option 3 National Number without leading 0 = 113xxxxxxx - IP Office inserts national code (0) and displays 0113xxxxxxx



You need to speak to your provider and get them to present the correct format for your needs.



+++ Divide By Cucumber Error. Please Reinstall Universe And Reboot +++
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

GillockLaw
  • Locked
  • Question
Inbound PRI Caller ID signal 1
Replies
1
Views
759
TouchToneTommy
TouchToneTommy
G
  • Locked
  • Solved
Avaya IP Office + Asterisk: wrong outgoing caller ID on PRI 1
Replies
3
Views
407
guilty76
G
R3LzX
  • Locked
  • Question
Twilio and mobility caller id pass through has anyone done it?
Replies
0
Views
358
R3LzX
R3LzX
Jouik
  • Locked
  • Question
Incoming calls Caller ID Name not showing on SIP Phones although received in Monitor trace
Replies
1
Views
348
Mo. Abdullah
Mo. Abdullah
TN94z
  • Locked
  • Question
IP Office 11.1.3.1 with IP Flex - Sending caller ID
Replies
7
Views
1K
TN94z
TN94z

Part and Inventory Search

Sponsor

Back
Top