|
Joined: Sep 2004
Posts: 395
Member
|
Member
Joined: Sep 2004
Posts: 395 |
OK, I'm having an issue with OS7100 system with Jive SIP. Software is 4.99. I'm being told by support that for security reasons the Samsung will only accept inbound SIP traffic from the same server IP address that it is registered to, which I do understand and makes sense to me. The problem is Jive has a range of servers and the inbound traffic can have a different IP address(only the last octet) from the registered address. Not sure if there is a way around this and I'm really surprised I haven't encountered this before.
Any Ideas?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Jun 2006
Posts: 3,004 Likes: 4
Moderator-Samsung
|
Moderator-Samsung
Joined: Jun 2006
Posts: 3,004 Likes: 4 |
Since you know all the ip addresses, add them to mmc833 i think it is.
|
|
|
|
Joined: Sep 2004
Posts: 395
Member
|
Member
Joined: Sep 2004
Posts: 395 |
Thanks for the response Nameless. So SIP peering? Never used that before and there are a number of settings. Default ones good enough? I'm assuming I have to enable SIP peering in the SIP carrier options?
Last edited by MichaelV; 04/30/18 04:16 PM.
|
|
|
|
Joined: Dec 2010
Posts: 681
Member
|
Member
Joined: Dec 2010
Posts: 681 |
How do you register with the Jive sip server? Shouldn't it be using that to make and receive calls as well?
|
|
|
|
Joined: Sep 2004
Posts: 395
Member
|
Member
Joined: Sep 2004
Posts: 395 |
Biztel,
Yes, it registers outbound just fine, pretty standard username, auth username, password, reg and proxy addresses. Problem is, inbound traffic follows a different path, server IP isn't the same as the registered server, but in the same subnet.
|
|
|
|
Joined: Jan 2010
Posts: 184
Member
|
Member
Joined: Jan 2010
Posts: 184 |
Hey
As namless said add them to 833, you don't need to enable SIP peering in the carrier options, 833 can just act as a white list in this instance.
|
|
|
|
Joined: Sep 2004
Posts: 395
Member
|
Member
Joined: Sep 2004
Posts: 395 |
Since you know all the ip addresses, add them to mmc833 i think it is. As namless said add them to 833, you don't need to enable SIP peering in the carrier options, 833 can just act as a white list in this instance. Well this sounds reasonable enough, however when I add the Jive server IP address in 833(leaving everything else at default), the OS7100 responds to the invite with the "status: 100 Trying" message and then promptly crashes and reboots??? What in the world is missing here?
|
|
|
|
Joined: Sep 2004
Posts: 395
Member
|
Member
Joined: Sep 2004
Posts: 395 |
Oh, BTW, I've moved this testing to a spare system, so I don't have to mess around with this on the customer's site. So don't be shy in offering ideas. ;-)
|
|
|
|
Joined: Sep 2004
Posts: 395
Member
|
Member
Joined: Sep 2004
Posts: 395 |
OK, this problem was solved by not using the Jive registration server name that came with the credentials, but using the outbound proxy name in both fields. Not sure why this didn't occur to me to try earlier, probably because Jive support kept saying "are you sure they are both in there properly?"
Anyway, I figured it out by reading the Jive guide for setting up the Panasonic NS700 on their SIP trunks and noticing that you only use the outbound proxy name. Sheesh.
|
|
|
Forums84
Topics94,518
Posts639,974
Members49,849
|
Most Online5,661 May 23rd, 2018
|
|
2 members (Yoda, BobRobert),
273
guests, and
42
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|