Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Recent content by Dmitriy_Nik

  1. D

    incoming call from SP

    Thanks for your interest in this post, I tried to solve the problem via TLS to make a trusted connection, but at the last moment I saw that when I bought SBCE, the manager did not include a free encryption license. As a result, I removed SMRG from the chain and left CM>SBE It's all working...
  2. D

    incoming call from SP

    II decided to try to build this circuit via tls, but when I got to the finish line I found out that there is no encryption license. I'll try to find one tomorrow. Found an interesting article, maybe this is my situation https://support.avaya.com/ext/index?page=content&id=SOLN216621&viewlocale=en_US
  3. D

    incoming call from SP

    😓, it was the middle of the night, I got confused. I corrected it, but the situation hasn't changed.
  4. D

    incoming call from SP

    Tried it, but nothing changed.
  5. D

    incoming call from SP

    Yes , I did. All entries are trusted in asm sip and sbc sip.That's why I can't understand why it lets outgoing calls through, but not incoming calls.
  6. D

    incoming call from SP

    I'm trying to figure out why SM is giving an error, but I can't find out where to look. All entities are created, routes are specified....
  7. D

    incoming call from SP

    Thank you all for the advice on my question. I solved the problem by removing SM from the chain, leaving only CM and SBC.
  8. D

    incoming call from SP

    I changed B1's IP address. But the situation has not changed. I did topology hiding as you said in your first reply. I'm doing something wrong... Yes, like you said, for some reason the connection is not trusted. and when receiving OPTIONS from the provider, the SM responds with
  9. D

    incoming call from SP

    Yes, on the SM server this option is also enabled. Media ports in the range 40000-52000, Signal ports 5060 1. 2.xx.xx.xx:47317 ──TCP─► 172.25.0.63:5060 | INVITE sip:+77*******40@172.25.0.63:5060 SIP/2.0 2. 172.25.0.63:5060 ──TCP─► 2.xx.xx.xx:47317 | SIP/2.0 100 Trying 3...
  10. D

    incoming call from SP

    Sorry, last time (first post) i fogot refresh trusted links from SM / initTM. This trace from SBC,it shows that the response is coming from SM towards SBC Grooming enfble on both sides SIP trunk without registration, outgoing communication works fine
  11. D

    incoming call from SP

    I have checked the SBC configuration again and have not found that the UDP protocol is used. However, when exchanging INVITE messages, the following is received from the provider side: │Via: SIP/2.0/TCP 172.16.240.132:5060;branch=z9hG4bK71b7.0d5f7945.0;rport...
  12. D

    incoming call from SP

    Acm sm trunk for j139 users asm sbc trunk for sip provider And the second one, just for test, acm asm 5070 tcp to release dialed numbers to the provider via a separate trunk to sm Yes you are right, I saw tcp and udp ports in traceSM ,I will try to get the data tomorrow and show you.
  13. D

    incoming call from SP

    Sip phones are configured via SM, they are inside the corporate network. On the SBC only the provider's trunk
  14. D

    incoming call from SP

    A1 and B1 interfaces have internal addresses and interface b1 goes through NAT. There are no remote workers on sbc, only sip trunk of the provider.
  15. D

    incoming call from SP

    I have J139 phones that are SM to CM adapted and running on the same port 5060 with the endpoint flag. Could this be related to this issue? Maybe I need to change the ports in 'SIP Entities' for asm => sbc=> SP mapping to a different one?
See more

Part and Inventory Search

Back
Top