Problem with incoming calls on trunk after update

[fonny]

Updated from Coma Berenicids to Epsilon Geminids

Trunk to weepee.org was working and will work the first minutes after the update but stops working after.

 

Trunk settings are:

# Trunk 2 in domain mycompany

Name: WeePeeTrunk

Type: register

To: sip

RegPass:

Direction:

Disabled: false

Global: false

Display: WeePeeTrunk

RegAccount: 329909010779

RegRegistrar: ssw9.brussels.weepee.org

RegKeep:

RegUser: 329909010779

Icid:

Require:

OutboundProxy: ssw9.brussels.weepee.org

Ani:

DialExtension: 40

Prefix:

Trusted: false

AcceptRedirect: false

RfcRtp: false

Analog: false

SendEmail:

UseUuid: false

Ring180: false

Failover: never

HeaderRequestUri: {request-uri}

HeaderFrom: {from}

HeaderTo: {to}

HeaderPai: {trunk}

HeaderPpi:

HeaderRpi:

HeaderPrivacy: id

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

BlockCidPrefix:

Glob:

RequestTimeout:

Codecs:

CodecLock: true

DtmfMode:

Expires: 3600

FromUser:

Tel: true

TranscodeDtmf: false

AssociatedAddresses:

InterOffice: false

DialPlan:

UseEpid: false

CidUpdate:

Ignore18xSDP: false

UserHdr:

Diversion:

Colines:

DialogPermission:

 

 

 

Checking the logs I see a difference after the REGISTER in the OPTIONS part.

With the previous version I have:

 

[9] 2012/10/29 23:11:31: Message repetition, packet dropped

[5] 2012/10/29 23:11:32: SIP Rx udp:91.208.12.139:5060:

OPTIONS sip:329909010779@192.168.120.54:5060;transport=udp;line=c81e728d SIP/2.0

Via: SIP/2.0/UDP 91.208.12.139:5060;branch=z9hG4bK72a4dc0a;rport

Max-Forwards: 70

From: "weepee" <sip:weepee@91.208.12.139>;tag=as4a5f9acc

To: <sip:329909010779@192.168.120.54:5060;transport=udp;line=c81e728d>

Contact: <sip:weepee@91.208.12.139:5060>

Call-ID: 7074c6386ca4d794639411ea1e5c9b3b@91.208.12.139:5060

CSeq: 102 OPTIONS

User-Agent: weepee

Date: Mon, 29 Oct 2012 22:11:32 GMT

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Content-Length: 0

 

[9] 2012/10/29 23:11:32: Resolve 178: aaaa udp 91.208.12.139 5060

[9] 2012/10/29 23:11:32: Resolve 178: a udp 91.208.12.139 5060

[9] 2012/10/29 23:11:32: Resolve 178: udp 91.208.12.139 5060

[5] 2012/10/29 23:11:32: SIP Tx udp:91.208.12.139:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 91.208.12.139:5060;branch=z9hG4bK72a4dc0a;rport=5060

From: "weepee" <sip:weepee@91.208.12.139>;tag=as4a5f9acc

To: <sip:329909010779@192.168.120.54:5060;transport=udp;line=c81e728d>;tag=808dd1526e

Call-ID: 7074c6386ca4d794639411ea1e5c9b3b@91.208.12.139:5060

CSeq: 102 OPTIONS

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

Content-Length: 0

 

[5] 2012/10/29 23:11:32: SIP Rx udp:91.208.12.139:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.120.54:5060;branch=z9hG4bK-63a8e4850daf5389ee0ea7beaccd8484;received=91.177.194.126;rport=2616

From: "WeePeeTrunk" <sip:329909010779@ssw9.brussels.weepee.org>;tag=148562258

To: "WeePeeTrunk" <sip:329909010779@ssw9.brussels.weepee.org>;tag=as4e1af036

Call-ID: dnju1co1@pbx

CSeq: 21259 REGISTER

Server: weepee

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Expires: 3600

Contact: <sip:329909010779@192.168.120.54:5060;transport=udp;line=c81e728d>;expires=3600

Date: Mon, 29 Oct 2012 22:11:32 GMT

Content-Length: 0

 

 

With the new server version I get:

 

[9] 2012/10/29 23:17:50: Message repetition, packet dropped

[5] 2012/10/29 23:17:50: SIP Rx udp:91.208.12.139:5060:

OPTIONS sip:329909010779@192.168.120.54:5060;transport=udp;line=c81e728d SIP/2.0

Via: SIP/2.0/UDP 91.208.12.139:5060;branch=z9hG4bK2871ac1c;rport

Max-Forwards: 70

From: "weepee" <sip:weepee@91.208.12.139>;tag=as65951f72

To: <sip:329909010779@192.168.120.54:5060;transport=udp;line=c81e728d>

Contact: <sip:weepee@91.208.12.139:5060>

Call-ID: 22e17dd3493accaf5e1876d012a9ea5e@91.208.12.139:5060

CSeq: 102 OPTIONS

User-Agent: weepee

Date: Mon, 29 Oct 2012 22:17:50 GMT

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Content-Length: 0

 

[5] 2012/10/29 23:17:50: SIP Rx udp:91.208.12.139:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.120.54:5060;branch=z9hG4bK-785019a110535dc753b83f44ff538859;received=91.177.194.126;rport=1796

From: "WeePeeTrunk" <sip:329909010779@ssw9.brussels.weepee.org>;tag=1259204269

To: "WeePeeTrunk" <sip:329909010779@ssw9.brussels.weepee.org>;tag=as34775fb0

Call-ID: niy63v33@pbx

CSeq: 18014 REGISTER

Server: weepee

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Expires: 3600

Contact: <sip:329909010779@192.168.120.54:5060;transport=udp;line=c81e728d>;expires=3600

Date: Mon, 29 Oct 2012 22:17:50 GMT

Content-Length: 0

 

Any idea what I need to change in the settings ?

[Vodia support]

Have tried the different variations under the "Remote Party/Privacy Indication"

 

The next option is to configure the custom headers, try the above if you're not successful then revert back to Coma Berenicids and post the invite so we can look at the headers.

[fonny]

Tnx Mr X,

 

I have tried all options under the "Remote Party/Privacy Indication" and been playing with different settings in Custom Header but still no go.

 

Included 'trace Coma Berenicids' which works. Startup pbx and receive one call.

Trace Epsilon Geminids is started directly after stopping Coma Berenicids and startup Epsilon Geminids. Weepee will accept the first incoming call but further incoming calls no more work.

Trace Epsilon Geminids2 is after stopping & starting Epsilon Geminids. Incoming calls don't work.

Outgoing calls work in both situations.

 

Fonny

[fonny]

anyone an idea whats wrong in my config ?

[fonny]

Updated today to v5.03 and suddenly all is working now.

[Vodia support]

That's excellent another great reason to run V5.03