Server Edition Issue

[rsv23]

Dear Guys,

We have server edition and expansion system. Extension to extension calls is only working one way.

Site A - server edition
Sete B - Expansion system

Site A - is the server edition. Extensions setup to this system can call extensions number in site B
Site B - Expansion system can't call extension on site A. I can see from the status it got connected but the target extension in site A is not ringing.

Any idea?

 

[dwill02]

Can you pull a monitor trace of the issue and post it please?

Have you restarted the primary call server since adding the expansion unit to the solution?

Have you restarted the expansion unit since adding it to the solution?

 

[rsv23]

Hi Dwill02,

No, we did not restarted the primary yet but the expansion unit, we already restarted it.

Do you recommend restarting the primary server?

thanks

 

[dwill02]

No need to reboot the whole primary server, just find a maintenance window when you can log into :7070 and restart the service.

A monitor trace might highlight the issue without a restart of services though, since you can recreate the issue fairly easily. Log into the expansion unit with monitor and get a trace of an attempted call from the expansion to the primary

 

[rdoubrava]

I'm guessing firewall.
the talk path (voice) are UDP packets.

 

[dwill02]

what hardware do you have in site B's control unit?

Are all the extensions in question IP phones?

If not:
Is there a combo card(s)? Or maybe a VCM card in Site B control unit?

 

[rsv23]

Dear Dwill02,

Combocard/VCM Module
ATM4V2

It is using the connection type VCM instead RTP Relay. and also it is using the trunkline to connect to the extension to site A instead of SCN.

Yes, they are all in ip phone.

 

[dwill02]

and also it is using the trunkline to connect to the extension to site A instead of SCN." Can you elaborate on this for me? What are the outgoing line group ID's for the trunks you have built in Site B?

 

[dwill02]

Based on that information, there must be a shortcode conflict that's causing it to try to hit the trunk (Outgoing ID 10). Have you tried building a shortcode to force extension calls across the SCN? In the case of the monitor trace you sent-- create a system shortcode like this:

Shortcode: 1622
Feature: Dial
Tel Number: 1622
Line Group: 99999

If that works for this one extension, that will make some headway.

 

[derfloh]

Is the SCN status OK in SSA on both sides? If it would be so the short codes would be ignored. I guess since the system doesn't know the other side's users the best match will be a ?/. short code.

Need some help with IP Office?

https://www.fwilke.com/home

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[rsv23]

Thanks guys, all working fine now.

it was an issue with the shortcode to push SNC to use for internal calls.

 

[derfloh]

Internal numbers and SCN numbers should always be found before any short code is processed. I guess the SCN is not fully working.

Need some help with IP Office?

https://www.fwilke.com/home

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/