You need either full detail logs for SIP subscriber from the maintenance GUI of the STMI, or configure a monitor session on the data switch so you can get a wireshark trace, see if the phone even registers.
Cha-zand optload does not check if you "have any SIP subscriber registered and working", it builds the ISDN options table used for some connections, historically ISDN but now also S0PP. You shouldn't make a cha-zandptload without first making a dis-zandpttbl; because the cha-zand will default the table and if this customer has any non standard configuration, then you just killed it. The dis-zand gives you the ability to restore it if needed.
Maybe you meant make a reg-zand to check for cha-zand, was not clear. But don't run the cha-zand without first making a dis.
If you configure a monitor session on the data switch against the STMI port, or install Wireshark on the PC with the softclient, what does the lan capture tell you is happening? SIP subscriber only needs to know its station number and registration IP address to work, unless you configure security/digest authentication. So you should see a register attempt and then a response from the STMI.
plokijuh mentions the opttbl, which if you have never had any SIP subscribers, or done anything with ISDN BRI, is likely to not be initialised. Make a dis-zandpttbl; to check current config. If it's empty, it will need a cha-zandptload like plokijuh mentions, because for SBCSU S0PP SIP stations, the ISDN tables are used for protocol conversion from SIP. After the optload you can make a dis-zandpttbl; again to see the difference.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.