Here is a tough one!
I've been a lurker for many years now but haven't come across this one yet.
In short: Calls originating from the local merlin have outbound caller id working fine, calls originating from the remote system, calling out through the legend, have caller ID showing up with just the area code. Yup, just the area code with no other trailing digits.
System Setup:
I have an R7 Merlin Legend with dual 100D PRI cards. Card "A" is connected to the LEC while card "B" is connected as a private LEGND-Network PRI to a linux based Asterisk system. Everything works great and calls can be originated to the LEC from both the local Legend and remote Asterisk.
Both systems talk to each other and CLID is passed both directions with both recognizing and able to route based on CLID.
Remote system connected to Card "B" is based on 4 digit extensions while the local LEGEND is 3 digit extension based. 4XXX is routed to the remote switch, over the Card "B" PRI via a UDP.
I've read a previous CLID post that spoke about 3 and 4 digit extensions between local and remote switches sometimes causing issues and have created a 3 digit extension on the remote switch with the same results, just the AREA CODE is passed to the outside called number.
All calls originating from the local legend have caller id working just fine.
Call progress from the remote switch is thus:
1. Dial is determined.
2. CLID of call is set to local LEGEND outbound CLID.
3. Call is handed to local LEGEND via pool 890
4. Local LEGEND receives call and routes out pool 70 to LEC
5. CLID appears as NXX.
The 23 lines on PRI "A" are assigned to the standard pool 70 while the "B" PRI lines are assigned to little Mr. 890.
I would really appreciate any troubleshooting tips / pointers / diagnostic next steps, etc... This has been wearing on me for the better part of 2 years now. I even added a 3rd PRI to the local LEGEND system with a different asterisk server configured completely different yet yielding the same results.
Thanks so much.
I've been a lurker for many years now but haven't come across this one yet.
In short: Calls originating from the local merlin have outbound caller id working fine, calls originating from the remote system, calling out through the legend, have caller ID showing up with just the area code. Yup, just the area code with no other trailing digits.
System Setup:
I have an R7 Merlin Legend with dual 100D PRI cards. Card "A" is connected to the LEC while card "B" is connected as a private LEGND-Network PRI to a linux based Asterisk system. Everything works great and calls can be originated to the LEC from both the local Legend and remote Asterisk.
Both systems talk to each other and CLID is passed both directions with both recognizing and able to route based on CLID.
Remote system connected to Card "B" is based on 4 digit extensions while the local LEGEND is 3 digit extension based. 4XXX is routed to the remote switch, over the Card "B" PRI via a UDP.
I've read a previous CLID post that spoke about 3 and 4 digit extensions between local and remote switches sometimes causing issues and have created a 3 digit extension on the remote switch with the same results, just the AREA CODE is passed to the outside called number.
All calls originating from the local legend have caller id working just fine.
Call progress from the remote switch is thus:
1. Dial is determined.
2. CLID of call is set to local LEGEND outbound CLID.
3. Call is handed to local LEGEND via pool 890
4. Local LEGEND receives call and routes out pool 70 to LEC
5. CLID appears as NXX.
The 23 lines on PRI "A" are assigned to the standard pool 70 while the "B" PRI lines are assigned to little Mr. 890.
I would really appreciate any troubleshooting tips / pointers / diagnostic next steps, etc... This has been wearing on me for the better part of 2 years now. I even added a 3rd PRI to the local LEGEND system with a different asterisk server configured completely different yet yielding the same results.
Thanks so much.