Polycom phone unable to call ONT sip phone in 7060

[taych]

Hi,

I have recently installed a NV7060 with some polycom phones connected to the LAN ports. I had also connected a Zhone OLT to the NV7060 GE 0/1 port with ONT attached to the OLT fiber downlink.

After all the necessary configuration, I plugged in an analog phone at the ONT and was able to ring and conversed with the polycom phone user.

However, when i used the polycom phone to call the ONT phone, the NV7060 was unable to locate the ONT phone and the call was diverted to voice mail.

During the debug sip stack message, it was discovered both calling and called party IP address was changed from 10.10.20.1 to 127.0.0.1 which might have caused the connection breakdown

See the attached debug and config file. Could anyone advise what might have contributed to the problem and offer your valuable fixes. Thanks !

[Anonymous]

Thank you for supplying the debug and configuration.  Admittedly the debug did look strange, almost like the ONT/OLT device tried to register with the NetVanta 7060's IP address or there was some type of loopback somewhere.  To troubleshoot this further we would need to see the output of both a debug voice verbose and debug sip stack messages enabled when the ONT/OLT device registers as well as a failed call attempt.  I would like to point out that while the device may work it is not officially supported.  You may want to check this thread for some other devices that users reported working to extend an analog line if there is not a way to interface it to the analog ports of the local NetVanta 7060:

Thanks,

Matt

[taych]

Thanks matt for your kind reply.

Attached are the debug logs as per your request. Kindly advise if you require further details.

Regards

Clarence

[Anonymous · Accepted solution]

Clarence, the registration message from the ONT device appears to contain some incorrect information. Below is a snippet from a registration of an IP706 phone:

09:11:02.301 SIP.STACK MSG     Rx: UDP src=10.10.20.2:5060 dst=10.10.20.1:5060

09:11:02.301 SIP.STACK MSG         REGISTER sip:10.10.20.1:5060 SIP/2.0

09:11:02.302 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.20.2:5060;branch=z9hG4bK5baa38903

09:11:02.302 SIP.STACK MSG         Contact: IP 706 Test <sip:1330@10.10.20.2:5060;transport=udp>;expires=0

You'll notice that the "Via" and "Contact" headers both reference the local IP address of the phone sending the registration. Here is the same portion from your ONT:

10:54:28.109 SIP.STACK MSG     Rx: UDP src=10.10.20.4:5060 dst=10.10.20.1:5060

10:54:28.109 SIP.STACK MSG         REGISTER sip:10.10.20.1:5060 SIP/2.0

10:54:28.109 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.20.1;branch=z9hG4bKbb1233742cff3299f

10:54:28.111 SIP.STACK MSG         Contact: Zhone15 <sip:3015@10.10.20.1:5060;transport=udp>;expires=3600

In this case, the ONT is inserting the IP address of the 7100 in both of those fields. The 7100 accepts the registration, however it stores its own IP address in the SIP registration database. When you attempt to call that phone, it sends the INVITE to itself in a loop until it times out.

You would need to correct whatever option controls this behavior in the device in order to get the call to work properly.

[Anonymous]

I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post to unmark it and select another in its place with the applicable buttons.  If you have any additional information on this that others may benefit from, please come back to this post to provide an update.  If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

Thanks,

Matt