LODR

[jschnarkey]

Hello,
I have a situation where I need to route calls from my 4K V7 to my Cisco call manager.
I would like users to dial normally, 9-XXX-XXX-XXXX but I would like it to send 8-XXX-XXX-XXXX to my cisco call manager.

I have built the Richt and ldat and I believe the magic would happen in the LODR.
Here is my LODR which is not doing the job,

DIS-LODR:3;
H500: AMO LODR STARTED
+-------------------------------------------------------+
| ODR POSITION CMD PARAMETER |
+--------+----------------------------------------------+
| 3 | 1 OUTPULSE 8 |
| | 2 ECHOALL |
| | 3 NPI UNKNOWN |
| | 4 TON UNKNOWN |
| | 5 END |
+--------+----------------------------------------------+
Any suggestions? And not sending an 8 is not a suggestion. The Call manager needs to route to the correct gateway via the 8.
I am already doing this in my Unify OSV but the 4K needs this also now.

Jake.

 

[Moriendi]

A sip trace would have been useful to see what was in the invite but I would assume you are sending the 9 after the 8, because you've used ECHOALL

If your LDPLN is 9-XXX-XXX-XXXX then swap the ECHOALL for
ECHO,2
ECHO,3
ECHO,4

The "9" is field 1 so you don't want to send that.

In any case, whatever your LDPLN is, by using ECHOALL you will be sending the 9.

By setting NPI/TON to UNKNOWN you won't be sending the leading + in front of the digits (which I guess is what you want, because your digit string starts with an 8).

 

[jschnarkey]

Thanks Moriendi.
I'll see if I can see what the call man is seeing. You suggestion though did not work.
I'm very close, this I know.

 

[jschnarkey]

So, if my LDPLN is 9-W-541-XXX-XXXX
Which field is 1, 2, 3 etc?

 

[jschnarkey]

Well alright. Call Manager is sending back 'unallocated number'
This is good news since I now see the number as Call Manager sees it.
8-541-541-951

I'm getting the area code twice. This should be an easy fix.

 

[jschnarkey]

Thank you Moriendi.
You gave me the clues I needed. Calls are now working. I send an 8 plus number to call manager. Call manager changes the calling search space and changes the 8 to a 9 and routes it out the proper gateway. All working perfect now.
And the winning LODR =

DIS-LODR:3;
H500: AMO LODR STARTED
+-------------------------------------------------------+
| ODR POSITION CMD PARAMETER |
+--------+----------------------------------------------+
| 3 | 1 OUTPULSE 8 |
| | 2 ECHO 2 |
| | 3 ECHOALL |
| | 4 NPI UNKNOWN |
| | 5 TON UNKNOWN |
| | 6 END |
+--------+----------------------------------------------+

 

[Moriendi]

The LODR references the LDPLN fields which are separated by the -, so with an LDPLN of 9-W-541-XXX-XXXX I would use an echo of fields 3,4,5. Field 1 is the 9 and field 2 is the W.

So using

ADD-LODR:101,,,,OUTPULSE,8;
ADD-LODR:101,,,,ECHO,3;
ADD-LODR:101,,,,ECHO,4;
ADD-LODR:101,,,,ECHO,5;
ADD-LODR:101,,,,NPI,UNKNOWN ,UNKNOWN ;
ADD-LODR:101,,,,END;


and dialling 9 541 123 4567 gives

                Called Party Number
                  Number
                    Type of Number                  Unknown
                    Numbering Plan ID               Unknown
                    Number
                      Digits                          85411234567

Originally with just the echoall it would have sent the 8, then because you use echoall but have not yet used anything in the dialled string, echoall will start from the beginning and send everything dialled.

               Called Party Number
                  Number
                    Type of Number                  Unknown
                    Numbering Plan ID               Unknown
                    Number
                      Digits                          895411234567

Your current config is definitely wrong. Using echo,2 when 2 is a W is a nonsense so it sends the 541 (this is why you got the 541 twice with the echo,2 echo,3). It can't send the W so it's sending the next field. I don't know if this is working as designed, or a bug, and it's possible it might stop working like that after a software update. I definitely would not rely on it always behaving like that.

I would correct your config to echo,3,4,5 or echo,3 and echoall. 3,4,5 would be the way I would do it but either will work.

 

[jschnarkey]

Sounds good.
Since I'm going to send all traffic from this campus out through that Cisco gateway I'll need to cover local, long distance, 911 and toll free. So I'll take what you have told me and work it from there.
I have local working now properly and am detailing out the rest to program the lprof's with the new source group and lrte's. Test the heck out of it and then bulk edit the campus with the new source group.

Thanks Moriendi. I appreciate the assist for sure. I will adjust to start my echo at 3.