problem setup trunk EuteliaVoip

[NSC-PA]

Hi,

someone managed to correctly configure a trunk with the operator Eutelia voip?

I have problems in receiving. "The number you have dialed is currently not available":

 

- this is my configuration:

# Trunk 12 in domain pbx.mydomain.local

Name: 091637XXXX

Type: register

To: sip

RegPass: ********

Direction:

Disabled: false

Global: true

Display: 09174802XX

RegAccount: 09174802XX

RegRegistrar: voip.eutelia.it:5060

RegKeep: 200

RegUser: 09174802XX

Icid:

Require:

OutboundProxy: voip.eutelia.it:5060

Ani:

DialExtension: 210

Prefix:

Trusted: true

AcceptRedirect: false

RfcRtp: false

Analog: false

SendEmail: true

UseUuid: false

Ring180: false

Failover: never

HeaderRequestUri: {request-uri}

HeaderFrom: {trunk}

HeaderTo: {request-uri}

HeaderPai:

HeaderPpi:

HeaderRpi:

HeaderPrivacy: id

HeaderRpiCharging: icid-value={icid-value};icid-generated-at={ip-address};orig-ioi={domain}

BlockCidPrefix:

Glob:

RequestTimeout:

Codecs: 8

CodecLock: true

DtmfMode:

Expires: 60

FromUser:

Tel: true

TranscodeDtmf: false

AssociatedAddresses:

InterOffice: false

DialPlan:

UseEpid: false

CidUpdate: info

Ignore18xSDP: false

UserHdr:

Colines:

DialogPermission:

 

- this is the translation assistance of Eutelia

 

We inform you that the numbers are configured on the PBX snomONE, but the checks carried out by the same issues the following error:

"Domain used is invalid, it 's likely that the user does not receive phone calls"

 

can someone help me?

thk

[Vodia support]

Please follow these guidelines to produce a SIP log. We will need to see the invite from the snomONE to the trunk provider.

 

http://wiki.snomone.com/index.php?title=How_to_Take_SIP_log_file.

[NSC-PA]

this is the log of the trunk, the

registration is ok, but the calls are not received:

 

 

[5] 2012/09/06 16:06:43:

 

SIP Rx udp:83.211.227.21:5060:

 

 

 

INVITE sip:0917487599@84.253.134.203:40819;transport=udp;line=a87ff679 SIP/2.0

Record-Route: <sip:83.211.227.21;lr=on;ftag=39A281C8-2362>

Via: SIP/2.0/UDP 83.211.227.21;branch=z9hG4bK3c38.995b1cd4.0

Via: SIP/2.0/UDP 195.62.226.18:5060;rport=64056;received=195.62.226.18;x-route-tag="tgrp:Slot7";branch=z9hG4bK166D09DDC

From: <sip:3939187523@195.62.226.18>;tag=39A281C8-2362

To: <sip:0917487599@voip.eutelia.it>

Call-ID: 90E763A3-F76211E1-B201820C-AC8A991E@195.62.226.18

User-Agent: Cisco-SIPGateway/IOS-12.x

CSeq: 101 INVITE

Max-Forwards: 9

Remote-Party-ID: <sip:3939187523@195.62.226.18>;party=calling;screen=yes;privacy=off

Contact: <sip:3939187523@195.62.226.18:64056>

Expires: 180

Allow-Events: telephone-event

Content-Type: application/sdp

Content-Length: 443

P-hint: 2 Niente 2

 

v=0

o=CiscoSystemsSIP-GW-UserAgent 7467 5558 IN IP4 195.62.226.18

s=SIP Call

c=IN IP4 62.94.199.37

t=0 0

m=audio 51234 RTP/AVP 18 8 0 4 3 2 125 101

c=IN IP4 62.94.199.37

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=yes

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:4 G723/8000

a=fmtp:4 bitrate=5.3;annexa=no

a=rtpmap:3 GSM/8000

a=rtpmap:2 G726-32/8000

a=rtpmap:125 X-CCD/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

 

 

 

 

[5] 2012/09/06 16:06:43:

 

SIP Tx udp:83.211.227.21:5060:

 

 

 

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 83.211.227.21;branch=z9hG4bK3c38.995b1cd4.0

Via: SIP/2.0/UDP 195.62.226.18:5060;rport=64056;received=195.62.226.18;x-route-tag="tgrp:Slot7";branch=z9hG4bK166D09DDC

Record-Route: <sip:83.211.227.21;lr=on;ftag=39A281C8-2362>

From: <sip:3939187523@195.62.226.18>;tag=39A281C8-2362

To: <sip:0917487599@voip.eutelia.it>;tag=2955a935fd

Call-ID: 90E763A3-F76211E1-B201820C-AC8A991E@195.62.226.18

CSeq: 101 INVITE

Content-Length: 0

 

 

 

 

 

[5] 2012/09/06 16:06:43:

 

SIP Tx udp:83.211.227.21:5060:

 

 

 

SIP/2.0 404 Not Found

Via: SIP/2.0/UDP 83.211.227.21;branch=z9hG4bK3c38.995b1cd4.0

Via: SIP/2.0/UDP 195.62.226.18:5060;rport=64056;received=195.62.226.18;x-route-tag="tgrp:Slot7";branch=z9hG4bK166D09DDC

Record-Route: <sip:83.211.227.21;lr=on;ftag=39A281C8-2362>

From: <sip:3939187523@195.62.226.18>;tag=39A281C8-2362

To: <sip:0917487599@voip.eutelia.it>;tag=2955a935fd

Call-ID: 90E763A3-F76211E1-B201820C-AC8A991E@195.62.226.18

CSeq: 101 INVITE

Contact: <sip:0917487599@10.99.0.202:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: snomONE/4.5.0.1090 Epsilon Geminids

Content-Length: 0

 

 

 

 

 

[5] 2012/09/06 16:06:43:

 

SIP Rx udp:83.211.227.21:5060:

 

 

 

ACK sip:0917487599@84.253.134.203:40819;transport=udp;line=a87ff679 SIP/2.0

Via: SIP/2.0/UDP 83.211.227.21;branch=z9hG4bK3c38.995b1cd4.0

From: <sip:3939187523@195.62.226.18>;tag=39A281C8-2362

Call-ID: 90E763A3-F76211E1-B201820C-AC8A991E@195.62.226.18

To: <sip:0917487599@voip.eutelia.it>;tag=2955a935fd

CSeq: 101 ACK

Max-Forwards: 70

User-Agent: SPS EUT RM GW 04

Content-Length: 0

[Vodia support]

is "0917487599" a DID tied to an extension if not follow this guideline.

Extension and DID

When the DID is associated with the account the pbx will search for a match, other suggestion is to populate the "send call" to field in the trunk section, maybe you can send the call to an Auto Attendant for starters.

 

 

Send call to field

 

also add the trunks provider IP to the Explicitly list addresses for inbound traffic: found in the trunk section as well, and choose "yes".

 

If the above does not work try playing with the trunk custom header, under the "Remote Party/Privacy Indication" in the trunk section.

 

http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers

[NSC-PA]

thanks for the help, I solved by deleting and creating the trunk as before.

 

I think the problem is to change the old trunk with parameters of another operator