CM 5.2.1 / SES 5.2.1 - Using wrong Protocol to connected Proxy

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • cdresen
    Member
    • May 2010
    • 3

    CM 5.2.1 / SES 5.2.1 - Using wrong Protocol to connected Proxy

    Hi there!

    We have a working solution with a CM 5.2.1 / SES 5.2.1 connected to a Ericsson MX-ONE PBX. The trunks between SES and Ericsson are configured as SIP-Trunks using TCP.

    Our main problem right now is, that all connections from the SES to any other device work with TCP. But whenever a an INVITE is send from the SES to the Ericsson side, the whole communication is realized via UDP.

    Unfortunately it is not possible, as far as I know, to disable UDP on either side.

    Just to be clear, I'm talking about everything but the RTP-Sessions. Of course, they are supposed to be UDP and thats all fine.

    What our customer just wants, is that all the communications, with the expection of the RTP-rounds, is TCP only.

    I have uploaded snapshots of either configurations of both systems.

    Please fill this thread with ideas/thoughts/comments. Every help is much appreciated!

    Regards,
    Chris
    Attached Files
  • pappaka
    Hot Shot
    .
    • Mar 2010
    • 11

    #2
    Reply

    Looking at the configuration of host Maps i don't find configuration issue. However I cannot comment on why UDP is used when TCP is configured as transport protocol for signalling between Avaya SES and Ericsson one-PBX.

    In order to find the reason I request for creating a online service request for troubleshooting the issue.

    Comment

    Loading