locked
Inbound sip trunk calls going to edge server RRS feed

  • Question

  • Hello Guys, we are trying to implement sip trunking into our on-premises SfB using AudioCodes Mediant 800 SBA. We can successfully make outbound calls but inbound calls will not work. I traced the issue using SfB logging tool and I can see that when the inbound SIP invite message arrives on the Front-end/mediation server it will route  to the edge server and  the edge server then sent back a 404 error.  Can anyone please tell me why this is happening? Thanks. MS
    Friday, November 4, 2016 6:08 AM

All replies

  • Friday, November 4, 2016 6:30 PM
  • Deleted
    Friday, November 4, 2016 9:01 PM
  • Hi MS-Tech-001,

    You SIP trunk is going to the SBC application of the Audiocodes Gateway?

    Direct sip trunk to the SBA is not supported.


    regards Holger Technical Specialist UC

    Saturday, November 5, 2016 9:07 AM
  • Thanks everybody for the quick reply. I have attached a screenshot of the sip trace which I took while making an inbound call. The first block is audiocodes gateway, the second one is our front end/mediation server and the last one is the edge server. We are currently receiving inbound calls via an analogue gateway so I guess our normalisation rules are ok.  I have created a RG workflow for one of our new sip number.  Can I please know if there is anything else I need to do? 

    @shankar - the audiocodes gateway not seems to be sending the dialled digits in E164 format, could it be the issue?  If so what can I do to fix it?

    @Holger -yes we are using SBC application. 




    • Edited by MS-Tech-001 Monday, November 7, 2016 5:36 AM
    Monday, November 7, 2016 5:34 AM
  • Monday, November 7, 2016 3:30 PM
  • Hi Guys! I have fixed our issue. As suspected it was a E164 issue. I was under impression that the user dial plan was used for both inbound and outbound normalization so didn't give any attention to the Global dial plan which was actually controlling the inbound normalization.  There was also a rule with same name on both global and user dial plan which created confusion while debugging the issue. Thanks a lot for all of your help.
    • Proposed as answer by Alice-Wang Tuesday, November 8, 2016 8:15 AM
    Tuesday, November 8, 2016 4:24 AM