SIP Trunk Issue

[Mitelboy]

Hi,
I have an issue dial out on SIP Trunk i have an MCD 7.0 PR1 and MBG 8.0.26 as sip proxy and mbg in server and gateway mode i spoke with service provider and they said the invite message on sip is IP Address instead of domain name. does anyone have an idea so i can sent the domain name instead of IP Address.

 

[sarond]

First place I would try is in the SIP Peer Profile
"Use To Address in From Header on Outgoing Calls"

When this option is enabled (set to 'Yes') the Address used in the SIP From header line will no longer be the physical 3300 IP address or FQDN. Instead the address will be replaced by the address to which the outgoing call is sent. Some providers require this for authentication purposes as it makes it look like the 3300 ICP is in the same domain as the SIP Server or SBC (Session Border Controller).

 

[Mitelboy]

thank you so much for your reply.
the value is already enabled.
There are two invite messages one is MCD to MBG internal network address this has the domain name and the other is from MBG's external network to Service provider SBC (Session Border Controller) this has the IP Address of SBC instead of domain name.

 

[DaveT82]

I know this thread is a few months old now but did you manage to find a solution? I'm facing the same issue - the MBG is rewriting the request to have the IP address of the destination SIP trunk rather than the domain provided in the SIP peer profile and SIP trunk configuration on the MBG.

I assume it's just a setting I need to enable but I'm not sure which!

 

[Billz66]

what about on the sip peer

Address Type


Select the address type for the local host. Two types are available:
FQDN - the Fully Qualified Domain Name (FQDN) of the local host, and the DNS name from the System IP Properties form.
IP - from the System IP Properties form.

NOTE: Ensure that MiVoice Business and the Service Provider are using the same Address Type in their SIP messages. If MiVoice Business uses FQDN, then the Service Provider must use FQDN.



If I never did anything I'd never done before , I'd never do anything.....

and due to an endless stream of MiCollab , MiCC issues
Life would be simpler If only they tested products properly before releasing them .....

 

[DaveT82]

Thanks for the suggestion but unfortunately regardless of that setting the MBG still rewrites the invite line to include the IP address of the SIP peer rather than the domain name.
The invite that the MCD sends to the MBG correctly contains the domain name, it's the MBG that's adjusting it

Cheers

 

[DaveT82]

Just to update the thread I resolved this issue by entering the SIP peer address again in the "External SIP Proxy" box under the Network element entry for the SIP peer

Cheers!

 

[bribob]

Dave,

I was in the same boat trying to get a Telstra trunk to work. Telstra wanted the domain name in the TO/FROM/PAI headers but the MBG was resolving the domain and sending out the IP. The MBG was in Server-Only mode, so we flipped it to Server-Gateway and that seems to have changed the MBG header manipulation behavior.

I also had to program 2 SIP peers in the MBG, one for the actual Telstra SBC (External SIP Proxy of the Network Element) and another for the domain (FQDN and SIP Registrar FQDN of the Network Element).
A static entry in MBG DNS was required for the domain (which was a fake domain) which resolves to the IP address of the SBC.

I'm going to swing the MBG back into Server-Only mode and see if the dual SIP peer configuration keeps the header manipulation the way it should be or if the Server-Gateway mode is the trick.


-b