0

Inbound Route Unitymedia by setting username

Pat Riley

June 02, 2021 07:41

None

Follow

Hello Forum,

i have a problem creating a inbound route for unitymedia sip-accounts on a yeastar s20 pbx.

The registration on a SIP-Server works with all my numbers, where you have to specify your sip-data according to the scheme username: n123456789_1, your password and the sip server.

Normally you create a inbound route by specify a did pattern according to the number(for example 0049021116729341 belongs to the username n123456789_1) that you want to reach form outside to your extension.

But in this case it doesn't work.

I made a wireshark scan where i made a discovery that surprised me. The SIP-Invite includes the username instead of the phone number you are dialing from outside.

 

I have no idea how to link the username to the number in a inbound route, because the username contains a underscore that is not allowed to use in the inbound routes.

 

Maybe someone has a idea or solution for this kind of sip-account.

I would appreciate.

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  Eric Jiang June 03, 2021 00:49

  Hi Pat Riley, I have created a ticket for you on this issue and our engineer will contact you soon.

• 0
  
  Larry Neblett June 03, 2021 16:06

  The post is a little confusing to follow, but perhaps when you do a Wireshark, the headers of interest are the To and URI headers. It is these headers that will contain the DID that the caller is using they may be somewhat different from one another as your provider, may for example, use and e.164 format for one (+XXXXXX) and a regular number for the other (XXXXXX). Examine these headers and if different, determine which one you wish to use and then set same in the trunk settings under advanced, inbound. Most like to use the TO header. 

  Then looking at the TO header, copy the number exactly as shown and put that in the DID filed for the Inbound route and direct to the extension or desired destination.  

• 0
  
  Pat Riley June 05, 2021 09:30

  This is unfortunately my problem.

  You can see the URI in the picture below.

  

  How can i create a inbound route that works? I can't use n185355003_1 because of the syntax:(

  Do you have any idea?

   

  Thanks for your support.