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 Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ESA CLID and VO

Status
Not open for further replies.
bignose21

bignose21

Programmer
Jul 4, 2003
2,227
GB
I have set up ESA for a CS1000E and SMG the calls at the CS100E go out of the Local PRI and the Calls at the SMG go out of a PRI on the SMG. As well as 999/112 calls which go to the PSTN they also have 3333 which is an on site first aid numer.

I have got this working ok at the main site but at the SMG I get no CLID. The way I route calls at the SMG is:

ERL 450 prepends 8830 route calls to RLI which locally terminates an adds 6 (AC2) in AC2 I have SPNs 8830999/8830112/88309112 which all route to the PSTN (striping the relevant digits), and 88303333 which terminates locally to an EXTN. All give me no CLID. I have a Static ELIN set aginst my ERL.

If instead in the ERL I route the calls to an RLI that strips 4 and insert 999 and goes to PSTN (does not work for 3333 because its needs to go to an extn), I see the Static ELIN.

Also another question in an ESA feture presentation I have seen it shows the Virtual Office users Loggin on and Transfering their ERL details, when an emergency call is placed they do not log out but use the right ERL details to terminate correctly. My sets drop back to the Host CS (a problem with the SMG phones).

I do not have the Subnet package, and do not have an external Discovery manager. I do Have the ESA/VO/Enhanced VO packages.
 
Sort by date Sort by votes
A few things to check:

In LD 20 PRT a CLIDVER and see what the call server thinks it should send. Below is an example of CLIDVER. The first uses [!]C[/!]LID TABLE, the second uses the [!]D[/!]EFAULT DFCL and the third uses the [!]E[/!]LIN CLID:

Code: 
   DN    KEY       TN       ERL   CTYP          CLID        ROUTE     CALLED#
------- ------ ----------- ----- ------- ------------------ ----- ----------------
   1101        252 0 00 01    10     911 [!]C[/!]          5551101 I 911              911
                                     311 [!]C[/!]          5551101 I 311              311
                                     112 [!]C[/!]          5551101 I 911              112

   6125 00 SCR 096 0 00 25    12     911 [!]D[/!]          9991234 I 911              911
                                     311 [!]D[/!]          9991234 I 311              311
                                     112 [!]D[/!]          9991234 I 911              112

   6131 00 SCR 096 0 00 07    14     911 [!]E[/!]          5556509 I 911              911
                                     311 [!]E[/!]          5556509 I 911              311
                                     112 [!]E[/!]          5556509 I 911              112

Also since you have no LIS, all the IP Sets will have hard coded ERLs and then they will be considered to be at their HOME location. When at the HOME location, ESA will use CLID table ESA entries if they are present. Make sure ALL of them are blank in the CLID tables:

Code: 
  ESA_HLCL [!]<blank>[/!]
  ESA_INHN [!]NO[/!]
  ESA_APDN [!]NO[/!]

My guess is you have something in the CLID ESA that is confusing the call server.

--
Fletch

Nortel Emergency Services PLM

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcast
 
Upvote 0 Downvote
For your second question regarding ESA VO Routing or ESA redirect.

If the call server recognises the ERL and knows about it, then it will route. If it doesn't recognise the ERL, then it will force a redirect to the original login. All call servers have to have knowledge of all ERLS to route.

Are you using all Phase 2 IP phones or a mix of Phase 2 and Phase 0/1? Only Phase 2 phones get and report the location 'cookie' to the call server. so a Phase 0/1 set registering with a VO session has no previous knowledge of it''s prior location.


--
Fletch

Nortel Emergency Services PLM

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcast
 
Upvote 0 Downvote
I'll have a look at the CLID stuff tomorrow when I get to work.

The VO problem: All my sets are new 1140E's with the lastest firmware on. The problem I have is a set that is at the SMG, registers alright to the main office in normal mode and can dial out following ERL routing. If I VO to another DN on the same main office and dial an ESA number the set drops back to the SMG CS, this has no trunks because the MGC's are all registered at the MO.
 
Upvote 0 Downvote
This *may* be a bug since you do not have LIS on. When you do a VO the set is put in a needs update state (confirm-able by looking in LD 117 and running LOCRPT ALL)

Since it is in this state, the call server may not be sure of the location causing the set to redirect (which goes to it's S1 address or the SMG).

I have a CR in that corrects the issue of hard coded ERL values being put into a needs update state. (this is not seen with a LIS which is the 'normal' for IP sets)

To me it sounds like you have stumbled across another interaction. If you do open a ticket on this, have your vendor reference:

CR Q01940919 - VO logged in IPset phone location unknown even though ERL is statically defined

Thanks

--
Fletch

Nortel Emergency Services PLM

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcast
 
Upvote 0 Downvote
In LD117 I get:

=> locrpt all
No IP phones found in RLM table

=>

 
Upvote 0 Downvote
Thats odd. You should see somethign like this:

Code: 
|           | Prime |        |     |                     |                        |     |     |      Location      |MAN ND |
|     TN    |  DN   |  Type  |State|        HWID         |      Signaling IP      | ERL | ECL |    Description     |UPD UPD|
|-----------+-------+--------+-----+---------------------+------------------------+-----+-----+--------------------+---+---|
|104 0 10 10|   6474|1230    |REG  |180019e1e70902662a   |192.168.1.124:5000      |   11|    0|BLDG 14 - Room 206  |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|
|96  0 0  18|   6218|2210    |REG  |3000907a06d9d56612   |192.168.1.91:5000       |  750|    0|WRLS CONFIRM LOC    |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|
|96  0 0  8 |   6201|2004P2  |REG  |18001bbaf494626602   |192.168.1.117:5000      |   14|    0|BLDG 11 - Room 623  |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|
|96  0 0  14|   6101|2001P2  |REG  |180019e1e5e1546602   |192.168.1.118:5000      |   13|    0|BLDG 14 - Room 413  |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|
|96  0 0  20|   6220|2210    |REG  |3000907a0571376612   |192.168.1.90:5000       |  750|    0|WRLS CONFIRM LOC    |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|
|96  0 1  1 |   9911|1150    |REG  |1800159bfea4de6627   |192.168.1.113:5000      |   12|    0|BLDG 14 - Room 312  |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|
|96  0 0  16|   6116|2004P1  |REG  |18000ae40507966600   |192.168.1.105:5000      |   14|    0|BLDG 11 - Room 415  |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|
|96  0 0  15|   6133|2002P2  |REG  |18001bbafae61c6602   |192.168.13.102:5000     |   11|    0|BLDG 10 - Room 206  |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|
|96  0 0  5 |   6111|2002P2  |REG  |18001bbafae6206602   |192.168.1.120:5000      |   14|    0|BLDG 14 - Room 622  |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|
|96  0 0  4 |   6100|1140    |REG  |18001b252f52c36625   |192.168.1.104:5000      |    1|    0|BLDG 14 - Room 205  |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|

--
Fletch

Nortel Emergency Services PLM

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcast
 
Upvote 0 Downvote
Sorry about that doing some reloading of the sets system still in the lab. I do have sets showing here is one example:

| Prime | | | | | | | Location |MAN ND |
| TN | DN | Type |State| HWID | Signaling IP | ERL | ECL | Description |UPD UPD|
|-----------+-------+--------+-----+---------------------+------------------------+-----+-----+--------------------+---+---|
|160 0 0 0 | 198000|1140 |REG |18002267cdb00e6625 |10.85.1.150:5000 | 450| 0|ROBIN RIGG |YES|NO


 
Upvote 0 Downvote
Now do a VO on that set and tell me what the ND UPD column says. Thats the 'Needs Update' state of the phone. Also interested if the set says "Location Unknown" on the display.

I heard back that the fix for the problem I mentioned before has been included in 6.00, and I am expecting a patch for 5.00 and 5.50 this week.

--
Fletch

Nortel Emergency Services PLM

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcast
 
Upvote 0 Downvote
Before:

160 0 0 5 | 198005|1140 |REG |18002267cdb01a6625 |10.85.250.51:5000 | 450| 0|ROBIN RIGG |YES|NO


After VO Login:

160 0 0 31| 198039|1140 |REG |18002267cdb01a6625 |10.85.250.51:5000 | 0| 0|UNKNOWN |NO |YES



"Phone Location Unknown" is displayed on the set.
 
Upvote 0 Downvote
Cheers mate. Sorry for this next bit its long winded but try to give you the full picture.

Back to my CLID issue. What I have is a 1000E and and SMG.

I have setup Basic ESA for 999/112 which go to PSTN and 3333 (First aid) which goes to a local First aider for the site originating the call. The Main office works ok I can add the OSN and the CLI as a Static ELIN on the ERL (no manipulation just RLI sending it to PSTN), also 3333 works ok routed to a local set.

At the SMG I have added an ERL, which I only have one but will be adding more on different sites. Therefore I need a way to get 999/112 calls to go out of the SMGs PRI and 3333 to go to the SMGs First Aider.

I have achieved this by adding 72 on the ERL and sending it to an RLI, the RLI adds 6 (AC2) and locally terminates the call. SPNs 72999/72112 route to RLIs pointing to the PSTN and DMI del 2, 723333 routes to an RLI that locally terminates and DMI of del 6 and add the First Aid DN. All this works ok and also picks up the OSN from the ERL, but the Static ERL ELIN is not sent out as CLID, tried Dynamic ELIN it is assigned to the set but again did not send CLI to the PSTN (You can call the set back on the dynamic ELIN no.). I have set all the ESA prompts in the CLID HLCL x and other 2 to No.

After a bit more testing found the only CLID it pays attention to is the one normal CLI assigned to the set. So the call is no longer recognised as ESA after going through the extra translation.

It does accept the static ELIN on the ERL if I change the RLI on the ERL to route straight to PSTN, but I can't do this because of 3333.
 
Upvote 0 Downvote
The problem you are experiencing is that the static or Dynamic ELIN is only applicable if you out a trunk. If you locally terminate, the ERLSITE and ERLLOC descriptors are set, but the call never leaves the PBX, therefore no need to waste an ELIN and map to the set. It is already dial-able internally. ELINs are designed for EXTERNAL callback mapping where they cannot dial a non-did directly for example.

--
Fletch

Nortel Emergency Services PLM

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcast
 
Upvote 0 Downvote
So my best bet is to use the normal DDI numbers for all sets that have DDI and set a seperate DDI to always send the security DDI number for all sets without DDI. The CLI is blocked in the network so only the Emergency services should get this CLI to return calls, and as the OSN part works the serurity will have the info if they recieve a call from the PSAP.

Unless you know another way I can config my ESA for this to take care of my internal and external ESA's.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

umts
  • Locked
  • Question
How should I get started and what should I know? 2
Replies
9
Views
1K
umts
umts
krtcomm1
  • Locked
  • Question
CLID on tandem calls outbound to PSTN when calls are forwarded externally
Replies
6
Views
577
krtcomm1
krtcomm1
Emara
  • Locked
  • Question
when dialing the access code and th
Replies
1
Views
490
Firebird Scrambler
Firebird Scrambler
lexer
  • Locked
  • Question
Meridian 11c and asterisk interconnection using PRI
Replies
7
Views
816
RS528
RS528
teckopen
  • Locked
  • Question
what is different between CLID and CLIP ?
Replies
1
Views
410
Firebird Scrambler
Firebird Scrambler

Part and Inventory Search

Sponsor

Back
Top