Jump to content

Unable to call between the extensions of snom ONE


Ganesh
 Share

Recommended Posts

Hello,

 

We have few snom phones registered with the snom ONE. The snom ONE and few snom phones are at location A. Few more snom phones are at location B and registered to the snom ONE at location A.

 

We are able to make calls between the snom phones connected within the location A. But we cannot call between the snom phones connected at location B.

We can make calls from location B to A but not from A to B.

 

The SIP trace of snom phones at location B says "403 use proxy" for any invites coming from the snom ONE.

 

Attached is the wireshark capture and SIP traces of snom ONE and snom phone. Can someone check this and help asap?

wireshark trace of snom one for non working call between extensions.zip

snom one SIP trace for non working call between extensions.txt

SIP trace of snom phone for non receiving incoming call.txt

Link to comment
Share on other sites

The "Use Proxy" method comes from the phone it seems, and AFAIK there is a setting on the phone that restricts inbound traffic to come from the "proxy" (AKA PBX). You can try to change the setting on the phone if it then accepts the traffic from that address.

 

Basically the phones at location B are registered to the snomone server at location A but are unable to receive any incoming calls. The SIP trace of snom phone at location B says “403, Use Proxy” for the Invites received from the snomone server.

 

The issue seems to be with snomone unable to understand the NAT. If we replace the snomone server with other SIP server, the entire system is working fine. The snom phones can communicate from location B to A and vice versa using the other SIP server.

 

Call flow while snomone is used

 

1. Calls from location A to B is NOT working.

2. Calls from location B to A is working

3. Calls between phones at location B is NOT working

4. Calls between phones at location A is working

 

Attached is the wireshark traces where you see a successful call from location B to A using other SIP server.

wireshark trace of 4s for working call.zip

wireshark trace of snom one for non working call between extensions.zip

Link to comment
Share on other sites

Is this an environment where the PBX has multiple IP addresses? There is no REGISTER message in the snomONE scenario. What is the output of "route print"?

 

There is definitively something wrong in the network setup. Even the RTP statistics coming from the phone show that there is a dramatic packet loss.

 

Also what is the outbound proxy of the phone that sends the "use proxy"? Did you plug and play it with the PBX? Or did you at least factory reset it before registering it to the PBX?

 

This is is a pretty much classical setup and should work without problems pretty much!

Link to comment
Share on other sites

Is this an environment where the PBX has multiple IP addresses? There is no REGISTER message in the snomONE scenario. What is the output of "route print"?

 

There is definitively something wrong in the network setup. Even the RTP statistics coming from the phone show that there is a dramatic packet loss.

 

Also what is the outbound proxy of the phone that sends the "use proxy"? Did you plug and play it with the PBX? Or did you at least factory reset it before registering it to the PBX?

 

This is is a pretty much classical setup and should work without problems pretty much!

 

The PBX has a single domain (localhost) and the server has single IP address (10.10.71.10). Attached is the SIP registration and calls traces of the snom phones with snomONE server.

 

There is no outbound proxy configured in the snom phone. We are using only the Registrar as 10.10.71.10. If we use the same registrar in the outbound proxy, still the same problem is observed. If we use the outbound proxy as 172.21.11.x (as seen in the SIP registration traces of snomONE) then the phones does not register.No plug and play is used, the phones are manually configured with snomONE. Factory reset was done before registering the phones.

 

The phones (ext 111 and 112) at location B can call to phones (203 and 204) at location A whereas the reverse is not working.

The phones (111 and 112) at location B cannot call each other.

The phones (203 and 204) at location A can call each other.

 

The "route print" of snomONE network is

 

C:\Users\Snom Technology>route print

===========================================================================

Interface List

16...1c 65 9d 25 ea c3 ......Microsoft Virtual WiFi Miniport Adapter

14...1c 65 9d 25 ea c3 ......Realtek RTL8191SE 802.11b/g/n WiFi Adapter

11...1c c1 de 9e 41 84 ......Realtek PCIe FE Family Controller

1...........................Software Loopback Interface 1

19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter

37...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2

17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3

15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface

===========================================================================

 

IPv4 Route Table

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 10.10.71.1 10.10.71.10 276

10.10.71.0 255.255.255.0 On-link 10.10.71.10 276

10.10.71.10 255.255.255.255 On-link 10.10.71.10 276

10.10.71.255 255.255.255.255 On-link 10.10.71.10 276

127.0.0.0 255.0.0.0 On-link 127.0.0.1 306

127.0.0.1 255.255.255.255 On-link 127.0.0.1 306

127.255.255.255 255.255.255.255 On-link 127.0.0.1 306

224.0.0.0 240.0.0.0 On-link 127.0.0.1 306

224.0.0.0 240.0.0.0 On-link 10.10.71.10 274

255.255.255.255 255.255.255.255 On-link 127.0.0.1 306

255.255.255.255 255.255.255.255 On-link 10.10.71.10 276

===========================================================================

Persistent Routes:

Network Address Netmask Gateway Address Metric

0.0.0.0 0.0.0.0 10.10.71.1 Default

===========================================================================

 

IPv6 Route Table

===========================================================================

Active Routes:

If Metric Network Destination Gateway

1 306 ::1/128 On-link

11 276 fe80::/64 On-link

11 276 fe80::d991:e426:3991:9937/128

On-link

1 306 ff00::/8 On-link

11 276 ff00::/8 On-link

===========================================================================

Persistent Routes:

None

 

C:\Users\Snom Technology>

The "route print" of phone at location B is

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. All rights reserved.

 

C:\Users\Snom Technology>route print

===========================================================================

Interface List

16...1c 65 9d 25 ea c3 ......Microsoft Virtual WiFi Miniport Adapter

14...1c 65 9d 25 ea c3 ......Realtek RTL8191SE 802.11b/g/n WiFi Adapter

11...1c c1 de 9e 41 84 ......Realtek PCIe FE Family Controller

1...........................Software Loopback Interface 1

19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter

37...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2

17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3

15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface

===========================================================================

 

IPv4 Route Table

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 10.11.51.1 10.11.51.10 276

10.11.51.0 255.255.255.0 On-link 10.11.51.10 276

10.11.51.10 255.255.255.255 On-link 10.11.51.10 276

10.11.51.255 255.255.255.255 On-link 10.11.51.10 276

127.0.0.0 255.0.0.0 On-link 127.0.0.1 306

127.0.0.1 255.255.255.255 On-link 127.0.0.1 306

127.255.255.255 255.255.255.255 On-link 127.0.0.1 306

224.0.0.0 240.0.0.0 On-link 127.0.0.1 306

224.0.0.0 240.0.0.0 On-link 10.11.51.10 274

255.255.255.255 255.255.255.255 On-link 127.0.0.1 306

255.255.255.255 255.255.255.255 On-link 10.11.51.10 276

===========================================================================

Persistent Routes:

Network Address Netmask Gateway Address Metric

0.0.0.0 0.0.0.0 10.11.51.1 Default

===========================================================================

 

IPv6 Route Table

===========================================================================

Active Routes:

If Metric Network Destination Gateway

1 306 ::1/128 On-link

11 276 fe80::/64 On-link

11 276 fe80::d991:e426:3991:9937/128

On-link

1 306 ff00::/8 On-link

11 276 ff00::/8 On-link

===========================================================================

Persistent Routes:

None

 

C:\Users\Snom Technology>

SIP registration traces of snomONE.txt

SIP logs for calls using snomONE.txt

Wireshark traces of calls using snomONE.zip

Link to comment
Share on other sites

[7] 2011/03/29 01:44:37: SIP Rx udp:172.21.11.10:50142:

REGISTER sip:10.10.71.10 SIP/2.0

Via: SIP/2.0/UDP 172.21.11.10:10719;branch=z9hG4bK-qf3j8jmaxb8g

[...]

 

[7] 2011/03/29 01:44:37: SIP Tx udp:172.21.11.10:10719:

 

So why does the phone not include the rport parameter? Maybe it was turned off (http://wiki.snom.com/Settings/enable_rport_rfc3581). As a result, the PBX sends the response back to the port that was advertized by the phone (according to the RFC).

 

Generally, I would suggest to factory-reset the phones and then use plug and play for the phones (including the upgrade to 8.4.18). You can try this with one phone and then if it solves the problems then you can include the other phones as well.

 

 

Link to comment
Share on other sites

  • 2 weeks later...

So why does the phone not include the rport parameter? Maybe it was turned off (http://wiki.snom.com/Settings/enable_rport_rfc3581). As a result, the PBX sends the response back to the port that was advertized by the phone (according to the RFC).

 

Generally, I would suggest to factory-reset the phones and then use plug and play for the phones (including the upgrade to 8.4.18). You can try this with one phone and then if it solves the problems then you can include the other phones as well.

 

Thanks. This is now working after the upgrade. :)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...